Is there a problem in v3.119 with CHDs in merged mode? When importing the information from the executable and scanning, it is not detecting some of the CHDs even though they exist. For example, 896jaa01.chd is in the ddr2m parent folder, but it isn't recognizing it.

Works fine here in full merged mode.
Be sure it's not locked by another application and be sure your reported chd is ok (chdman -verify).

From 3.118b to 3.119 nothing really changed for the chd routines (metadata check ok..but that doesn't play a role here). If you still get the problem after a rescan with no other interfearing tasks/correctness of the chd in question, send me your cmpro.ini, the belonging settings file *.cmp and let me know which MAME version you used for importing the data.


Roman Scherzer

Roman,

I verified the file with chdman, and it appears correct. I sent an email to your gmail address with the requested files.

Thanks for the files.

You disabled some CHD types. The chds in question are type cdrom0 and cdrom1 which is disabled in your setup.
Go to "Scanner->Hash & CD" and enable all chd regions.

By disabling the regions, the chds were not checked for existance. Normally they aren't listed as missing then, so there is a little issue which will get fixed for the next version.


Roman Scherzer

Yup, that was it. I didn't know about those options, thanks for checking.

> Yup, that was it. I didn't know about those options, thanks for checking.
>


Thanks for reporting the issue. It was wrong skipping behaviour when chd regions are disabled. It took the 1st CHD, correctly skipped it when the belonging region was disabled but didn't report it. But it also skipped the following CHDs of the set without marking them as 'don't care'.....which was wrong.


Roman Scherzer