said:
>Interesting. Before having loaded any drivers, NICPAK reported up to 6
>options after chipset detection in addition to the FETND. It suggested
>the Realtek 8139 as well, which I thought was curious (I've had good luck
>with these) but since the machine is a VIA based system, I decided to go
>with the FETND. Is the Realtek 8139 driver a real option or a
>lesser/inaccurate detection? Curiously, after having loaded the FETND,
>NICPAK reports only the FETND option.
Hard to say without seeing the output of
pci.exe -P -T -B -D -R
>In the driver with the less-than-stellar reputation, you think or
>elsewhere?
Probably the driver. The Resource Manager only reports what the driver
tells it.
>Apparently not this one, huh?
:-)
>When you run the report.cmd that comes with SPCIIRQ (which contains
>individually many of the reports you are asking for below) which
>aggregates the output into one file called report.log.
Uhh. This only works if report.cmd can find all the exes it calls and if
you send me the zip file that it creates.
>I think it works as "pci -b -d -p" and that's what was included) and ...
Either way is fine.
FWIW, I recommend you reread report.log, so you know what to send me.
>both are included in the attached DIAGNOSE.ZIP file.
No they aren't. ;-)
>Strangely, the FETND.NIF file does not have an entry for the IRQ option
>range. I've seen these in other NIF files usually specifying a default
>value and the possible values but this NIF does not.
You are thinking ISA-land and living in PCI-land. Well written PCI
drivers are capable of allocating their IRQs without assistance. SPCIIRQ
overcomes the limitations of some drivers by doing the allocation for
them.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 14 |
September |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
