Save the progress before service
Inventory the console's existing saved data through the memory manager before clearing memory, modifying the console or investigating a retention fault. Photograph the game names and available entries, then identify a documented export route for the installed hardware. The SD Loader project includes save backup and restore. Follow the manual matching its firmware, and make a second computer copy of each export before another backup can replace it. A successful export should be tested with expendable progress before relying on a restore for important data.
Name archives with the console identity, game, date and export method. Keep untouched exports separately from converted or edited files. An emulator save state contains an emulator-specific machine snapshot; it is not automatically the console's native saved data. Never overwrite the only retained export while exploring conversions. If investigating save retention, first establish that the same title can create and reload a small test save through an ordinary shutdown.
Preserve the complete disc
A disc preservation set needs the track layout as well as the program data. Retain the CUE sheet and every referenced data or audio file together. Open the CUE as text and check that its filenames match the stored files, including case where relevant. Calculate hashes after imaging and retain the imaging tool, optical drive and error log. A playable copy is useful, but it does not establish that the original read was complete or error-free.
| Archive component | Reason to retain it |
|---|---|
| Track image files and CUE | Program, music and the relationship between tracks. |
| Disc and packaging photographs | Region, pressing and physical identification. |
| Read log and hashes | Evidence for comparing future reads. |
| Native saves and configuration | Progress and the conditions of a playback test. |
The loader preparation guide describes its accepted folder and audio requirements. Keep a preservation master separate from any converted loader copy. Converting lossy audio back to an uncompressed file cannot restore information discarded earlier.
Use CD-specific tools and tests
NeoCD-Libretro documents CUE and CHD input, BIOS choices and emulator states. Record the core build, selected BIOS and loading-related options when reporting a problem. Confirm music and later scene loads rather than stopping at the title screen. Emulator-only success remains a test result with stated conditions.
For homebrew, build a project that explicitly targets the Neo Geo CD's boot and disc layout, preserving its source, build instructions and assets. Renaming an AES or MVS cartridge image does not supply a CD loader or split a game's resources into loadable sections. Use the maker's SD loading workflow to iterate a valid CD image, then compare against original-hardware loading where available. Include button checks, save behavior, audio and repeated loads in the release checklist. Record unsupported hardware plainly, and return to loader planning if a hardware installation is required.