Windows 95 Floppy Disk Compression with DriveSpace

During the mid-1990s, the standard 1.44 MB floppy disk struggled to accommodate increasingly large files and applications. Windows 95 addressed this storage limitation through DriveSpace, a disk compression utility, alongside ScanDisk, a disk analysis and repair tool. Together, these utilities allowed users to nearly double the capacity of removable floppy media to roughly 2.8 MB by converting physical media into transparently compressed virtual drives while actively maintaining file system integrity.

The Compressed Volume File (CVF)

DriveSpace did not compress individual files one by one on the floppy disk's native file system. Instead, it converted the entire disk structure into a single, hidden container file called a Compressed Volume File (typically named DRVSPACE.000).

When a user compressed a floppy disk:

  1. DriveSpace created DRVSPACE.000 on the physical disk (referred to as the "host" drive).
  2. The operating system mounted this container file as a virtual drive using the original drive letter (usually A:).
  3. Any read or write request sent to A: passed through the DRVSPACE.BIN driver, which compressed or decompressed data on the fly using a variation of the Lempel-Ziv (LZ) algorithm (specifically Microsoft Real-Time Compression Interface, or MRCI).

Because files were packaged together inside the CVF, Windows 95 bypassed the traditional cluster waste common to standard FAT file systems, packing fragmented pieces of data far more tightly than a standard 1.44 MB format allowed.

Seamless Mounting and Portability

Windows 95 introduced an automount feature for removable media. When a user inserted a compressed floppy, the operating system checked the disk’s boot sector and root directory. If DRVSPACE.000 was present, the system automatically mounted the CVF to drive A: without requiring the user to open a utility or restart the computer.

If the floppy was inserted into another computer running Windows 95 or MS-DOS 6.22 (which included DoubleSpace/DriveSpace drivers), the disk mounted automatically. However, systems lacking these drivers would only see the uncompressed host partition containing a small READ.ME text file and the locked DRVSPACE.000 archive.

The Dual Role of ScanDisk

Because DriveSpace separated physical storage from the virtual file system, disk corruption could occur at two distinct levels: the physical floppy surface or inside the virtual file system within the CVF. Windows 95 modified ScanDisk to handle this dual architecture natively.

When checking a compressed floppy, ScanDisk executed a two-stage diagnostic process:

  • Host Drive Verification: ScanDisk first scanned the physical media for standard magnetic degradation, bad sectors, and defects. It ensured that the DRVSPACE.000 file itself was completely readable and situated on physically intact sectors.
  • Internal Structure Analysis: ScanDisk then inspected the internal structures inside the CVF. Standard disk utilities could not interpret the modified File Allocation Table (MDFAT) used within a DriveSpace volume. ScanDisk verified the internal FAT entries, reconciled discrepancies between compressed sector sizes and allocated clusters, and fixed cross-linked compressed files.

Through this coordinated approach, DriveSpace maximized the physical constraints of floppy media while ScanDisk prevented data loss caused by the higher vulnerability of densely packed, compressed sectors on magnetic disks.