What is a Clean Boot for WFWG 3.11 with NetWare? PSS ID Number: Q119384 Article last modified on 08-18-1994
3.11
WINDOWS
| The information in this article applies to: |
| - Microsoft Windows for Workgroups version 3.11 |
SUMMARY
A “clean boot” (that is, starting your computer after all unnecessary commands have been removed from your CONFIG.SYS and AUTOEXEC.BAT files) is used as a basic troubleshooting step to test possible conflicts between Windows for Workgroups (WFWG) 3.11 and various terminate-and-stay-resident (TSR) programs and device drivers. There are different types of clean boots; the correct one to use depends on whether or not Windows for Workgroups has been installed.
MORE INFORMATION
Before Clean Booting
Create a bootable floppy disk that contains the MS-DOS system files and any other files that are required to make the system operational, such as disk- compression utilities (for example, Stacker), disk-partitioning drivers (for example, Disk Manager), and other third-party device drivers.
To Clean Boot Before Running Windows for Workgroups Setup
If you are not using any disk-compression software, disk-partitioning software, or other third-party drivers necessary to boot the computer, you can boot the machine from a floppy disk that contains only the MS-DOS system files–no CONFIG.SYS and AUTOEXEC.BAT files are required.
If your system does use disk-partitioning, disk-compression, or other third- party software that is required to boot the computer, the startup files on the disk created above should match the appropriate files below.
Using ODI Drivers [Novell NetWare 3.x or 4.x Shell]:
CONFIG.SYS ———-
FILES=45 BUFFERS=20 <Third-party disk-partitioning driver> <Third-party disk-compression driver> <Other required third-party driver>
AUTOEXEC.BAT ————
PROMPT <math display="inline">P</math>G CD<NetWare directory> LSL <ODI network card driver> IPXODI NETX <or VLM> CD
Using IPX.COM (Monolithic) [Novell NetWare 3.x Shell Only]:
CONFIG.SYS ———-
FILES=45 BUFFERS=20 <Third-party disk-partitioning driver> <Third-party disk-compression driver> <Other required third-party driver>
AUTOEXEC.BAT ————
PROMPT <math display="inline">P</math>G IPX NETX
To Clean Boot After Installing Windows for Workgroups with Novell NetWare as a Secondary Network ————————————————————————-
Using ODI Drivers [Novell NetWare 3.x or 4.x Shell]:
CONFIG.SYS ———-
FILES=45 BUFFERS=20 DEVICE=<WFWG 3.11 directory>.SYS PATH=C:;C: <Third-party disk-partitioning driver> <Third-party disk-compression driver> <Other required third-party drivers> SHELL=C:.COM /E:1024 /P LASTDRIVE=P <for NetWare 3.x> -or- LASTDRIVE=Z <for NetWare 4.x> STACKS=9,256 DEVICE=<WFWG 3.11 dir>.SYS
AUTOEXEC.BAT ————
<WFWG 3.11 directory> NET START PROMPT <math display="inline">P</math>G SET TEMP=C:<valid path> CD <NetWare directory> LSL <ODI network card drive> IPXODI <WFWG 3.11 directory>.EXE NETX <or VLM> CD
Using IPX.COM (Monolithic) [NetWare 3.x Shell Only]:
CONFIG.SYS ———-
FILES=45 BUFFERS=20 DEVICE=<WFWG 3.11 directory>.SYS PATH=C:;C: <Third-party disk-partitioning driver> SET TEMP=C:<valid path> <Third-party disk-compression driver> <Other required third-party drivers> SHELL=C:.COM /E:1024 /P LASTDRIVE=P STACKS=9,256 DEVICE=<WFWG 3.11 dir>.SYS
AUTOEXEC.BAT ————
<WFWG 3.11 dir> NET START PROMPT <math display="inline">P</math>G PATH C:;C: SET TEMP=C:<valid path> IPX NETX
Exceptions
The following are examples of drivers that should NOT be removed; these drivers are used to make the hard drive accessible when the computer is turned on. This is not a complete list, but it does include most of the commonly used drivers.
Hard disk drivers: SQY55.SYS, SSTBIO.SYS, SSTDRIVE.SYS, AH1544.SYS, ILIM386.SYS, ASPI4DOS.SYS, SCSIHA.SYS, SCSIDSK.EXE, SKYDRVI.SYS, ATDOSXL.SYS, NONSTD.SYS
Disk-partitioning drivers: DMDRVR.BIN, SSTOR.SYS, HARDRIVE.SYS, EDVR.SYS, FIXT_DRV.SYS, LDRIVE.SYS, ENHDISK.SYS
Disk-compression utilities: STACKER.COM, SSWAP.COM, SSTOR.EXE, DEVSWAP.COM, DBLSPACE.SYS
If the purpose of a device driver or program is unknown, do NOT remove it. Most device drivers and programs display a message describing the purpose when they are initialized.
What a Clean Boot Does Not Include
A clean boot does not include the following:
- DOS=HIGH,UMB
- EMM386.EXE
- INSTALL=SHARE.EXE
- INSTALL=FASTOPEN.EXE
- Third-party memory managers
- RAM disk devices
- JOIN, GRAPHICS, PRINT, SUBST, APPEND
- MODE for printer redirection
- Multiple path statements
- MS-DOS-level mouse drivers
- Third-party disk caches
- Various third-party TSRs
- LOGIMENU, CLICK
- Virus checkers
- Drivers for scanners/fax
- Drivers for CD-ROM/network
- Tape backup spoolers/redirectors/buffers
- Data acquisition units
- Keyboard accelerators/buffers
REFERENCES
More information about clean booting can be found on pages 153-154 of the Microsoft Workgroup Add-On for Windows version 3.11 “User’s Guide,” and in Chapter 13, pages 9-10 of the Microsoft Windows for Workgroups “Resource Kit Addendum for Operating System Version 3.11.”
For information about clean booting Windows 3.1, query on the following words in the Microsoft Knowledge Base:
clean and boot and win31
Additional reference words: 1.0 1.00 3.00 3.10 3.11 LAN Manager LANman clean-boot novel PRINT.COM RAMDRIVE.SYS JOIN.EXE PRINT.EXE MODE.COM GRAPHICS.COM SUBST.EXE win31 kbnetwork WFWG
=================================================================
Copyright Microsoft Corporation 1994.
