> 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