Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08824 Core Minor Always Feb 23, 2024, 07:54 Feb 23, 2024, 20:34
Tester john_iv View Status Public Platform MAME (Official Binary)
Assigned To hap Resolution Fixed OS Windows 10/11 (64-bit)
Status [?] Resolved Driver
Version 0.262 Fixed in Version 0.263 Build 64-bit
Fixed in Git Commit bd09f30 Github Pull Request #
Summary 08824: pool10j, pool10k: Two Pool 10 sets audit as missing when the merged archive is intact and best available.
Description Pool10k and Pool10j, clones of pool10, go to the unavailable filter/folder in the MAME UI when you audit the fully merged, best available set.

Repro in .262 release and current tip of tree: 0.262 (mame0262-320-g50401e234a9)
Steps To Reproduce 1. Put fully merged into \roms (this zip contains 13 clones).
2. Launch mame.exe, hit F1 and do a full audit.
3. Observe Pool10j and pool10k in the unavailable filter.

If you launch them you get incorrect length messages on the palcd20v8h.u22 and *.u23 roms
and for pool10j
incorrect length on the palce16v8h.u5, palce20v8h.u22, and palce20v8h.u23
Additional Information From an additional set of eyes:

Well, if you fully merge the pool10 sets you run into this:

rom name="palce16v8h.u5" size="2194" crc="123d539a" sha1="cccf0cbae3175b091a998eedf4aa44a55b679400" status="baddump" region="plds" offset="0"

rom name="palce16v8h.u5" size="279" status="nodump" region="plds" offset="0"

Since the second one is a nodump, it won't appear at all in your archive but the other one does. They are differently sized and I guess MAME loads a nodump by name (since no checksum is known) and then finds the one from pool10e which has a different size.
Github Commit
Regression Version
Affected Sets / Systems pool10j, pool10k
Attached Files
png file icon 1.png (137,279 bytes) Feb 23, 2024, 08:01 Uploaded by john_iv
Contents of
There are no relationship linked to this issue.
User avatar
Feb 23, 2024, 12:25
edited on: Feb 23, 2024, 12:30
IMO empty files are more useless than NO_DUMP, I removed them. I haven't checked if this issue is fixed now, but it probably is.

If, in the future, correct PAL dumps are added to this set and the sizes mismatch again, the way to fix it is to increase the size of the NO_DUMPs.
User avatar
Senior Tester
Feb 23, 2024, 20:08
Confirmed fix with 0.262 (mame0262-331-g229d19de63e). Thanks Hap.
Note: Had to extract and use clrmamepro to rebuild