Microsoft KB Archive/124789

{|
 * width="100%"|

How to Create a "Clean Boot" Disk to Troubleshoot Problems

 * }

Q124789

-

The information in this article applies to:


 * Microsoft Visual C++, versions 1.0, 1.5, 1.51

-

SUMMARY
Conflicts may occur between Visual C++, terminate-and-stay-resident (TSR) programs, or device drivers under Windows and Windows for Workgroups. This article explains how to troubleshoot these problems by doing what is often called a "clean boot." To perform a "clean boot" means to remove all unnecessary commands from the CONFIG.SYS and AUTOEXEC.BAT files and restart the computer.

MORE INFORMATION
When a conflict occurs, you may encounter problems like these:


 * Corrupt or incomplete installations
 * Insufficient memory or file handles
 * Inexplicable error messages generated from the application
 * Complete inability to use the application successfully

Removing Commands from CONFIG.SYS and AUTOEXEC.BAT
If you have MS-DOS version 6.0 or later, you can press the F5 key at startup to completely bypass your CONFIG.SYS and AUTOEXEC.BAT commands, or you can press the F8 key to confirm each CONFIG.SYS command. You can also press and hold down the SHIFT key when MS-DOS displays the "Starting MS- DOS..." prompt to completely bypass your CONFIG.SYS and AUTOEXEC.BAT commands.

Otherwise, you can use a text editor such as MS-DOS EDIT, MS-DOS EDLIN, SYSEDIT.EXE, or Windows Notepad to edit your CONFIG.SYS and AUTOEXEC.BAT files. Follow the instructions given below.

NOTE: Before making changes to the files, make backup copies of the the AUTOEXEC.BAT and CONFIG.SYS files. You should also have a standby bootable floppy disk in case the computer fails to boot correctly.

Before Doing a Clean Boot
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, disk partitioning drivers, and other third-party device drivers.

Doing a Clean Boot Before Running Windows Setup
If there is no disk compression software, disk partitioning software, or other third-party drivers necessary to boot the computer, you can boot it by using a floppy disk that contains only the MS-DOS system files, without a CONFIG.SYS or AUTOEXEC.BAT file.

If disk partitioning, disk compression, or other third-party software is required to boot the computer, the AUTOEXEC.BAT and CONFIG.SYS files on the bootable floppy disk should contain the following lines:

"AUTOEXEC.BAT"   PROMPT $P$G "CONFIG.SYS"   FILES=50 BUFFERS=30 &lt;Third-party disk partitioner&gt; &lt;Third-party disk compression driver&gt; &lt;Other required third-party driver&gt;

Windows Clean Boot
After Windows is installed, the AUTOEXEC.BAT and CONFIG.SYS files on the bootable floppy disk should contain the following lines:

"AUTOEXEC.BAT"   PROMPT $P$G PATH=C:\WINDOWS;C:\DOS;C:\ SET TEMP=C:\ "CONFIG.SYS"   FILES=50 BUFFERS=30 DEVICE=C:\ \HIMEM.SYS    STACKS=9,256 SHELL=C:\ \COMMAND.COM /E:1024 /P

Windows for Workgroups Clean Boot
After Windows for Workgroups version 3.1 is installed, the AUTOEXEC.BAT and CONFIG.SYS files on the bootable floppy disk should contain the following lines:

"AUTOEXEC.BAT"   NET START PROMPT $P$G PATH C:\Windows;C:\DOS;C:\ SET TEMP=C:\ "CONFIG.SYS"   FILES=50 BUFFERS=30 DEVICE=C:\\HIMEM.SYS    DEVICE= \PROTMAN.DOS /I: DEVICE=.DOS DEVICE= WORKGRP.SYS SHELL=C:\ \COMMAND.COM /E:1024 /P STACKS=9,256 After Windows for Workgroups version 3.11 is installed, the AUTOEXEC.BAT and CONFIG.SYS files on the bootable floppy disk should contain the following lines:

"AUTOEXEC.BAT" <pre class="CODESAMP">  <WFWG 3.11 dir>NET START PROMPT $P$G PATH=C:\Windows;C:\DOS;C:\ SET TEMP=C:\ "CONFIG.SYS" <pre class="CODESAMP">  FILES=50 BUFFERS=30 DEVICE=C:\<WFWG 3.11 dir>\HIMEM.SYS <Third-party disk partitioner> <Third-party disk compression driver> <Other required third-party drivers> DEVICE=<WFW 3.11 dir>IFSHLP.SYS SHELL=C:\ \COMMAND.COM /E:1024 /P STACKS=9,256

Exceptions
The following are examples of drivers that SHOULD NOT be removed; they are used when the computer is turned on to make the hard drive accessible. This is not a complete list, but it does include many frequently used drivers:

<pre class="FIXEDTEXT">  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 Partitioners:         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 If the purpose of a device driver or program is unknown, DO NOT remove it. Most device drivers and programs will display a message describing their purpose when they are initialized. A clean boot DOES NOT include:


 * DOS=HIGH,UMB
 * EMM386.EXE
 * INSTALL=SHARE.EXE
 * INSTALL=FASTOPEN.EXE
 * Third-party memory managers
 * RAM disk devices, such as RAMDRIVE.SYS
 * JOIN.EXE, GRAPHICS.COM, PRINT.COM, SUBST.EXE, APPEND
 * MODE.COM 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

Additional Troubleshooting Steps
<ol> <li>Verify that the File Allocation Table is valid:

<ol style="list-style-type: lower-alpha;"> <li>Exit Windows.</li> <li> At the command prompt, type the following: "chkdsk /f" CAUTION: You must exit Windows BEFORE you type the above command. CHKDSK will also check the directory structure. </li></ol> </li> <li>Verify that you are using the correct version of MS-DOS for your computer. For example, if you are using a COMPAQ computer, you should be using a version of COMPAQ MS-DOS.</li> <li> Verify that the path, environmental space, and TEMP directory are valid. At the command prompt, type: "set"</li></ol>

Reinstall Windows after you make the above changes to the CONFIG.SYS and AUTOEXEC.BAT files.