 No.02632
Tafoid Administrator
Sep 28, 2008, 17:33
|
I cannot duplicate this. Keep in mind that the m1 file that was in the archives was changed this release with a different file identically named. If you are using the older M1 file, it will not audit correctly, even if correctly named. If you are positive you have the file with the required CRC MAME requires, I suggest you unzip the contents and make a brand new ZIP file with the contents and try again as it is quite possible there is some corruption somewhere. |
|---|---|
 No.02634
Firewave Senior Tester
Sep 28, 2008, 18:01
|
This is weird: D:\mame>mameud -rp d:\_roms\mame -verifyroms ms5pcb ms5pcb : 268-m1.bin (524288 bytes) - NOT FOUND romset ms5pcb is bad 1 romsets found, 0 were OK. The file is not in the archive and clrmamepro reports no missing roms. But it is listed in the -listxml output. Looking at the "Set Information" screen in clrmamepro it is shown and not reported as missing. I also checked the archive and it is not corrupt. Seems like we are actually dealing with a clrmamepro issue. OK, gets even weirder. I did a rescan for my set and suddenly it started fixing ms5pcb and now the file is there and the set is really valid... |
|
No.02637
Haze Senior Tester
Sep 28, 2008, 21:18
|
ms5pcb won't run in the next version anyway, the set is a fake, the program roms should be different. |
|
No.02639
Tafoid Administrator
Sep 29, 2008, 02:15
|
Closing this one out as unable to reproduce. |