OK... First of all, let's define a legend:
Hey Roman, I'd like to understand more about the settings for merged sets.
PROFILER >
OPTIONS >
MISC PROFILER OPTIONS- Parsing Options
- Parse ROM 'merge' Tags
Why someone would not to parse the merge attribute (as declared inside M. A. M. E.'s XML) of a clone's rom name?
I mean, if I want my sets to be merged I need to tell clrmamepro to parse the merge attribute, right?
- Parse DISK 'merge' Tags
As above... I want my sets to be merged, so both roms and CHDs should be merged accordingly to what's declared inside M. A. M. E.'s XML.
- Hash Collision(is this enabled only when Hash Collision Name is selected in Full Merge Mode?)
- Single File
This will put only roms with same sha1sum inside its clone's subdirectory, right?
- Single Clone
This will put ALL roms of each clone with same sha1sum inside the relative clone's subdirectory, right?
- All Clones in Relationship
?
SETTINGS- Full Merge Mode
- Normal Mode
?
- Hash Collision Name
"You use the hash collision naming convention fo all clone files, no matter if a hash collision happened or not."
? ... Please could you elaborate on this in simple terms
Looking at this excerpt as a reference, could you help me by reporting a concrete example?
<machine name="hotd4a" sourcefile="sega/lindbergh.cpp" cloneof="hotd4" romof="hotd4">
<description>The House of the Dead 4 (Export) (Rev A)</description>
<year>2005</year>
<manufacturer>Sega</manufacturer>
<biosset name="bios0" description="6.0.0010 alternate version"/>
<biosset name="bios1" description="6.0.0009"/>
<biosset name="bios2" description="6.0.0010"/>
<rom name="6.0.0010a.bin" merge="6.0.0010a.bin" bios="bios0" size="1048576" crc="10dd9b76" sha1="1fdf1f921bc395846a7c3180fbdbc4ca287a9670" region="pci:1f.0" offset="0"/>
<rom name="6.0.0009.bin" merge="6.0.0009.bin" bios="bios1" size="1048576" crc="5ffdfbf8" sha1="605bc4967b749b4e6d13fc2ebb845ba956a259a7" region="pci:1f.0" offset="0"/>
<rom name="6.0.0010.bin" merge="6.0.0010.bin" bios="bios2" size="1048576" crc="ea2bf888" sha1="c9c5b6f0d4f4f36620939b15dd2f128a74347e37" region="pci:1f.0" offset="0"/>
<rom name="fpr-24370b.ic6" merge="fpr-24370b.ic6" size="4194304" crc="c3b021a4" sha1="1b6938a50fe0e4ae813864649eb103838c399ac0" region="pci:1e.0:03.0" offset="0"/>
<rom name="vid_bios.u504" merge="vid_bios.u504" size="65536" crc="f78d14d7" sha1="f129787e487984edd23bf344f2e9500c85052275" region="pci:01.0:00.0" offset="0"/>
<rom name="317-0427-com.bin" merge="317-0427-com.bin" size="8192" crc="ef4a120c" sha1="fcc0386fa708af9e010e40e1d259a6bd95e8b9e2" region=":pic" offset="0"/>
<disk name="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" merge="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" sha1="e13da5f827df852e742b594729ee3f933b387410" region="cf" index="0" writable="no"/>
<disk name="dvp-0003a" sha1="46544e28735f55418dd78bd19446093874438264" region="dvd" index="0" writable="no"/>
[...]
## tuncated output ##
[...]
</machine>
If I understood correctly the merge mode, I should end up with this:
Parent
romsetmame/hotd4.zip:
317-0427-com.bin
Parent
CHDmame/hotd4/:
dvp-0003b.chd
Clone
CHDmame/hotd4a/:
dvp-0003a.chd
BIOS
romsetmame/lindbios.zip:
6.0.0009.bin
6.0.0010.bin
6.0.0010a.bin
fpr-24370b.ic6
vid_bios.u504
BIOS
CHDmame/lindbios/:
mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01.chd
Thank you Roman!