Windows 95 Hardware Detection Log File Explained

During the installation of Windows 95, the operating system relied on automated routines to probe system components, saving the hardware discovery records directly to a file named DETLOG.TXT. This article explains the purpose of DETLOG.TXT, details the specific hardware information it captured, and explores how Windows 95 used this file alongside recovery mechanisms to navigate system crashes during setup.

The Role of DETLOG.TXT

The primary setup file responsible for maintaining information about hardware detected during Windows 95 installation is DETLOG.TXT. Created in the root directory of the primary boot drive (typically C:\DETLOG.TXT), this hidden plain-text file served as a real-time record of the operating system's hardware detection phase.

When Windows 95 launched its detection routines, it checked for legacy non-Plug and Play devices, existing configurations, and newly introduced Plug and Play peripherals. Every step of this hardware interrogation was written to DETLOG.TXT as it occurred.

Information Stored in the Log

DETLOG.TXT recorded technical parameters for every system component identified by setup detection modules, including:

  • Device Classes and Identification: Information regarding the motherboard chipset, bus architectures, display adapters, storage controllers, network cards, sound cards, and communication ports.
  • Resource Allocations: Specific hardware resource requests, including Interrupt Request lines (IRQs), Input/Output (I/O) port addresses, Direct Memory Access (DMA) channels, and memory ranges.
  • Detection Modules: The specific software routines (such as dynamic link libraries used by setup) invoked to identify specific classes of hardware.
  • Verification Results: Indicators showing whether a hardware probe was successful, inconclusive, or skipped due to user intervention or known conflicts.

Error Recovery with DETCRASH.LOG

Hardware probing in 1995 often involved direct queries to legacy ISA cards, which frequently caused computer systems to lock up or reboot unexpectedly. To handle these failures, the Windows 95 Setup program operated a recovery system:

  1. Setup opened DETLOG.TXT and flushed each detection step to the disk before attempting to probe a specific hardware address.
  2. If the machine froze, a secondary binary file called DETCRASH.LOG recorded the exact detection sub-routine that was active when the failure occurred.
  3. Upon restarting the system and relaunching Setup, the installer read DETCRASH.LOG to skip the fatal probe, while DETLOG.TXT updated to reflect the bypassed test.

DETLOG.TXT vs. SETUPLOG.TXT

While DETLOG.TXT focused exclusively on hardware discovery, it worked in tandem with SETUPLOG.TXT.

SETUPLOG.TXT recorded the broader installation process, including choices made in the setup wizard, file copy operations, directory creations, and registry initialization steps. For troubleshooting device detection failures or hardware conflicts, administrators and technicians relied specifically on DETLOG.TXT to determine which device interrupted the installation process.