The information in this article applies to:
SUMMARY
When you install Windows for Workgroups over Microsoft LAN Manager, Setup
assumes you are upgrading your network operating system. It assumes that
you will not be using LAN Manager as your network, but will instead be
using the Microsoft Windows Network, or one of the other supported networks
listed during installation. MORE INFORMATIONAfter you install Windows for Workgroups on top of LAN Manager and select "No Windows support for networks," the following error message may appear when you start Windows: The AUTOEXEC.BAT, CONFIG.SYS, and SYSTEM.INI files need to be modified to make Windows for Workgroups function properly with LAN Manager. Setup saved your old CONFIG.SYS file as CONFIG.OLD and your old AUTOEXEC.BAT file as AUTOEXEC.OLD. Copy the lines specific to LAN Manager from the .OLD files and combine them with the lines needed for Windows. NOTE: If you had an existing AUTOEXEC.OLD or CONFIG.OLD, it will rename the files CONFIG.001 and AUTOEXEC.001 Example AUTOEXEC.BAT for Windows for Workgroups with LAN Manager: @ECHO OFFExample CONFIG.SYS for Windows for Workgroups with LAN Manager: (Notice that the line DEVICE=C:\WINDOWS\IFSHLP.SYS has been removed that Windows for Workgroups Setup usually inserts.) DEVICE=C:\DOS\SETVER.EXEDelete the SYSTEM.INI in the Windows directory. Modify the following lines:
The PROTOCOL.INI in the LANMAN.DOS directory should remain unchanged from a
regular LAN Manager workstation. The PROTOCOL.INI in the Windows directory
should contain only the following lines:
NOTE: If you plan on using WinPopup, make sure that you run WINPOPUP.EXE
from the LANMAN.DOS\NETPROG directory, not the one that may be in the
Windows directory.
Additional query words: wfw wfwg 3.11 2.2 2.1
Keywords : |
Last Reviewed: September 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |