183
« on: 07 August 2024, 08:03 »
Hi, first of all, thanks for the donation.
Long thread, so I hope I can answer everything here...
> "I like the idea of a full merged ROMset, but ClrMAMEPro 4.048d can't do it the way I want, with clone subfolders"
You can do this. It automatically does it when you got merge collisions (same filename, different hashes inside a parent/clone relationship). If you want subfolders everywhere, you need to enable settings->full merge mode -> hash collision mode
>"replacing commas by periods in some machines' refresh rates"
well, yes and no. the tools do some changes to things which would lead to a bad filename (e.g. "." can't be at the end of a filename in Windows or |,*,? can't be within a filename, that's why they get replaced for machine/rom/disk/sample names). The refresh rates , . replacements are however done by pugixml which does some localized transformation of decimal numbers automatically. No big deal though.
> "After MAME finished verifying both collections, I had 47,016 txt files on each drive. 5,323 of them had 0 bytes"
Erm...does MAME creates them? Because cmpro / new tools don't create dummy sets
> "kizuna4p is a clone of kizuna, but kizuna4p.zip isn't created by ClrMAMEPro"
old cmpro has an option for "fake or dummy clones". Profiler->Options->Parsing Options->Don't create dummy clones.
new tools would handle them as sets on their own
>"Side note: I am puzzled as to why some machines which don't have ROMs receive OK"
Well, guess you need to ask MAME devs why MAME's audit does so. Yes, one is a "non runnable" device. While the other is a machine also representing a softwarelist holder.
>"Continuing, the new rebuilder inserted 13 files marked as NO GOOD DUMP KNOWN inside 11 zipfiles"
I can't repeat this. Can you tell me your rebuilder settings? Can you repeat it? If yes, can you send me one of the input folder archives which lead to this?
>"It warned me about misplaced and wrongly named CHD disks".
Would be interesting to know which ones. If the rebuilder created them, they should be in the correct place. Can you give me information about which files are affected and what the message is? Maybe run a non-fix scan and send me the scan result (either from "scans" folder or a copy to clipboard via context menu)
