How Windows 95 (Chicago) Revolutionized the PC Era: Origins, Architecture, and Impact

Origin and Project Naming

In early 1992 the Windows team concluded development of Windows 3.1 and defined a new strategy to dominate desktop, notebook and emerging pen‑based devices, leaving servers and workstations to the NT team. Three technical challenges were identified: user‑interface design, hardware support, and networking.

Microsoft launched a series of internal projects that later merged into the code‑name Chicago , which became Windows 95:

Cougar – a new 32‑bit protected‑mode kernel intended as the evolution of the Windows 3.x 386 kernel.

Panther – integration of the Win32 API into the Cougar kernel.

Rover – a mobile‑device variant of Cougar/Panther.

NT – the professional workstation/server line, first shown in July 1993.

Cairo – an upgrade to NT that incorporated many Cougar/Panther innovations.

Cougar and Panther together formed the core of Chicago, providing a 32‑bit protected‑mode kernel capable of dynamically loading and unloading device drivers while preserving compatibility with existing MS‑DOS applications.

System Architecture

Chicago’s architecture built on the Windows for Workgroups 3.1 386 model but added a full set of virtual device drivers (VxDs) and virtual DOS machines (VDMs) to run both legacy 16‑bit software and new 32‑bit code.

The three principal VxDs were:

VMM32.VXD – memory management, event handling, interrupt processing, driver loading, virtual‑machine creation and task scheduling.

CONFIGMG.VXD – plug‑and‑play (PnP) support.

IFM.VXD – file‑system coordination, disk buffering and a 32‑bit protected‑mode I/O path that bypasses MS‑DOS.

Key binary components were split between 16‑bit and 32‑bit modules:

Kernel: KRNL386.EXE, KERNEL32.DLL, VWIN32.VXD – responsible for memory, process and file‑system management.

User interface: USER.EXE, USER32.DLL – window management, controls and dialog handling.

Graphics: GDI.EXE, GDI32.DLL – the Graphics Device Interface for device‑independent drawing.

Unlike earlier Windows releases, MS‑DOS was no longer resident in memory. All 16‑bit DOS applications were redirected to 32‑bit Chicago routines, and DOS programs could run without DOS‑specific drivers, giving Windows 95 three operational modes: native DOS (via VDM), Win16, and Win32.

Design Process and User‑Experience Focus

By the end of 1992 Windows 3.x had sold over 50 million copies. Microsoft assembled a roughly 24‑person team (half designers, half programmers) and adopted an iterative development model rather than a linear waterfall approach. The cycle consisted of:

Idea generation and rapid prototyping.

User testing in Microsoft labs with both novice and experienced participants.

Collection of concrete feedback (e.g., “Can you complete task X after ten minutes?”).

Refinement of UI elements such as the start menu, taskbar and file‑dialog boxes.

Release of a public beta to gather broader feedback before final shipping.

Release Timeline and Technical Impact

Windows 95 shipped on 24 August 1995 at a retail price of US $210. Key technical innovations that reshaped the PC market included:

Integrated plug‑and‑play support, allowing automatic detection and configuration of ISA and PCI devices.

Transition from ISA to PCI as the dominant expansion bus, eliminating manual jumpers and DIP switches.

Full 32‑bit Win32 API, enabling a new generation of high‑performance applications and games.

Improved memory management and multitasking through the protected‑mode kernel.

Retention of a small 16‑bit compatibility layer to preserve legacy software support.

Within four days of launch one million copies were sold; the first year saw roughly 40 million units shipped, confirming the rapid adoption of the new platform.

Legacy

Chicago’s combination of Windows 3.1 compatibility, a robust Win32 API, and PnP hardware handling closed the usability gap with competing operating systems such as the Macintosh. The architecture set the foundation for subsequent Windows releases and accelerated the decline of ISA‑only hardware, OS/2 and early Linux distributions on consumer PCs.