Windows For Workgroups - Intel EtherExpress PRO/100 User Manual

2 If you hang on error code 92%, the NDIS driver loaded properly
but the scheduler failed to load. This is usually because your
interrupt in the PROTOCOL.INI doesn't match the ni_irq line.
Make sure you change the ni_irq line to match the INT you want
to use. This process is described under DEC PATHWORKS in
Chapter 2, Software Installation.
3 If everything loads and you don't connect to the network, try the
following
a Choose another INT setting.
b Verify that you have a good cable.
c Verify that you have excluded the memory being used by the
Intel adapter from the EMM386 line of CONFIG.SYS.
d Try adding wordsize=8 in the m16andis section of the
PROTOCOL.INI file.
e Always do a cold boot when troubleshooting.

Windows for Workgroups

This section describes general troubleshooting procedures and
possible error codes you might encounter under Windows for
Workgroups. Before doing anything else, check your configuration
files against the sample files in Chapter 3, Configuration Reference
of this document.
Drivers load but you cannot see anybody on the network.
• Check that you have selected the correct workgroup.
• Ensure that there are no spaces in your computer name.
When trying to perform the add adapter function, an error occurs
stating the OEMSETUP file does not contain adapter information.
Move or rename the oem*.inf files from the windows system directory
(C:\WINDOWS\SYSTEM) and invoke the network setup program
again.
Drivers do not load or errors are reported when net start is executed.
Determine if Card and Socket services are in use. Use the vendor
provided configuration program to determine what memory and
interrupt resources are allocated in Card and Socket services for the
Troubleshooting
107