How MS-DOS 6.22 VERIFY Command Impacts Disk Safety

The VERIFY command in MS-DOS 6.22 is designed to ensure that data written to a disk can be read without input/output errors, providing a basic safeguard against recording media failures. However, while it is widely assumed to perform a comprehensive data validation, it does not compare the written data against the original data in memory. Instead, it merely confirms that the destination sectors are physically readable, offering limited write safety at the cost of disk performance.

How the VERIFY Command Works

When turned on via VERIFY ON, MS-DOS instructs the system BIOS to set a verification flag during disk write routines. Through interrupt INT 13h, MS-DOS writes the sector and immediately requests the disk controller to read the sector's Cyclic Redundancy Check (CRC) or Error Correction Code (ECC).

The controller validates that the newly written track and sector headers are structurally intact and that the checksum matches the recorded bits. If the controller encounters an unreadable sector or an invalid CRC/ECC, MS-DOS catches the error immediately and halts the operation, alerting the user before the original data is discarded from memory.

What VERIFY Does and Does Not Protect Against

The VERIFY command provides a specific layer of protection, but it does not guarantee complete data integrity:

• What it catches: It detects physical media defects, such as bad sectors on floppy disks or early hard drives, where the magnetic coating failed to record a readable magnetic transition.
• What it misses: It does not detect data corruption that occurred before the write took place. If data was corrupted in RAM, within the CPU, or along the bus before reaching the drive controller, the drive calculates a valid CRC/ECC for the corrupt data and writes it anyway. Because VERIFY does not perform a byte-for-byte comparison between disk and RAM, these errors pass undetected.

Performance Impact

Enabling VERIFY incurs a notable speed penalty. Because the drive head must wait for the disk platter or magnetic media to complete an additional rotation to reread the sector checksums, write throughput drops significantly—often by 30 to 50 percent depending on the drive geometry and transfer rate.

Practical Impact in MS-DOS 6.22

By the era of MS-DOS 6.22, hard drives using IDE (Integrated Drive Electronics) and SCSI interfaces had integrated internal, hardware-level ECC and sector-remapping mechanisms that operated automatically. Consequently, using VERIFY ON for hard drives added redundant latency with virtually no additional data protection. Its primary practical utility remained confined to removable media, particularly floppy disks, where surface degradation and read-after-write failures were frequent and hardware-level defect management was absent.