Roman,

When I scan my CHDs I get

Cube Quest [folder: cubeqst - size: 154kb]
no or corrupt chd header/sectormap: cubeqst.chd [chd-md5: d2e6010f9b9d36ba50664096ec331f8d] [chd-sha1: 5266a0a43963628464fac1719e1cefec627042a4]

It passes a MAME scan & plays perfectly.

Then I get

Area 51 / Maximum Force Duo (R3000) [folder: a51mxr3k - parent: area51mx - size: 2mb]
missing but fixable (-> area51mx) chd: area51mx.chd [chd-md5: fce1a0954759fa22e50747959716823d] [chd-sha1: 7e629045eb5baa8cd522273befffbf8520828938]


Again I scan it with MAME it passes a scan & plays perfect. Can you explain this a little? If I missed it somewhere I am sorry in advance

Thank You

> Cube Quest [folder: cubeqst - size: 154kb]
> no or corrupt chd header/sectormap: cubeqst.chd [chd-md5:
> d2e6010f9b9d36ba50664096ec331f8d] [chd-sha1:
> 5266a0a43963628464fac1719e1cefec627042a4]

You should run a chdman -verify on the file and report the results.


> It passes a MAME scan & plays perfectly.

MAME doesn't scan the file. It loads the header and later on during gameplay it uses the sectormap to find the needed data. If the sectormap is somehow corrupted somewhere you most likely don't see it until you completely played the game. Again, I think a chdman -verify should show you if the chd in question is corrupt or not.



> Area 51 / Maximum Force Duo (R3000) [folder: a51mxr3k - parent: area51mx - size:
> 2mb]
> missing but fixable (-> area51mx) chd: area51mx.chd [chd-md5:
> fce1a0954759fa22e50747959716823d] [chd-sha1:
> 7e629045eb5baa8cd522273befffbf8520828938]

a51mxr3k and area51mx share the same file so you only need it once in the area51mx folder. If cmpro complains about it in the clone you either:
- you're using not-merged sets (then you'd need the file twice)
- don't have the parent enabled
- use a different datfile (better use a direct mame import)
- something went wrong when the parent was scanned (maybe some other tool blocked the access)

Both things sound a bit spooky to me and I think something may interfear with your scan. Maybe a virusscanner (try to turn it of for the roms folder or during scan) or a general fault.
What you can do is: Go to About and drag'n drop the chds in question into the window. Cmpro will report hashvalues for the dropped files and please copy/paste me the results. This will be hashvalues for the files themselves, not for the unpacked chd. But so I can see if your files differ from the commonly available ones.

Since you don't seem to have issues with other chds something's seem to wrong with these 2 or something is spooky on your system. Please gimme some more information about which MAME.exe/datfile you're using, which merge mode, how you stored your files, the cmpro settings etc...(easiest would be to send me cmpro.ini, the settingsfile *.cmp for the used profile for this purposes).


Roman Scherzer

So I verified my mach3.chd with chdman and it turned out to be successful/ok. I also had a problem with my Cube Quest chd and that too showed up ok with chdman. I will try the other stuff you said soon and let you know my findings. I created the dat file with 129.

Can I assume that the chds that I scanned (with chdman) are correct and that I'm probably doing something wrong with CLRmame?

> Can I assume that the chds that I scanned (with chdman) are correct and that I'm
> probably doing something wrong with CLRmame?

It more sounds that a) the chds are fine and b) something on your system interfears during scan so that cmpro reports an issue. The message only appears if the chd_open routines which also read the sector map return an error.

No issues with any chds here and noone else reported such things yet....and all the other chds on your system seem to be scanned correctly, don't they?

However I changed some lines in the next version which you might want to try out (when it's out). I still somehow think that some other process (virusscanner, torrents ;), etc...) may lock the file in question....



Roman Scherzer