Preservation should retain enough information to reconstruct the original software and your own progress. A CD image, floppy image, copied directory and emulator state preserve different things. Keep an untouched master copy, record how it was created and test working copies before altering the real machine.
Inventory what needs saving
Separate original game media from installed software, operating-system files, configuration and user saves. Photograph disc and disk labels and note which machine reads them successfully. For a hard disk or replacement flash device, record its interface, partitions and boot setup before connecting it to another computer.
Do not approve an unfamiliar computer's request to initialize or format an Amiga disk. Use a tool or emulator that understands the actual format, and make a whole-device image where appropriate before attempting file-level repairs. Copying visible files alone may omit partition information or a boot area.
Keep media structure intact
For a CD containing both data and audio, retain the complete track arrangement and its descriptor rather than assuming one ISO captures everything. Test music, transitions and later loading stages, not only the opening screen. Keep file names and any descriptor references together when moving the image.
For floppies, determine whether the software uses an ordinary filesystem or a nonstandard layout. WHDLoad's documentation distinguishes DIC and RawDIC tools for imaging workflows; the title-specific installer identifies what it needs. A successful file copy does not establish that unusual disk structures or protection have been preserved.
WHDLoad installations are their own format
Regular WHDLoad uses title-specific installers and Slave files to run supported installed software. Preserve the installer version, Slave, required data and any configuration alongside the game. Consult its documentation for save and quit behavior, because these can differ among installations.
The special WHDLoadCD32 variant is optimized for an unexpanded CD32 and explicitly lacks writing support, including saved games and high scores. Do not plan a persistent playthrough on the assumption that every WHDLoad build saves in the same way. An expansion-based regular installation must be assessed according to its actual hardware and software requirements.
A preservation workflow
- Label the physical source, machine and read tool used.
- Create an image or documented file extraction without overwriting the source.
- Calculate a checksum and keep the original output untouched.
- Make a separate copy for conversion, emulation or installation experiments.
- Test a representative boot, audio segment and save/reload sequence in a matching environment.
- Store notes explaining any read errors, unsupported features or missing content.
If repeated reads produce different results, investigate the source media and drive before treating one file as authoritative. Avoid repeatedly inserting visibly damaged or contaminated media into a known-good drive.
Restore confidence
WinUAE's original project provides a practical environment for testing a matching emulated configuration. Preserve its configuration with the image, including ROM provenance and relevant hardware choices. An emulator save state is useful for convenience but should accompany, rather than replace, ordinary game saves and media.
The captured Amiga backup article provides additional context. Return to model identification when a preserved title works in one environment but fails on another; hardware mismatches are often more informative than repeated image conversion.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.