Windows 3.11 System Driver Reference Files

In Microsoft Windows 3.11, the primary system file responsible for storing dynamic link references and initialization directives for system drivers is SYSTEM.INI. Because Windows 3.11 relied heavily on modular Dynamic Link Libraries (DLLs) and Virtual Device Drivers (VxDs) to communicate with hardware, SYSTEM.INI acted as the central configuration catalog. This article details the structure of SYSTEM.INI, how it linked system drivers to hardware subsystems, and the key sections responsible for loading these drivers into memory.

The Role of SYSTEM.INI in Windows 3.11

Windows 3.11 operated as a 16-bit graphical operating environment running on top of MS-DOS, with 32-bit enhancements available in 386 Enhanced Mode. Rather than embedding hardware communication directly into the kernel, Windows utilized modular driver files (typically carrying .DRV or .386 extensions) that functioned as dynamic link libraries.

To resolve which DLL or driver executable to load for each hardware interface, the Windows loader read text directives from SYSTEM.INI located in the main C:\WINDOWS directory.

Core Driver Sections in SYSTEM.INI

The configuration file was organized into distinct bracketed sections that handled specific dynamic driver assignments:

  • [boot]: This section declared core 16-bit system drivers required to boot the graphical environment. Key entries included:
    • display.drv: Dynamically linked the video driver (e.g., VGA, SVGA).
    • mouse.drv: Referenced the pointing device driver.
    • keyboard.drv: Linked the keyboard translation driver.
    • system.drv: Handled the underlying computer hardware abstraction.
    • comm.drv: Managed serial communication ports.
    • drivers=: Pointed to dynamic libraries such as mmsystem.dll for multimedia support.
  • [386Enh]: Used when running in 386 Enhanced Mode. This section listed 32-bit Virtual Device Drivers (VxDs) using directives such as device=*vxdname or paths to external .386 files (e.g., device=vshare.386 or network drivers like ifshlp.sys). These drivers virtualized hardware access for multi-tasking DOS and Windows applications.
  • [drivers]: Often used for installable driver references, including multimedia, MIDI, and waveform audio devices mapped dynamically through the Control Panel.

Complementary Files

While SYSTEM.INI was the definitive source for low-level system driver bindings:

  • CONTROL.INI stored user-level driver descriptions and mappings configured via the Windows Control Panel.
  • WIN.INI managed user preferences, desktop environments, and application-specific settings rather than hardware-level dynamic links.

Before the Windows Registry replaced decentralized initialization files in Windows 95, SYSTEM.INI served as the foundational link table connecting Windows 3.11 to its dynamic driver architecture.