Repository navigation
getting started
This page walks you through installing ROM Validator and completing your first validation.
| Component | Requirement |
|---|---|
| Operating system | Windows 10/11, Linux, or macOS 11 or later |
| Architecture | x64 or ARM64 |
| Runtime | .NET 11 Desktop Runtime (Windows) or .NET 11 runtime (Linux/macOS) |
On Windows, the application refuses to run from a temporary folder or directly from a zip archive. Always extract the release bundle to a permanent folder before launching it.
- Open the latest release.
- Download the bundle that matches your platform and architecture:
-
release_<version>_win-x64.ziporrelease_<version>_win-arm64.zipfor Windows -
release_<version>_linux-x64.tar.gzorrelease_<version>_linux-arm64.tar.gzfor Linux -
release_<version>_osx-x64.dmgorrelease_<version>_osx-arm64.dmgfor macOS
-
- Install it:
-
Windows - extract the zip to a permanent folder, for example
C:\Program Files\ROM ValidatororD:\Tools\RomValidator, and runRomValidator.exe. -
Linux - extract the archive to a permanent folder, make the executable startable if
needed (
chmod +x RomValidator), and run./RomValidator. -
macOS - open the
.dmgand dragROM Validator.appto your Applications folder, then launch it. The app is ad-hoc signed, so macOS may ask you to confirm the first launch.
-
Windows - extract the zip to a permanent folder, for example
Every bundle contains one single-file executable and requires the .NET 11 runtime. Windows
bundles also ship 7za.exe and 7za_arm64.exe alongside the application. Every bundle also
contains LICENSE.txt, ReadMe.md and WhatsNew.md. On Linux and macOS the archive fallback uses
a system-installed 7zz, 7z or 7za when one is available; otherwise SharpCompress is used on
its own.
When the application starts you will see:
- the Validate ROMs and Generate DAT tabs in the header,
- the App Data, Donate, About and Exit buttons on the right,
- a status bar at the bottom that reports what the application is doing.
The application checks GitHub for a newer release on every launch. If an update is available you are asked whether you want to open the release page. See Updates.
- Open the Validate ROMs tab.
- Click Browse... next to ROMs Folder to Scan and select the folder that contains your ROM files.
- Click Browse... next to DAT File and select a No-Intro XML DAT file
(
.dator.xml). DAT files can be downloaded from no-intro.org or with the Download Dat Files button. - Keep the default options:
- Move successful items to
_successfolder - Move failed/unknown items to
_failfolder - Automatically rename files when hash matches but filename differs
- Move successful items to
- Click Start Validation and watch the live log and statistics.
When the run finishes, the results are organized in subfolders of the folder you selected:
| Folder | Contents |
|---|---|
_success |
Files that matched the DAT file |
_fail |
Files that did not match or are unknown |
_duplicate |
Files that matched but whose target name already existed |
See Validating ROMs for the full workflow.
- Open the Generate DAT tab.
- Click Select Folder and choose the folder that contains your ROMs.
- Optionally fill in Name, Description and Author for the DAT header.
- Click Start Hashing, then Export DAT and choose where to save the
.datfile.
See Generating DAT Files for details.
| Data | Windows | macOS | Linux |
|---|---|---|---|
| Logs | %LOCALAPPDATA%\ROM Validator\Logs |
~/Library/Application Support/ROM Validator/Logs |
~/.local/share/ROM Validator/Logs (XDG data directory when set) |
| Fallback screenshots | %LOCALAPPDATA%\ROM Validator\Screenshot |
~/Library/Application Support/ROM Validator/Screenshot |
~/.local/share/ROM Validator/Screenshot |
| Screenshots (primary) |
Screenshot next to RomValidator.exe
|
Screenshot next to the app |
Screenshot next to RomValidator
|
Click App Data in the header to open the per-user folder in your file manager. See Screenshots and Application Data.