> A) How come some dat files are named after a mame release
> (Mame32QA_Icons_v.119.zip), yet other are just names in dateformat

Datfile author decides.

> B) For the date named ones, how do you know which mame release they are for
> (does it matter?)

On my datfile page you find current ones which are suitable for the latest official MAME version.


> that "MAME Samples 20070916 (cm).zip" is suitable for Mame 119 (other than
> Romans download page from telling you?)

The latest samples datfile on my page is MAME Samples 20071017 (cm) and it's suitable for MAME .120.



> Why is there are separate samples dat file (MAME Samples 20070916 (cm).dat)?

Because MAME's direct import lists samples only by name. No size, hashvalues etc. are available.


> Also, I've got the "Green light" when verifying with "MAME Samples 20070916

You got an outdated samplesdatfile.


> Then with Mame32, if I "Audit All Roms" - I'm told

MAME32's audit functionality is broken since ages.



> Q3) ClrMamePro in general
> This is what I (think) I want :-
> "Merged Sets" for the ROMS
> "Split Sets" for samples
> "Split Sets" for CHDs

You can only have ONE merge mode which is valid for sets. And sets consits of roms and/or samples and/or chds.



> I'm guess I'm still confused about what exactly a set is!?!

A set is everything which is defined in the xml/datfile game tags. A set can be a collection of roms and/or samples and/or chds. There are e.g. chd-only sets.



Roman Scherzer