Identify the storage arrangement
Flash cartridges expose different features. The Flash Masta USB page describes a cartridge programmed through built-in USB, including capacity and selectable slots. Older Linkmasta documentation describes a separate USB-to-cartridge interface with backup operations. Do not assume the integrated cartridge can read arbitrary retail cartridges merely because the separate device could.
The NeoPocket GameDrive manual documents loading from a card into cartridge flash and saving data back to the card. Follow the sequence for your firmware; transferring a ROM and committing changed game data are separate steps. Back up the current card and configuration before a firmware change or new transfer.
Determine what the game stores
A ROM image contains program data. Depending on cartridge and tool, progress backups may involve modified flash contents or a tool-specific representation. An emulator state is different again. Preserve the first extracted file without renaming it into another format. Record what the tool called its operation and which cartridge, slot or installed-game entry it accessed.
Never infer save support solely from a successful ROM read. Check that the reader documents the needed operation for the cartridge type. Do not test writes or erases on irreplaceable progress. Use spare writable storage or disposable homebrew to establish the workflow before touching the only surviving save.
Make a backup that can be assessed
- Record edition, cartridge identity, visible progress and reader version.
- Perform the documented read-only backup and retain its log.
- Repeat a read when practical and compare sizes and checksums.
- Copy the unchanged result to separate storage locations.
- Use working copies for conversion and emulator tests.
- Restore through a documented compatible path and verify actual progress.
A save-screen photograph provides context but cannot substitute for a restorable archive. An unfamiliar binary format is not automatically a bad backup: it may be intended for its original tool. Keep documentation and software versions with it. A checksum detects later changes to that file; it does not establish that the first read was correct.
Commission a loader without overwriting evidence
Verify the console with an original supported game. Transfer one creator-authorized homebrew example using the loader's own workflow. Confirm boot, input, native saving where provided, normal shutdown and reload. Record physical results separately from emulator results. A game that loads but loses progress needs a save-path diagnosis.
Before replacing installed software, commit pending data as the manual directs and archive it. Do not remove cards or cables during writes. Retain the exact firmware and host software used for a successful test instead of trusting that a future version behaves identically. Continue with homebrew development for build formats and release testing. Keep a small test dataset so each firmware change can be checked without risking a library of valuable saves.