Mixing NDIS 2.0 and NDIS 3.x in Docked and Undocked StatesLast reviewed: December 11, 1995Article ID: Q140990 |
The information in this article applies to:
SYMPTOMSWhen you are using a portable computer with a PCMCIA network adapter that uses NDIS 2.0 (16-bit) drivers, the computer may stop responding (hang) or reboot when you try to start it while it is not docked in its docking station if the docking station contains a network card that is capable of using NDIS 3.x (32-bit) network adapter drivers.
CAUSEWhen Windows 95 detects the NDIS 2.0 drivers for the PCMCIA network adapter, it forces the loading of NDIS 2.0 drivers for the other network adapter (which is not currently present because the computer is undocked). Because one of the network adapters is not present, an incomplete binding occurs, which can cause the computer to hang or reboot.
RESOLUTIONTo enable Windows 95 to start whether the computer is docked or undocked, create a multiple-boot configuration. Do not perform this procedure until you have determined that you have a docked state that requires an NDIS 3.x driver to be loaded and an undocked state that requires an NDIS 2.0 driver to be loaded, or vice versa. If this is not the case, you need to perform other troubleshooting steps to resolve the problem. To create a multiple-boot configuration, follow all the steps in the following sections.
Preparing for Multiple Configurations
Configuring the Network While Docked
Configuring the Network While Undocked
Enabling Multiple ConfigurationsNOTE: The information in this section assumes that Windows 95 is installed in the Windows folder on drive C. If this is not the case, please adjust the following information accordingly. Use any text editor (such as Notepad or Edit.com) to edit the Autoexec.bat file. Add the following lines to the file:
set windir=c:\windows choice/c:DU Docked or Undocked configuration if errorlevel 2 goto docked if errorlevel 1 goto undocked goto end :docked cd %windir% attrib -r -s -h system.dat del system.dat del protocol.ini copy/b c:\configs\system.dok system.dat copy c:\configs\protocol.dok protocol.ini goto end :undocked cd %windir% attrib -r -s -h system.dat del system.dat copy/b c:\configs\system.und system.dat copy c:\configs\protocol.und protocol.ini goto end :end rem all doneAfter you add these lines, save and then close the Autoexec.bat file. When you restart your computer, the network adapter drivers will be processed after the Autoexec.bat file has been processed. Therefore, the networking components can be segregated into separate boot configurations without causing a problem. NOTE: Although this technique can be used for a variety of different situations, it should be used only in this case. All other situations requiring multiple configurations should be handled through the user interface using system profiles.
REFERENCESFor additional information about setting up multiple configurations, double-click the Help.com file in the Other\Oldmsdos folder on the Windows 95 CD-ROM, and then click Multi-config on the Command References page.
|
KBCategory: kbnetwork kbhw
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |