> First of all, please use the clrmamepro forum.
I am sorry but I can't complete registration there, it seems my whole IP range has been labeled as spam by your forums. I have sent two emails to simone to say that I wasn't a bot nor a spammer but he didn't answer me. My nick is "Read Only" (with a space) in your forums, so if you can do anything to fix it, I would be grateful.
> Be sure you got Profiler->Options->Parse Disk Merge Tags enabled and you're using a > datfile which uses them...preferable a direct MAME data import instead of a 3rd party > dat.
That's how it is set currently and I use direct MAME data import.
> Then of course you should not use unmerged sets...otherwise you'd need to double the > file. > > So, generally, the message means that a file is missing but cmpro found it somewhere > in your paths and is able to fix it directly but you're right, normally you don't > need to double it....depending on the used settings/database
I understand now, so this is happening because I use non-merged sets. I knew what merged set meant, but to be honest I had no idea what was the difference between Non-merged and Split set, and since Non-merged was the default option at the time when I first downloaded cmpro I just didn't touch it. Now I have finally understood the difference and knowing a bit how the parent/clone relationship is working in the MAME source code, I realize "Split set" is exactly what MAME needs, and that I was having a lot of unneeded dupes, damn! I have rebuilded a Split set and now I don't have the "missing but fixable" message anymore. Thank you very much Roman.
Lol did I just get rid of 14 Gigs?
|