Choose the level of preservation
A file copy preserves visible files. A sector image also represents filesystem structures, boot sectors and partition layout. A floppy flux capture records lower-level magnetic transitions for analysis of formats that ordinary sector reads may not describe. Choose the method for the evidence you need rather than calling every copied directory a full disk backup.
The Greaseweazle project documents flux capture through a supported drive and USB interface. Its image-format reference distinguishes supported representations. A flux file is not automatically a DOS-mountable image. Keep the original capture and any decoded sector image separately.
Identify drive and media requirements
Record disk label, physical size, density, write-protect state and damage before insertion. Match drive capability, cable orientation, power and interface against the actual hardware documentation. Do not adapt an unfamiliar connector by wire color or plug shape. A modern USB floppy drive should not be assumed to support every historical disk format or preserve copy-protection behavior.
Inspect suspicious media before repeated reads. A contaminated or damaged disk can affect a drive and subsequent disks. If a read reports errors, retain the first log and avoid an endless retry loop with no new diagnostic information. Establish drive behavior with expendable known media before using a rare original.
Create an assessable archive
- Assign a disk identifier and photograph its label.
- Record drive, interface, tool version and read settings.
- Keep the first image and log unchanged.
- Repeat a read where appropriate and compare results.
- Store original and derived images with conversion commands.
- Verify separate archive copies and retain checksums.
A matching checksum establishes file consistency, not the absence of original read errors. Keep unreadable sectors and tool warnings in the manifest. Do not overwrite the first capture with a later “repaired” image. A working copy can be modified for testing while the archive remains available for future analysis.
Use emulator images deliberately
The 86Box disk-image documentation describes image formats and geometry handling. Select a supported representation and appropriate emulated controller. Changing a file extension does not convert a structured image into a raw image. Preserve controller and geometry settings with the image so the same virtual machine can be recreated.
Do not expose one writable image simultaneously to multiple systems. Close the emulator and detach or unmount host access before another tool writes to it. Use copies for boot repair, filesystem checks and installer experiments. A new emulator image is a suitable disposable test destination; an archival original is not.
Verify recovery without sacrificing the original
Restore or mount a working copy through a documented path and confirm directory structure, expected files and boot behavior where relevant. For a physical restoration, use compatible spare media and preserve write logs. Record what was restored and what remains unverified. Continue with software preservation to retain application settings and dependencies alongside the media.