Disk compression

From Wikipedia, the free encyclopedia
  (Redirected from SuperStor)
Jump to: navigation, search

A disk compression software utility increases the amount of information that can be stored on a hard disk drive of given size. Unlike a file compression utility which compresses only specified files - and which requires the user designate the files to be compressed - a disk compression utility works automatically without the user needing to be aware of its existence.

When information needs to be stored to the hard disk, the utility will compress the information. When information needs to be read, the utility will decompress the information. A disk compression utility overrides the standard operating system routines. Since all software applications access the hard disk using these routines, they continue to work after disk compression has been installed.

Disk compression utilities were popular especially in the early 1990s, when microcomputer hard disks were still relatively small (20 to 80 megabytes). Hard drives were also rather expensive at the time, costing roughly 10 USD per megabyte. For the users who bought disk compression applications, the software proved to be in the short term a more economic means of acquiring more disk space as opposed to replacing their current drive with a larger one. A good disk compression utility could, on average, double the available space with negligible speed loss. Disk compression temporarily fell into disuse by the late 1990s, as advances in hard drive technology and manufacturing led to increased capacities and lower prices.

With the advent of solid state disk technology in the late 2000s, disk compression again garnered interest. SSDs offered extremely fast disk read and write times (especially for random writes which are very taxing to traditional, spinning platter hard drives). However, the speed gains of SSDs came at an exponential increase in cost compared to mechanical hard drives. Most tablets that started shipping in the late 2000s also integrated SSDs for their underlying storage, and these could not be upgraded or replaced; again creating fresh demand for disk compression solutions.

Note: While the most familiar disk compression utilities were designed to work on DOS systems, the concept was not specific to DOS. The utility DiskDoubler, for example, worked on the Apple Macintosh platform.

Common disk compression utilities[edit]

Standalone utilities[edit]

The initial compression utilities were sold independently. A user had to specifically choose to install and configure the software.

  • Stacker from Stac Electronics
  • XtraDrive from Integrated Information Technology ( IIT)
  • SuperStor Pro from AddStor
  • DoubleDisk Gold from Vertisoft Systems
  • DiskDoubler from Salient Software

As of the late 2000s, with the new need for SSD compression, on both stand-alone SSDs purchased by consumers, and fixed SSDs integrated into tablets alike; brand-new disk compression utilities emerged - which were designed to work with modern versions of Windows.

  • ZIPmagic from Simon King`s Utilities Group

Bundled utilities[edit]

The idea of bundling disk compression into new machines appealed to resellers and users. Resellers liked that they could claim more storage space; users liked that they did not have to configure the software. Bundled utilities included:

  • DR DOS 6.0, from Digital Research, included a version of SuperStor.
  • PalmDOS 1.0, from Novell (after acquiring Digital Research), included a DPMS-enabled version of SuperStor.
  • MS-DOS 6.0 and MS-DOS 6.2, from Microsoft, included DoubleSpace, which was based in part on Vertisoft Systems' DoubleDisk.
  • PC DOS 6.1, from IBM, included a version of SuperStor.
  • MS-DOS 6.22, from Microsoft, included DriveSpace, which was DoubleSpace with a different compression algorithm.
  • PC DOS 6.3, from IBM, included a version of SuperStor.
  • Novell DOS 7, from Novell (after acquiring Digital Research), included a DPMS-enabled version of Stacker 3.12.
  • PC DOS 7.0, from IBM, included a DPMS-enabled version of Stacker 4.02 from Stac Electronics.
  • OpenDOS 7.01, from Caldera (after acquiring Novell DOS), included a DPMS-enabled version of Stacker 3.12.
  • DR-DOS 7.02/7.03, from Caldera, included a DPMS-enabled version of Stacker 3.12.
  • PC DOS 2000, from IBM, included a DPMS-enabled version of Stacker 4.02.
  • Windows 95, from Microsoft, included an updated version of DriveSpace.
  • Plus!, from Microsoft, included DriveSpace 3.

Other utilities[edit]

While Windows NT, from Microsoft, included both a native support and a command line utility named 'compact' that compresses files on NTFS systems, that is not implemented as a separate "compressed drive" like those above.

How disk compression works[edit]

Disk compression usually creates a single large file, which becomes a virtual hard drive. This is similar to how a single physical hard drive can be partitioned into multiple virtual drives. The compressed drive is accessed via a device driver.

On more modern versions of Windows, the approaches to disk compression are similar. WIMBoot technology, debuting with Windows 8.1 Update 1, uses a single large file as before; with compressed data accessible through a driver. Data deduplication technology, debuting with Windows Server 2012, compresses on-disk data dynamically without creating a separate container file; data is not compressed on a per-file basis but across the entire disk as if it were a single file (providing significant compression gains). NTFS compression technology, debuting with Windows NT 3.1, also compresses on-disk data dynamically, but compression is performed on a per-file basis only.

Compressing existing drives[edit]

All drives would initially be empty. The utility to create a drive would usually offer to "compress a current drive". This meant the utility would:

  1. Create an empty compressed drive, stored on the existing drive.
  2. Transfer existing files on the old drive to the new compressed drive.
  3. Increase the size of the new compressed drive as necessary to accommodate more files and allow empty space when done.
  4. When all files were transferred, the drive letters would be swapped.

Usually certain system files would not be transferred. For example, OS swap files would remain only on the host drive.

Compressing the boot drive[edit]

Note that the device driver had to be loaded to access the compressed drive. A compressed drive C: required changes to the boot process as follows:

  1. BIOS loads sector 0 of the first physical hard drive (partition sector)
  2. Partition sector loads sector 0 of the bootable partition. In this case, it's the host drive.
  3. Host drive sector 0 loads (in the case of MS-DOS) IO.SYS and begins Config.Sys processing
  4. Compression device driver is loaded. Compressed drive becomes C; host drive usually became F.
  5. Processing continues from compressed drive.

Performance Impacts[edit]

On systems with slower hard drives, disk compression could actually increase system performance. This was accomplished two ways:

  1. Once compressed, there was less data to be stored.
  2. Disk accesses would often be batched together for efficiency.

If the system had to frequently wait for hard drive access to complete (IO bound) converting the hard drive to compressed drives could speed up the system significantly. Compression and decompression of the data will increase the CPU utilization. If the system was already CPU bound, disk compression will decrease overall performance.


Some common drawbacks to using disk compression:

  • Not all compression utilities would confirm the absence of errors in the file system before compressing a disk in place. Some errors, such as crosslinked files, could result in additional data loss during the transfer process. [1]
  • The compressed drive is only visible if the device driver is loaded and the compressed drive is mounted. A boot disk, for example, might not contain the driver.
  • Users did not always realize that the large file on the host drive contained the compressed drive. While it was usually "hidden" by default,[2] users who did find the large file curious or suspicious were able to delete it. This would normally result in data loss.

See also[edit]

External links[edit]


  1. ^ In crosslinked files, two files are storing at least part of their data in the same location. At least part of one file (the "bad" file) is always lost in this instance. However, if the "bad" file is copied and then deleted, part of the "good" file is deleted as well. Microsoft ScanDisk was created, in part, to perform a better check of the file system prior to compression than the old MS-DOS CHKDSK utility.
  2. ^ For example, DOS associated up to four attributes with files: System, Hidden, Read-Only, and Archivable. Files with the System or Hidden attributes are often not displayed by default. Files with the System or Read-Only attribute cannot be deleted with the "Erase" (or "Del") DOS command. Most compression utilities would mark the drive file with at least one or more of the System, Hidden, and Read-Only attributes (many would use all three). However, files marked with such attributes can be viewed and deleted by other means. In addition, the user can also remove attributes.