Emulator & Retro Tools
Dreamcast DCM Directory Location Recovery
Restore one mapped DCM byte corresponding to a one-byte defect in the documented VMU root directory-location value after independent normalized filesystem validation.
Tool family
Save-format utilities for supported retro systems and emulator workflows.
Current catalog
Planned and deprecated records are intentionally excluded from Tool Family archives. Each result still carries its own support and processing state.
Emulator & Retro Tools
Restore one mapped DCM byte corresponding to a one-byte defect in the documented VMU root directory-location value after independent normalized filesystem validation.
Emulator & Retro Tools
Restore exactly one damaged byte in the fixed two-byte VMI version value 0 only when the exact 108-byte record, resource-name checksum and all other documented fields independently validate.
Emulator & Retro Tools
Restore exactly one damaged byte in the fixed VMI file-number value 1 only when the exact 108-byte record, resource checksum, version and every other documented invariant independently validate.
Emulator & Retro Tools
Validate a complete DexDrive GME memory-card wrapper and extract its exact embedded 128 KiB PS1 card only when the 123-456-STD marker and every embedded card checksum pass.
Emulator & Retro Tools
Validate a complete VGS/MEM memory-card wrapper and extract the exact 128 KiB embedded raw PS1 card after the fixed 64-byte VgsM header.
Emulator & Retro Tools
Validate a complete PSX memory-card wrapper and extract the exact 128 KiB embedded raw PS1 card after the fixed 256-byte PSV-framed header used by the existing strict parser.
Emulator & Retro Tools
Strictly validate a GameShark GCS single-save wrapper and extract only the exact complete 8 KiB-block payload range after the 0x150-byte wrapper.
Emulator & Retro Tools
Strictly validate a DATELGC_SAVE single-save wrapper and extract only its exact complete 8 KiB-block payload range after the 0xC0-byte wrapper.
Emulator & Retro Tools
Validate the documented DeSmuME DSV footer prefix and terminal cookie, then extract only the exact raw save bytes preceding the footer.
Emulator & Retro Tools
Restore exactly one damaged byte in a complete PSX PSV wrapper signature only when its embedded standard PS1 card independently validates before the wrapper byte is touched.
Emulator & Retro Tools
Losslessly wrap a strictly valid 128 KiB raw PS1 memory card in the independently documented canonical 64-byte VGS/MEM representation, with strict target reopen and byte-identical rollback proof.
Emulator & Retro Tools
Repair exactly one corrupted GameCube directory/BAT mirror by reproducing the documented copy, update-counter, checksum, and strict-reopen rule.
Emulator & Retro Tools
Repair exactly one checksum-invalid 32-byte Controller Pak ID block only when the other three valid redundant ID copies are byte-identical and both index tables are clean.
Emulator & Retro Tools
Repair exactly one checksum-invalid 256-byte Controller Pak index page from its valid mirrored index table while preserving every other byte.
Emulator & Retro Tools
Generate a deterministic read-only evidence report for GameCube card geometry, header checksums, directory/BAT mirrors, byte ranges, filesystem evidence and the exact Phase 47 recovery decision.
Emulator & Retro Tools
Generate a deterministic read-only evidence report for all four Controller Pak ID copies, both index mirrors, raw index nodes, byte ranges and the exact Phase 48 recovery decision.
Emulator & Retro Tools
Compare two same-geometry GameCube memory-card images read-only, bind both sources by SHA-256, map structural and byte-range differences, compare validated filesystem evidence and export a deterministic portable evidence bundle.
Emulator & Retro Tools
Compare two exact 32 KiB Nintendo 64 Controller Pak images read-only, map changed regions and raw index-word evidence, compare redundant metadata states and export a deterministic portable evidence bundle.
Compatibility first
A tool family groups related jobs, but individual file formats and game versions can have different requirements. The individual tool page is the source of truth for compatibility, processing mode, limitations, and verification details.