FreeDOS DISKCOPY: Floppy Media, Images, Verification, and Destructive Edges

FreeDOS DISKCOPY is more than a floppy-to-floppy command: its project documentation also describes image-file input and output, selectable buffering strategies, read/write verification, and an error-recovery mode. Those options change what the result means. In particular, fast mode can produce an image whose files are equivalent to the source while the disk layout is not byte-for-byte identical. Choose the operation from the preservation goal, not from the shortest command line.

Treat every disk-copy command as a source/destination operation that can overwrite valuable media. Confirm the drive letters, insert the correct source and destination, and keep an independent image or backup when the original matters. A command that finishes without an error does not by itself prove a forensic sector clone, a readable long-term archive, or application-level correctness.

Identify whether each operand is a drive or an image

The FreeDOS help describes a drive operand such as A: as a floppy device and a non-drive operand as an image file. DISKCOPY can copy from a drive to an image, from an image to a drive, or between image files. Read the command help for the installed build because options and implementation details can change. Never rely on visual similarity between A: and a path to identify which argument will be overwritten.

For a two-drive copy, explicitly supply both letters after checking them. For a one-drive system, the program reads from the source, then asks the operator to exchange media before writing the destination. Wait for the prompt and verify the physical disk label each time. Mixing the source and destination disks during this sequence can silently reverse the intended operation.

An image is still a file on a filesystem. Ensure the host drive has enough free space, that the output name does not already identify an important file, and that the image destination is not on the floppy being read unless the workflow intentionally handles that layout. The FreeDOS documentation’s own same-drive image example warns that the output file is not included in the image being created, and insufficient memory can prevent the copy.

Select copy fidelity before selecting speed

The /F fast option copies only sectors considered filled. The FreeDOS help explicitly warns that this produces a destination that is not exactly the same as the original, even though the files are said to be identical. That may be useful for a compact image or a file-oriented migration, but it is the wrong default for preserving unused sectors, deleted-data remnants, boot-area slack, or a byte-for-byte acquisition.

Do not describe an /F image as a raw, complete floppy image. Its omitted sectors are part of the distinction. If the requirement is exact media preservation, use a tested acquisition method that reads and records every sector, including failures, and validate the output independently. DISKCOPY may be convenient for ordinary disk duplication; convenience does not make every mode forensic.

The default copy path may use XMS, EMS, buffers, or a swap file, according to the project help. /M restricts the operation to memory-based resources such as XMS, EMS, or buffers. /I reports which kind of memory is used. These switches affect resource requirements, not the meaning of the image. If the program cannot hold the data needed for a copy, choose another supported strategy rather than assuming that adding /M makes a larger disk fit.

Verification and recovery options are not guarantees

/V requests verification of reads and writes. The documentation says this takes about twice as long and does not change DOS’s global VERIFY setting. Verification improves confidence that the operation completed according to the utility’s read/write checks, but it is not a cryptographic checksum of every logical file and does not prove that the source was correct.

/R requests disk error-recovery mode and asks the program to scan more effectively for media errors. It can attempt to copy more readable data from a damaged source. That is not a guarantee of recovery, and additional reads can stress deteriorating media. Preserve the source first when possible. For an irreplaceable disk, prefer an imaging workflow with a map of unreadable regions so the first pass can prioritize recoverable data and later retries can be controlled.

If an image file already exists, /O permits overwriting it. Treat this as a destructive choice: verify the destination filename and preserve any previous image before using the option. /T suppresses a media-change prompt when writing an image to the same physical disk that contains it. The FreeDOS help explicitly warns that the image file can be erased by that operation. Do not use /T without checking where the image is stored and documenting that the source file is expendable.

A controlled workflow

First read the installed command’s syntax and list the source and destination. A normal image capture with read/write verification can be expressed as:

diskcopy a: archive.img /v /x

This is an illustrative command, not an exact-sector forensic acquisition. /X tells the utility to exit automatically rather than asking whether another copy should be made; /V requests verification. Confirm that archive.img resolves to the intended healthy destination and that the output drive has capacity. If the image name already exists, stop and decide explicitly whether to preserve or replace it.

For an image restore, reverse the operands only after checking the target disk identity:

diskcopy archive.img a: /v

This overwrites the destination disk’s contents. The command does not offer a safe preview of which files or sectors will be changed. Keep the original image immutable and use expendable media for restoration tests. If the image is on drive A: and the destination is also A:, do not use /T casually; the documented behavior can erase the image before it is read.

After capture, record the exact command, DISKCOPY version, source identification, destination path, filesystem free space, verification setting, and any read errors. Hash the finished image using an independent checksum utility and store the digest separately. A hash proves that the image file remains unchanged between checks; it does not prove that the image fully represents the original disk. For fast /F output, mark the result as a compact file-equivalent image rather than an exact media clone.

Legacy format and interoperability limits

The FreeDOS help lists supported diskette capacities and says DISKCOPY uses a format compatible with the Linux rawrite utility. It also notes that DISKCOPY cannot read from or overwrite Linux floppy disks, although it can write a Linux floppy image to a DOS disk. Treat these as statements about the documented FreeDOS implementation, not universal claims about every raw-image program or physical drive.

Hardware, controller firmware, emulator configuration, and floppy geometry all affect whether a medium can be read. If the command reports a geometry or media error, do not repeatedly switch formats or apply a write operation to the only copy. Record the error, verify drive type and diskette density, and use a supported controller or a dedicated imaging tool when the preservation objective exceeds DISKCOPY’s documented workflow.

Do not combine ASSIGN with DISKCOPY. FreeDOS’s ASSIGN documentation explicitly lists DISKCOPY among commands that must not be used with drive remapping. Clear unexpected drive assignments before operating on floppy media, then verify the drive map again. This eliminates a subtle way to read or overwrite a different physical device than the operator intended.

Acceptance checks

Before ending a copy, confirm the source and destination roles, exact mode (/F or full copy), whether /V was enabled, and whether errors occurred. For ordinary duplication, compare directory listings and open important files on the destination. For archival preservation, use a full-sector image method and a separate digest; DISKCOPY’s fast mode is specifically not a byte-equivalence claim.

FreeDOS DISKCOPY is practical for controlled legacy floppy operations and supported image workflows. Reliable use depends on distinguishing byte fidelity from file equivalence, verifying the destructive destination, preserving source evidence, and reading the installed utility’s documentation before relying on a switch.

Related:

Sources: