kmoody/libretro
1
0
Fork 0
mirror of https://github.com/Abdess/retroarch_system.git synced 2026-04-15 21:32:32 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update docs, site generator & verification

Browse Source 
Add and reorder BIOS path entries in the site generator (BizHawk, EmuDeck, RetroPie, RomM). Update the add-platform pipeline steps and CI workflow notes. Document verification behavior changes: FirmwareDatabase index now includes sha256; RomM uses MD5 verification (verify.py checks MD5 only); BizHawk uses SHA1; severity label for GREEN adjusted to WARNING. Clarify troubleshooting/verify output semantics (UNTESTED and mismatch reporting), add profiling fields (core_classification option and adler32), fix several path and link typos (RetroDECK path, README/CONTRIBUTING links), and other small docs polishing.
This commit is contained in:
Abdessamad Derraz
2026-04-02 16:26:12 +02:00
parent 2f11542ed3
commit 92b270c054
9 changed files with 28 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
wiki/troubleshooting.md
View File

@@ -72,13 +72,11 @@ filename from the emulator profile.
## Hash mismatch / UNTESTED
`verify.py` reports `HASH_MISMATCH` or `UNTESTED` for a file.
**HASH_MISMATCH:**
`verify.py` reports `UNTESTED` for a file.
The file exists and was hashed, but the computed hash doesn't match any expected
value. This means you have a different version of the file than what the platform
or emulator expects.
or emulator expects. The reason field shows the expected vs actual hash prefix.
To find the correct version, check the system page on the site. It lists every
known BIOS file with its expected MD5 and SHA1.
@@ -147,10 +145,11 @@ How to read and interpret `verify.py` output.
| Status | Meaning |
|--------|---------|
| `ok` | File present, hash matches (or existence check passed) |
| `untested` | File present, hash not confirmed (existence-only platforms) |
| `untested` | File present, hash not confirmed against expected value |
| `missing` | File not found in the repository |
| `hash_mismatch` | File found but hash doesn't match expected value |
| `size_mismatch` | File found but size doesn't match what the emulator expects |
Hash and size mismatches are reported as `untested` with a reason field
showing expected vs actual values (e.g., `expected abc123… got def456…`).
**Reading the output:**