Although the scanner reports just one missing rom, both the scanner statistics results as well as the profiler report 2 missing roms. I have never noticed any discrepancies in the past between those numbers. Thought I let you know. BTW, I am using clrmamepro 3.88.

> Although the scanner reports just one missing rom, both the scanner statistics
> results as well as the profiler report 2 missing roms. I have never noticed any
> discrepancies in the past between those numbers. Thought I let you know. BTW, I
> am using clrmamepro 3.88.
>


Read the FAQ linked on the main page. The statistics window always counts ALL roms/sets from the datfile no matter which merge mode is selected. The scan results DOES show the issues depending on the selected merge mode.

So if you miss 1 parentfile from puckman and puckman got 30 clones which all use that parentfile,too...you'll see one missing parent file in scanresults, while the statistics show 31.


Roman Scherzer

You are right as always! Sorry for not having consulted the FAQ as my first option. It is just that I have never noticed it so far and it did not come to my mind that it maybe in the FAQ. And I was not aware that this particular game had a clone. It has, I just checked in MAWS, and yes, its only 1, which perfectly explains the 2 roms missing that are reported. Just out of curiosity, why did you choose the tree to not show the parent and the clones, or is it the settings I use, which you were sort of indicating in your answer.

> explains the 2 roms missing that are reported. Just out of curiosity, why did
> you choose the tree to not show the parent and the clones, or is it the settings
> I use, which you were sort of indicating in your answer.


Well...because the scanner tree *shows issues* and if you use split or full merged mode, a missing parentfile is only an issue in the parentset. If you turn to unmerged, a missing parentfile is listed in each.


Roman Scherzer