EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: bpablo71 on 13 October 2015, 11:36
-
Hi,
i´m update to the last release but it´s a while that i´m getting the message that some roms are missing:
Vs. Mach Rider (Endurance Course Version) [folder: machridr - size: 48kb]
missing set: Vs. Mach Rider (Endurance Course Version)
missing rom: mr-1a [size: 8192] [CRC32: e3e3900d] [SHA1: c66807ca372d2e5ac11030fdf3d30e30617d4e72]
missing rom: mr-1b [size: 8192] [CRC32: 5547261f] [SHA1: aedb7ab1ef0cd32f325ec9fc948ca1e21a78aa7a]
missing rom: mr-1c [size: 8192] [CRC32: cb864802] [SHA1: 65f06a8eaca3347432f3f2f673a24692415d869f]
missing rom: mr-1d [size: 8192] [CRC32: 379c44b9] [SHA1: 7b148ba7f7eea64509733f94b4eaafe5bfcf3527]
missing rom: mr-2a [size: 8192] [CRC32: 685899d8] [SHA1: 02b6a9bc21367c481d0091fa8a8f2d1b841244bf]
missing rom: mr-2b [size: 8192] [CRC32: 33a2b41a] [SHA1: 671f37bce742e63250296e62c143f8a82f860b04]
missing rom: rp2c04-0002.pal [size: 192] [CRC32: fd19ae5e] [SHA1: 8ed14347c5a0b1a8a4d6365d6727e0951a00131c]
Paranoia [folder: paranoia - size: 416kb]
missing set: Paranoia
missing rom: 1.319 [size: 32768] [CRC32: ef9f85d8] [SHA1: 951239042b56cd256daf1965ead2949e2bddcd8b]
missing rom: 2.318 [size: 32768] [CRC32: a35fccca] [SHA1: d50e9044a97fe77f31e3198bb6759ba451359069]
missing rom: 3.317 [size: 32768] [CRC32: e3e48ec1] [SHA1: 299820d0e4fb2fd947c7a52f1c49e2e4d0dd050a]
missing rom: 4.352 [size: 32768] [CRC32: 11297fed] [SHA1: 17a294e65ba1c4806307602dee4c7c627ad1fcfd]
missing rom: 5.201 [size: 262144] [CRC32: 9893e0e6] [SHA1: b3097e7f163e4a067cf32f290e59657a8b5e271b]
missing rom: 6.29 [size: 32768] [CRC32: 5517532e] [SHA1: df8f1621abf1f0c65d86d406cd79d97ec233c378]
Vs. Platoon [folder: platoon - size: 256kb]
missing set: Vs. Platoon
missing rom: chrver0.ic6 [size: 131072] [CRC32: 689df57d] [SHA1: 854aaa9feb16e3f239fba6069fbf65e69858fe73]
missing rom: prgver0.ic4 [size: 131072] [CRC32: e2c0a2be] [SHA1: 1f8e33d6da8402be6a376668a424bfde38471021]
missing rom: rp2c04-0001.pal [size: 192] [CRC32: a6293faa] [SHA1: 190a410a3d818e124b2b9d2ef9fb3da003bb5d4c]
During the scan i´m getting that message
Set: Vs. Mach Rider (Endurance Course Version)
Name: machridr
File: D:\Paolo\Mamedev\roms\roms\machridr\rp2c04-0002.pal
Do you want to add the missing ROM?
Set: Paranoia
Name: paranoia
File: D:\Paolo\Mamedev\roms\roms\paranoia\5.201
Do you want to add the missing ROM?
Set: Vs. Platoon
Name: platoon
File: D:\Paolo\Mamedev\roms\roms\platoon\rp2c04-0001.pal
Do you want to add the missing ROM?
The 3 roms exist and they are correct in the usual rom path. I have tryed to download again but no lucky. I have softlist too (even if not all). What is it wrong ?
Thank you
-
I will have a look later tonight...what happens if you let cmpro's fix missing add the files for you?
...and with latest version you mean 4.025 of course, don't you?
-
Yes 4.025
If i let cmpro fix the files doesn´t happen anything to the files. It´s seems that cmpro is finding more files around with the same name but i checked and there is only one machridr while paranoia is in 3 dir (roms, softlist\kc_cass and softlist\pce) and platoon in 2 dir (roms and softlist\specpl3_flop)
-
this should fix it (see attachment)...
fixed: disabled softwarelists with non-unique assigned paths could lead to wrong missing set messages
-
it works fine now :)
thank you very much!
-
i have problem with cmp20151013:
1. i used x64 build of cmp.
2. i did 'Clear Cache'.
3. i used latest MAME .exe as DAT file.
4. cmp crashed on one of the last stages of creating DAT from XML. i beleive, it's 'Generating Set Hashes' process.
5. i repeated steps 1-3 two times, and cmp still crashed on the same stage.
then i reverted back to official clrmamepro 64bit 4.025, and MAME DAT file creates fine.
-
official and nightly build only differ by one if statement in the scanner. so that cant be the reason. it is more likely youre facing the issue stated in the other recent forum post.
-
official and nightly build only differ by one if statement in the scanner. so that cant be the reason. it is more likely youre facing the issue stated in the other recent forum post.
if you mean this post (http://www.emulab.it/forum/index.php?topic=4010.msg15770#msg15770), i did it with clean cache, and cmp is still crashing...
-
try to clear the cache and the hash folder (hope it is the correct name) before starting cmpro
-
try to clear the cache and the hash folder (hope it is the correct name) before starting cmpro
i cleared both cache and hashes folders. cmp20151013 still crashes on the same stage:
-
well you have to wait till the weekend or use something before 4025. weirdly enough it works fine for me with mame or other dats. Im pretty sure about the place to fix but actually this should only be problem when old hash data is loaded in. I try my best on saturday evening
-
http://mamedev.emulab.it/clrmamepro/binaries/cmp20151018.rar (http://mamedev.emulab.it/clrmamepro/binaries/cmp20151018.rar)
-
cmp20151018.rar
MAME .exe DAT is created fine now.
thanks, Roman!!
-
heh, another problem appeared (on cmp20151018), which wasn't existed before - when scanning complete MAME set, there is one error:
[spoiler]Acorn FileStore E01 [folder: e01 - size: 128kb]
missing rom: e01sv133.rom [size: 65536] [CRC32: 2a4a0032] [SHA1: 54ad68ceae44992293ccdd64ec88ad8520deec22]
missing rom: e01sv140.rom [size: 65536] [CRC32: 5068fe86] [SHA1: 9b8740face15b5541e2375b3054988af00757931]
unneeded file: D:\emulation\games\MAMEROMs\e01\0254,205-03 e01 mos [not fixed]
unneeded file: D:\emulation\games\MAMEROMs\e01\0254,205-04 e01 fs [not fixed]
[/spoiler]
-
well...a missing rom. should be easy to check if it is really missing or noz :-)
-
well...a missing rom. should be easy to check if it is really missing or noz :-)
no, it's not missing. i have complete MAME 0.166 set. previous cmp build(s) didn't have that error.
-
well....did you look at the archive itself? Maybe you should zip up and send me your profile *.cmp file (settings folder), cmpro.ini and the used dat (or if it's current official MAME, let me know).
-
well....did you look at the archive itself?
yes. the ROM set is correct.
Maybe you should zip up and send me your profile *.cmp file (settings folder), cmpro.ini and the used dat (or if it's current official MAME, let me know).
files are attached. DAT is official MAME 0.166 .exe.
-
thanks, I will have a look at it tonight
-
well...looking at the listxml output:
rom name="0254,205-04 e01 fs" size="32768" crc="ae666c76" sha1="0954119eb5cd09cdbadf76d60d812aa845838d5a" region="r65c102" offset="0"
rom name="0254,205-03 e01 mos" size="32768" crc="a13e8014" sha1="6f44a1a48108c60a64a1774cb30c1a59c4a6a199" region="r65c102" offset="8000"
it seems that cmpro is now right complaining about your archive and was wrong in the past...your old e01sv*.rom files are wrong...
have to check when these files were replaced....and have to check which fix makes it visible now...
-
hmm..ok...it seems that these roms belong to "e01s" and not "e01"
very interesting...wonder what caused this....will do some investigation...and I guess people have to find the real e01 now ;-)
-
and I guess people have to find the real e01 now ;-)
here how those sets are organized now (see screenshots with ROM name, size and CRC32).
-
well, the funny thing is that since 162 (when mess became mame) they never changed....currently I'm checking which cmpro version was not able to find it...4.023 and 4.025 do detect it right
...maybe it was just a cache flaw....
-
sorry...haven't found a reasonable explanation for this yet. The device sets were added in 162 and haven't changed since then. Checked some "165 locations" and they got the correct e01 and e01s sets. Same for 166. So it can't be a global problem. I don't know a reason why your e01 holds the e01s files and why older cmpro versions did not warn you.
I've tried to recreate the scenario and each version from 4.023 did find it and warned about it.
So...I can only imagine, the e01 archive was somehow replaced with e01s archive after e01 was scanned already, so it was not listed. But hell, I don't have any clue how that should happen.
If anyone got an idea or can recreate a scenario...please let me know. If anyone sees the problem, please let me know the archive date/time stamp....maybe this helps to figure out when this happend.
update...ok..had the chance to look at another backup which represents the time after .165 but before .166....and the 2 sets are still ok....so either something went weird with updating the sets with .166 or after that....
-
ok....I found something....well...something weird...I now got it once when receiving data from the latest MAME exe that e01 was identically to e01s....(and the fixing prompts which cmpro will show are ok then....)...will do some more tests....wonder when this happens....
-
haha...it seems that the error is within MAME...
I've created a batchfile which runs -listxml 10 times.....then I compared the output....1 out of the 10 files was different...
and guess where...exactly in the e01/e01s sets...
so it's a MAME bug...I will report this to MAMETesters.
-
thanks for investigation, Roman.
-
it is clear now, that the problem was MAME and not cmp, so i re-created MAME DAT with cmp20151018, and it didn't show any errors on scan, as expected. ;)
-
Hmm...either the problem is more rare than expected or they fixed it...I've run dozens of -listxml now with .167 and the e01/e01s problem did not appear.