The system may also hang if the network adapter is configured
incorrectly. The configuration settings include IRQ, Base I/O
port, and Base Memory Address.
To correct your settings under Windows for Workgroups 3.1, delete the
PROTOCOL.INI, PROTMAN.DOS, WORKGRP.SYS, and other Workgroup network
driver files. Then, from Control Panel, choose the Network icon, and
indicate the correct network adapter and configuration settings.
To correct your settings under Windows for Workgroups 3.11:
a. Start Windows for Workgroups by typing "win /n" (without the
quotation marks) and then press ENTER.
b. In the Network group, choose the Network Setup icon.
c. Configure Windows for Workgroups for No Network and exit Windows for
Workgroups.
d. Rename the PROTOCOL.INI file to PROTOCOL.PSS. For example, type
"ren c:\windows\protocol.ini c:\windows\protocol.pss" (without the
quotation marks) at the MS-DOS command prompt and then press ENTER.
e. Run Windows for Workgroups.
f. In the Network group, choose the Network Setup icon.
g. Configure Windows for Workgroups for the appropriate network card
using the correct settings.
h. Exit and restart Windows for Workgroups.
NOTE: Each time the PROTOCOL.INI file is updated, the old one is
saved with a sequentially numbered extension (that is, PROTOCOL.000,
PROTOCOL.001, PROTOCOL.002, and so forth). Using this naming
convention, you may be able to recover an earlier PROTOCOL.INI that
was configured correctly.
Windows may hang if you have installed the incorrect NDIS NIC
network card driver in your CONFIG.SYS file. To verify that the
driver you selected matches the network card you are using, choose
the Network icon from Control Panel. If the network card you are
using is not listed during Setup, check the manufacturer's
suggested emulation.
The network card supplier may need to provide an NDIS-compatible
driver. If the card you are trying to install is not listed in
Control Panel, contact your network card manufacturer to obtain a
specific NDIS driver that works with Windows for Workgroups.
The order of the network drivers in the CONFIG.SYS file is also
important. For example, protocol manager (PROTMAN.DOS) must be
loaded before any other Windows for Workgroup network drivers. If
PROTMAN.DOS is not loaded first, you may receive various error
messages referring to the protocol manager.
For troubleshooting purposes, remove the Windows for Workgroups
network drivers from the CONFIG.SYS and AUTOEXEC.BAT files. When
you start Windows for Workgroups, you should receive a message
about no network functionality. Accept the message and continue
loading Windows for Workgroups.