This profile targets only the documented little-endian VMI file-number field 01 00. SaveEditor independently checks the resource-name checksum, date/time ranges, NUL-padded names, version zero, mode bits, reserved zero field and file size before changing one file-number byte in a copy and strictly reopening the result.
Emulator & Retro Tools
Dreamcast VMI File Number Recovery
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.
01 / Tool workbench
Use the runtime only when it is actually ready.
The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.
Session change summary
No output has been built in this session.
02 / Compatibility
Know the supported input before opening a file.
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
.vmi
Platforms
Dreamcast
Supported versions / editions
Dreamcast VMI metadata records using the documented 108-byte layout.
Input constraints
Exactly 108 bytes; resource checksum and all non-target VMI fields valid; version exactly 0; exactly one file-number byte differs from 01 00; one-byte output scope.
Known limitations
No checksum rewrite, no VMS resource/payload synthesis, no date/name/mode/file-size reconstruction, and no multi-byte fixed-field repair.
Output / result
A new 108-byte VMI record differing from source at exactly one file-number byte.
03 / Instructions
Use a reversible workflow.
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
- 01Keep the original
Preserve an untouched copy before creating or transforming binary output.
- 02Confirm scope
Match the file size, format, platform, and version to the support information on this page.
- 03Process locally
Use the runtime only when the page reports that its declared engine is loaded.
- 04Validate output
Compare or test the result before replacing any working source file.
Tool-specific steps
Choose the original VMI. SaveEditor restores one file-number byte only after every other documented field independently establishes a coherent VMI record.
04 / Privacy and processing
The processing mode is part of the product contract.
SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.
Declared mode
Browser local
Runtime state
Operational
Tool-specific privacy notes
Phase 54 reads only the explicitly selected local Dreamcast file in the browser. The sega-legacy-recovery-v1 runtime has no fetch, XMLHttpRequest, WebSocket, sendBeacon, FormData upload, server-side save processing, or telemetry path. The permanent 16 MiB per-file ceiling remains in force and the selected source is never modified.
05 / Troubleshooting
When a file is rejected, do not force it.
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
Any checksum or semantic-field failure, wrong version/reserved data, or more than one file-number mismatch stops recovery.
06 / Verification
Support claims should be traceable.
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Last verified2026-08-10
Profiledreamcast-vmi-file-number-recovery
Method notes
Verified with deterministic fixtures, every eligible one-byte corruption position, zero/multi-byte refusal, source immutability, exact one-byte scope, strict structural reopen, independent Python reconstruction, and full regression/source-package parity. The documented VMI checksum is independently recomputed from the VMS resource name.
Public references
07 / FAQ
Questions to answer before editing.
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Is Dreamcast VMI File Number Recovery ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.
Related tools
Continue with the same tool family.
Only index-ready verified records from the same Tool Family are shown here.
Related guides
Read the guidance connected to this tool.
Only reviewed, index-ready Guides that explicitly reference this Tool are included.
Beginner
Backups & Safety
Dreamcast VMU / VMS Save Formats Backup & Identification Guide
A safety-first Dreamcast VMU / VMS Save Formats guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Beginner
Save File Formats
Dreamcast VMU / VMS Save Formats Integrity & Troubleshooting Guide
A fail-closed Dreamcast VMU / VMS Save Formats troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.