Keep the original SD media and your working files separate. Before changing Gizmondo firmware or trying a new launcher, preserve readable card contents, important user media and the device's current configuration. A copied game executable, a card image and a backup of internal settings represent different preservation results.
Inventory media and files
Photograph card labels and record which device and firmware can read each card. Note the existing directory layout, application files, saved progress, pictures and other personal media. Keep private photos and contact information out of a public preservation package.
Use an appropriate reader to copy accessible files without formatting the original card. If the card is unreadable, retain any errors and investigate its condition before performing repair operations. A tool's offer to initialize media is not a preservation step.
Preserve a master and a working copy
- Label the original card and record its visible capacity and layout.
- Copy its readable files or create a suitable whole-card image with a documented tool.
- Retain the original output untouched and calculate checksums.
- Create a separate working copy for launcher and application tests.
- Test that the device detects the copy and that representative files open correctly.
- Verify that an important game save can be loaded before changing firmware.
Matching checksums show that copied files are identical; they do not prove that an unreadable part of a damaged card was recovered. Keep acquisition errors with the archive so a future owner can assess what is missing.
Historical PC connection
The original manual documents ActiveSync and its contemporary PC requirements. Treat those as a historical environment to reproduce, not a promise that a current desktop operating system supports the same drivers unchanged. Record the PC software version and connection method that actually works.
Start with a cable known to support the required data connection. Do not assume that a cable used successfully for charging has all the data conductors or correct connector arrangement. If using a dedicated older PC environment, preserve its installer and setup notes alongside the device record.
Application-specific data
The PicoDrive Gizmondo instructions require its executable and supporting KGSDK library to remain together. Preserve a complete documented application directory rather than keeping only the executable. Other historical software can have different dependencies, launcher names or file locations.
Read each application's save behavior and maintain its ordinary saves separately from emulator states where applicable. When changing a build, first test with a disposable copy of the data. A state generated by another platform's port should not be assumed compatible.
Before reset or software update
Record the current firmware, launcher and any homebrew-enabled prerequisites. Preserve the original update package and its provenance if one is part of a documented workflow; do not obtain a random rehosted binary solely because its filename looks familiar. Confirm the target revision and consequences before installing it.
Repeat a small offline test after a successful change: card detection, application launch, controls and save load. Return to hardware and service triage when a failure also exists on the original known-good setup. Use homebrew compatibility for release-specific requirements.
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.