Windows 98 Startup Disks for System Recovery

Microsoft Windows 98 utilized an enhanced, floppy-based Emergency Startup Disk (ESD) to provide users with a reliable environment for diagnosing, repairing, and reinstalling compromised systems. This article details how Windows 98 created these startup disks, the innovative features they introduced—most notably native CD-ROM support and RAM drive utilization—and the specific command-line utilities bundled to restore unbootable computers.

Creation of the Startup Disk

Users were prompted to create an Emergency Startup Disk during the initial setup of Windows 98. Alternatively, a disk could be generated at any point through the Control Panel by navigating to Add/Remove Programs and selecting the Startup Disk tab. The operating system formatted a high-density 3.5-inch floppy disk (1.44 MB) and copied a minimal MS-DOS 7.1 environment along with critical diagnostic executables.

The RAM Drive and Compressed Utilities

Because a standard floppy disk had limited capacity, Windows 98 could not store all necessary diagnostic tools in uncompressed form alongside the operating system kernel. To bypass this limitation, Windows 98 introduced a dynamic RAM drive mechanism:

  1. Boot Initialization: Upon booting, CONFIG.SYS loaded HIMEM.SYS (extended memory manager) and RAMDRIVE.SYS, creating a temporary virtual disk in the computer’s RAM (typically assigned the drive letter immediately following the primary partitions).
  2. Decompression: The startup sequence extracted EBD.CAB (Emergency Boot Disk cabinet file) directly to the RAM drive using the EXTRACT.EXE utility.
  3. Execution: This gave users immediate access to advanced diagnostic and repair tools running entirely from RAM, preventing disk-swapping and speeding up command execution.

Native CD-ROM Drivers

The most significant advancement in the Windows 98 startup disk over its Windows 95 predecessor was universal CD-ROM support. Previous recovery methods required users to manually find, configure, and install real-mode DOS drivers for their specific CD drive brand.

Windows 98 resolved this by including standard ATAPI (IDE) and SCSI CD-ROM drivers directly on the disk. During boot, users were presented with a boot menu:

  • Start computer with CD-ROM support.
  • Start computer without CD-ROM support.
  • View the Help file.

Selecting CD-ROM support loaded generic drivers along with MSCDEX.EXE (Microsoft CD-ROM Extensions), enabling the system to access optical media immediately. This made it possible to run Windows setup directly from the installation CD (setup.exe) on a machine with a corrupted or newly formatted hard drive.

Core Recovery Utilities

The Windows 98 startup disk included several command-line utilities targeted at specific failure points:

  • SCANDISK.EXE: Checked and repaired File Allocation Table (FAT16 and FAT32) file system errors and surface defects on the hard drive.
  • FDISK.EXE: Managed hard drive partitions, allowed repartitioning, and included the undocumented /mbr switch (fdisk /mbr) to repair corrupted Master Boot Records infected by boot-sector malware.
  • FORMAT.COM: Prepared partitions for fresh installations by creating a clean FAT16 or FAT32 file system.
  • SYS.COM: Transferred core system files (IO.SYS, MSDOS.SYS, and COMMAND.COM) to the primary drive to restore bootability without wiping user data.
  • EXTRACT.EXE: Allowed advanced users to manually extract missing or corrupted individual system files from the .CAB archives located on the Windows 98 installation CD.

The Recovery Workflow

When Windows 98 suffered a catastrophic boot failure, the user inserted the floppy disk into drive A: and ensured the BIOS boot order prioritized the floppy drive. Once booted into the MS-DOS environment, the user could run SCANDISK to fix filesystem corruption, rewrite boot records with SYS C:, or, in cases of total system failure, reformat the drive and launch SETUP.EXE from the CD-ROM drive to perform a clean operating system installation.