Hi,

I have the following problem: for a number of CHDs (calspeda, code1db, ddrbocd, drmn2mpu, hellngt, gauntd24, geebeeg, jdreddb, jojoalt, mfightcc, p911e, p911uc, sfiii3a, tsurugij and vaportrp), I get the error mentioned above. Yet, when I remove those files, the next time I run ClrMame they get reported as missing.

Similarly, both macs2os_h.bin and macs2os_l.bin from mac2bios and 10 from sfiii3a are flagged as unneeded, although if I remove them, the get reported as missing, too.

What can I do about this situation?

Be sure you're using the latest cmpro version and be sure you get your data from the official MAME binary. Fake clone roms aren't needed (when using the default option). For chds, you have to put the chds in the parent folder.

mac2bios is a full nodump and not needed at all.


Roman Scherzer

I always check first for a new version of cmpro and I'm using the mame executable or .dat files from mamechannel.it (I think they are as official as it gets, if not from the official page). (Incidentally, I always compile my own version of SDLMAME when an update is released. Is there a way to create a .dat file using SDLMAME?)

But I'm still having the above mentioned problem. I have 3 folders for my ROM files: 'ROMs', 'CHDs' and 'LDs' (I think the names are self-explanatory). I make sure the paths are added to cmpro's preferences.

Taking calspeed as an example, I have a folder called 'calspeed' in the 'CHDs' folder, inside of which is 'calspeed.chd'. Same goes for calspeda: 'calspeda.chd' inside 'calspeda' inside 'CHDs'.

Both files are correctly identified and pass the SHA1 test.

I first thought maybe I mixed up calspeed and calspeda. So I exchanged their names and positions. But cmpro correctly identified the two files and reported them as calspeed and calspeda, respectively. If I rename calspeda to calspeed, cmpro reports "missing but fixable (-> calspeed) chd: calspeda.chd". If I reverse the name change, calspeda is reported again as unnecessary, if I delete calspeda, next time I run cmpro it is reported as missing. If I put 'calspeda.chd' inside 'calspeed', cmpro reports "wrong placed chd: ...CHDs\calspeed\calspeda.chd (move to set: calspeda)".

I'm completely lost here :-(

I hope my explanations were somewhat clear enough so some kind soul may tell me that I'm stupid and what I'm doing wrong here.

It's pretty easy:

If you're using split-merged sets do the following:

- keep your calspeed.zip romset in a romfolder
- keep a rompath subfolder called "calspeed" in a romfolder
- keep a rompath subfolder called "calspeda" in a romfolder
- put calspeed.chd (525.720.024 bytes) in the calspeed subfolder
- put calspeda.chd (511.316.095 bytes) in the calspeda subfolder


If you're using full-merged sets do the following:
- keep your calspeed.zip romset in a romfolder
- keep a rompath subfolder called "calspeed" in a romfolder
- keep both chds in that calspeed subfolder
- remove any instance of a calspeda folder



What you most likely did is: keeping full merged sets but split up the chds. So clrmamepro was correctly telling you:

unneeded fake clone: calspeda (merge to: calspeed)
wrong placed chd: calspeda\calspeda.chd (move to set: calspeed)

First line complains about a calspeda folder which isn't needed if you keep sets merged (plus calspeda is 100% identical to its parent rom-wise). And it tells you to move it to calspeed.
Second line tells you about the wrong placed chd. It should belong to calspeed. Again, cmpro tells you to move it.

Now if you manually moved calspeda.chd to calspeed but didn't remove the calspeda subfolder, cmpro will tell you again: unneeded fake clone: calspeda (merge to: calspeed) since it's not needed.


Roman Scherzer

> If you're using split-merged sets do the following:
>
> - keep your calspeed.zip romset in a romfolder
> - keep a rompath subfolder called "calspeed" in a romfolder
> - keep a rompath subfolder called "calspeda" in a romfolder
> - put calspeed.chd (525.720.024 bytes) in the calspeed subfolder
> - put calspeda.chd (511.316.095 bytes) in the calspeda subfolder
>

Thanks for putting in the sizes, so I could check I didn't mix the files up. That was not the case.

> Now if you manually moved calspeda.chd to calspeed but didn't remove the
> calspeda subfolder, cmpro will tell you again: unneeded fake clone: calspeda
> (merge to: calspeed) since it's not needed.
>


I'm not trying to be stupid, but I seem unable to wrap my head around this, and I think I also forgot to mention that I'm using split sets, so it seems that I need the first variant.

But that is what I'm doing (I think)! Here's my set up:


MAME
|-ROMs (folder)
| ...
| calspeed.zip
| ...
|-CHDs (folder)
| ...
| calspeda (folder)
| | calspeda.chd
| calspeed (folder)
| | calspeed.chd
| ...


I have both ROMs and CHDs in a Rom-Path in cmpro's settings.

Maybe it has to do with the fact that I put my CHDs in a different folder than the normal ROMs?

> Maybe it has to do with the fact that I put my CHDs in a different folder than
> the normal ROMs?

No. Your setup works fine here. I tested it with different paths for chds/roms.

Please send me:

- cmpro.ini
- the belonging profile settings file *.cmp file from cmpro's settings folder
- the dat (if you're using one) in question. Otherwise let me know which MAME binary you've used

fastest would be roman.scherzer at gmail dot com


Roman Scherzer

Thanks for the files.

However with your setting it works perfectly fine here (Windows, official MAME).

Maybe some Mac/Crossover/SDLMAME thingie. Will do further checks.


Roman Scherzer

- calspeed and other chd issue will be fixed in 3.119
- mac2bios is a SDLMAME issue



Roman Scherzer