Checking for Conflicts at System Startup

If a computer fails to start Windows 95, try the following tasks:

• Check for upper memory area conflicts. If you suspect an upper memory conflict, use win /d:x to start Windows 95.
• Check whether Safe Mode resolves the problem. To verify whether loading minimal drivers will resolve the problem, use F5 or win /d:m to start Windows 95.
• Check for conflict with 32-bit disk access. If you don't want to load 32-bit disk access, use win /d:f to start Windows 95.
• Check for hard disk I/O conflicts. If you want to force VirtualHDIRQ=Off, use win /d:v to start Windows 95. For more information, see "Using WIN.COM Switches" earlier in this chapter.
• Check for and remove unnecessary drivers and TSRs, and retry.
• Check for device conflicts by using Device Manager in the System option in Control Panel.
• Check for an outdated or damaged VxD by examining the BOOTLOG.TXT and then do the following:
  • If it is in the Windows SYSTEM\IOSUBSYS directory, rename it.
  • If it has a .386 filename extension, examine the [386Enh] section of SYSTEM.INI and remark out its lines. When renaming VxDs, be sure to change the .VXD extension. Windows 95 loads all files that in the IOSUBSYS subdirectory that have a .VXD extensions.
  • If it is in VMM32.VXD, check the Windows SYSTEM\VMM32 directory for a VMM32 file, and rename or move it.