I used to check in the best mode (at least I hope) all ROMs and CHDs by enabling all possible CRC/MD5/SHA1 switches (decompress etc. etc.) on past versions of ClrMAMEPro.
It usually took a lot of time to complete.
Since when the button "Hash & CHD Setting" appeared and/or Logiqx started to release his DATs on XML format (?), ClrMAMEPro is faster BUT I always get on final window:
...
Wrong MD5s: N/A
Wrong SHA1s: 0
...
like it didn't check the MD5s (!?!).
Under CHD Regions/Available Regions on my system I can see only choices (checked...):
- Standard
- (...blank...)
But on ClrMAMEPro site, under the "Work in Progress" section there is an example with many other regions I never saw, like:
- disks
- ide
- laserdisk
- scsi0
- scsi1
Why I can't see that regions? What is going wrong? Is this the reason because MD5s are not checked?
I constantly upgrade ClrMAMEPro to use the last version, I tried to delete the ini preference files with no luck.

Roman (when you'll ever read this), really thank you very much for your time and hard work on ClrMAMEPro.

And thanks to anyone that will answer and/or solve this "problem".

You're using a datfile which doesn't use regions for chds. That's why you don't see laserdiscs, cdrom0, etc.
For MAME you don't need to use a datfile anyway. It's prefered to use a direct import from the MAME binary. Profiler->Create can be used for this.

However it shouldn't list a blank region below 'standard' and I will also look into the md5 thingie (however it shows "N/A" here if no md5s are available). Both won't happen when you use the direct import from MAME instead using Logiqx's dat.

[edit] ok...I already fixed the empty region part...however I have no idea why it shows an empty md5 count. Can you send me the used datfile, your cmpro.ini and the belonging *.cmp settings folder file for your used profile.


Roman Scherzer

Roman, thank you for your quick answer!
You're right: after the MD5s there was a N/A (I cut & pasted directly from the screen log...), but it didn't showed because (I suppose) the less-then "<" and great-then ">" characters are special control characters that are not shown on "forum" text (but they do appear on "source" text). I modified the original post by deleting them so at least you can see the N/A.
About your answer, I didn't know it: I always used Logiqx dats (expecially in the past, when he made the "diff" dats). I'll try like you said (tomorrow...).
I'm happy maybe you discovered a little bug, if you still need the log, ini and cmp let me know.
Bye!

ah...ok...if the N/A appears...fine ;) So no MD5 issue (since MAME doesn't have any MD5 values stored, so you can't check them) and the empty region is fixed (and you don't see the others since your dat doesn't support it).
Under this circumstances I don't need your files anymore.


Wow...you never used a MAME binary directly? Hell you missed a lot 8)



Roman Scherzer

Roman, for the first time I used a datfile created from inside ClrMamePro with mame.exe v0.127 (but I just saw v0.128 is out!).
With it I correctly can see, like you said, all CHD-regions ;-).
Yesterday I ran a full-scan (with all type of CRC selected, decompress etc.) of my rom collection: it took 8 hours and 13 min to complete (my PC is 3 years old)!
More or less like before when I used Logiqx dats that were not XML, excluded the extra time needed for cubeqst.chd.
I'm sure that the scan stopped for checking a long time on every CHD file but at the end, in the log window, I saw that MD5s result said "N/A".
Did it check for any reason only SHA1? Just to know... because anyway now I sure all ROMs/CHD/Samples are OK.
[edit]: I just read again your previous answer and noted that you already said MAME binary doesn't have inside the MD5s CRC values...

Another question:
Compared with Logiqx dat MAME v0.127 the dat created with CMP differs about the "alpha denshi" samples: it says the the old samples are not necessary anymore (8 zips for 8 games, but I suppose they were "fake") and it wants only "alphamc07.zip" samples... which of the two is right? Yours, of course ;-), but why Logiqx dat is different?

Another question:
Is there a way to create, using CMP, a diff dat between two mame.exe versions?

A. Q.:
Can CMP export a dat he created in some kind of filetype? It seems that the dat file created in the datfiles directory is like a placeholder...

An idea:
It would be nice to have a feature to pause a Scan (expecially the ones that you know are long), maybe by creating a temporary file with the results up to that point, and to resume it at a later time, instead of aborting it...

Maybe too many questions?

Many, many thanks for all your work on CMP!!!

P.S.: you were right, I missed a lot!

> my rom collection: it took 8 hours and 13 min to complete (my PC is 3 years
> old)!

Yieks...a standard scan (without sha1 and full chd decompression) takes 1 minute here and when everything is in the diskcache only 8 seconds ;)


> Did it check for any reason only SHA1?

MAME only supports sha1 and crc32. CHDs do have also an additional md5 value in the header.


> "alphamc07.zip" samples... which of the two is right? Yours, of course ;-), but
> why Logiqx dat is different?

My samples datfile is based on the MAME's sample output. No idea what Logiqx uses.

> Is there a way to create, using CMP, a diff dat between two mame.exe versions?

No. Use Logiqx's mamediff tool instead.

> Can CMP export a dat he created in some kind of filetype? It seems that the dat
> file created in the datfiles directory is like a placeholder...

You can always use Scanner->Scan Results Tree window->Set Information (button bottom left) -> Export

> It would be nice to have a feature to pause a Scan (expecially the ones that you
> know are long)

Simply hit 'cancel' during a scan and ignore the prompts. You can go on later then. Ok..currently this means you have to keep you PC on and don't quit cmpro...
Not a bad idea to provide some 'pause' functionality where you can turn off your pc. However nobody knows if someone scans 50% then pauses, manually changes parts of the 50% and continues scanning....
Normally fastscan is for this....one full scan, afterwards only fastscans..


You don't need to do a full sha1 + chd decompress all the time...this is overkill...you may want to do this once a year or so....



Roman Scherzer