Role of BOOTLOG.TXT in Windows 95 Troubleshooting

In Windows 95, the BOOTLOG.TXT file served as an essential diagnostic record that logged every step of the operating system's startup sequence in chronological order. By tracking the initialization of real-mode drivers, Virtual Device Drivers (VxDs), and core system components, it allowed users and technicians to pinpoint the exact hardware conflict, corrupted file, or driver failure that prevented the operating system from booting normally.

Generation and Location

The BOOTLOG.TXT file was located in the root directory of the boot drive (C:\BOOTLOG.TXT). It was not generated automatically during a standard boot unless configured to do so. Users typically created it by pressing F8 during the initial "Starting Windows 95..." prompt to access the Windows 95 Startup Menu and selecting Logged (\BOOTLOG.TXT). Alternatively, administrators could trigger its creation by running the WIN /B command from MS-DOS or by adding BootKeys=1 and BootLog=1 to the hidden MSDOS.SYS configuration file.

How the Log Recorded Information

The file tracked each step of the startup sequence as a paired event: an attempt to load a component, followed immediately by the result of that attempt. The log documented several distinct phases of the boot process:

  1. Real-Mode Drivers: Captured components loaded via CONFIG.SYS and AUTOEXEC.BAT, reporting lines such as Loading Device = followed by LoadSuccess = or LoadFailed =.
  2. Virtual Device Drivers (VxDs): Documented 32-bit protected-mode drivers required for Windows 95 subsystem hardware access. Entries appeared as Loading Vxd = [DriverName] followed by LoadSuccess = [DriverName] or LoadFailed = [DriverName].
  3. Core System Files and Shell: Recorded the initialization of core graphics, fonts, and system resources such as GDI.EXE, USER.EXE, and the Desktop shell (EXPLORER.EXE).

Identifying Boot Failures

When Windows 95 froze, crashed, or displayed a blue screen during boot, technicians would restart the machine in Safe Mode or boot to a DOS command prompt to inspect BOOTLOG.TXT using a text viewer like EDIT.COM.

Troubleshooting focused on identifying two key patterns:

  • Explicit Failures: Searching the file for the string LoadFailed or Status = Failure. A failed load pointed directly to missing, damaged, or incompatible .386, .SYS, or .VXD files.
  • Hanging Components: In many crash scenarios, Windows 95 locked up entirely before a failure could be logged. In these cases, the problem component was identified by navigating to the very bottom of BOOTLOG.TXT. The last entry showing a Loading action without a corresponding LoadSuccess entry indicated the exact driver or device responsible for freezing the system.

Once the offending driver was identified via the log, users could disable the associated hardware in Device Manager, rename the conflicting file from DOS, or reinstall the corrupted system component to restore stability.