Quoted from hiho:
Id like to bring this thread back up - Im not able to find a valid l-4 set for mousin. The ones from ipdb I pulled are both fooked, even the ones from vpinmame error out with crc mismatches. Any help appreciated?!
I ran into this a few months ago with a customer I had burned a set of roms for...
I came across this thread in my search and then played with a hex editor...I was going to post, and then realized it seemed to just match and repeat inkochnito's findings above and I could not confirm the previous version's checksums officially. However maybe it will help with clarification and how I came to the similar conclusion so you can decide which set to use.
Pinmame will always say the CRC/checksum is wrong, if it doesn't match what Pinmame is expecting, but you can replace/rename other versions to actually test and play...it's just hard-coded in pinmame what versions it is expecting....but this can be / is different in this case that the 4 digit checksum a physical machine/game code is expecting and would throw an error on the display. (The pin mame crc's are configured to whatever chip size was submitted to them...and does not adapt for manipulating the chip sizes/repeating code if they don't reprogram it, and they don't disect the code on each game..they just make sure pinmame plays it....but I did end up testing them by manually building them in pinmame to test in test mode)
So here is what I had prepared for a post previously, and had set aside
MOUS_U26.L4 Code repeats after 00003FF0 (doubled to burn a 27C128 on 27C256)
mous_u27.l4 Code repeats after 00007FF0 (doubled to burn a 27C256 on 27C512)
mous_u4.l2 This is correct L2 version? (I have confirmed working on physical machine) (Very Drastic differences in code, like it was rewritten)
mous_u19.l2 Very minor differences between first and last couple of lines (Correct L2?)
mous_u20.l2 Identical to IPDB
mous_u21.bin - Not Included / Supplied
mous_u22.l1 Identical to IPDB
IPDB Pinmame L4
MOUS_U26.L4 Code stops at 00003FF0 (Identical to first half of PPS)
mous_u27.l4 Code stops at 00007FF0 (Identical to first half of PPS)
mous_u4.l2 This is actually L1 Version named wrong
mous_u19.l2 Very minor differences between first and last couple of lines (Correct L1 labeled wrong?)
mous_u20.l2 Identical to PPS
mous_u21.bin Identical to mous_u20.l2
mous_u22.l1 Identical to PPS
So to add to the confusion...I found a mention or 2 of some machines having u21 instead of u20, but not sure why. The manual shows both U20 and U21 with different part numbers, but I know data can change after printing. It sounds like what happened is they moved the u21 to U20 at some point...mid production or for whatever reason. U21 is on MPU board. U20 is on the sound board. Maybe they just moved it to put them in one spot, but didn't actually change the code?...maybe they switched from sys11b to 11c?..Maybe just L2 changed where it was looking for it?...I dunno all guesses at this point, but this is where the duplicate of u20 in u21 in pinmame's set came into play.
So long story short, it sounds like PPS has the correct L4/L2 latest version on their site, but have doubled up the CPU roms to fit the larger chips. (causing people to think they are wrong compared to IPDB), and IPDB labeled the L1 sound chips wrong, and had the "original" CPU images. The sound roms then got uploaded to IPDB as a separate LX version under the wrong naming convention.
Hoping this helps and doesn't confuse you further lol