Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[geekbrain]

Roman,
The attached log file reflects the latest 0.188 MAME with your 32 bit 4.032 code running under Win 10 (32 bit).  It is essentially a snapshot of all ROMs updated and prior to adding the updated CHDs.  It is incorrectly flagging   317-0432-jpn.data   as missing.  I tried using the rebuilder with the file and it would not rebuild.  When I finally attached the CHDs, the issue went away.  It also indicates that 3 ROMs are missing (when there are none).  I am not complaining but just simply alerting you to this strange behavior.

-Thanks-

[Roman]

What makes you so sure that the 3 roms were not missing when the scan was done?
It's pretty common that due to strange set re-arrangements from one version to another already existing files from sets are put into the backup folder and won't be picked up directly by fixmissing. So a good choice is always to do a rebuild from the backup folder after a first fix scan.

[geekbrain]

The log file shows two 'missing rom' listed in the list but 3 at the bottom summary.  After this log file I only performed a Pippin rebuild and added the missing CHDs.  Somehow the   317-0432-jpn.data   rom was magically recognized after adding the CHDs.  Regardless, I have a clean set and just wanted to point out a potential anomaly.

[Roman]

ah...stats count are never correct...;-) ...ignore them....If I remember correctly they are counted without taking the merge mode into account....so a missing parent rom may be listed only once in the scan tree but multiple times in the stats....etc..etc....really...the only important thing is a clean tree output.

Regarding 317-0432-jpn.data..let's look at 187...there was it only available in "vs42006". Now with 188, "vs42006b" was added which uses an alternative chd. So as long as you don't have the chd, you're actually missing the set "vs42006b"...and if the set is missing, it will list all its roms as missing.....even if in this case it belongs to the parent.
When you've added the chd, the set check found vs42006b as available and the rom was not listed as missing...
Nothing that special....and I think I've changed it recently in the nightly build...but I will double check that.

And the pippin set was a bit special this time anyway since an existing file was doubled for whatever reason....so rebuilding the set itself would fix the problem.


Update:
ok...I know the reason why cmpro did is not able to 'fix-missing' Pippin....it simply skips the found match in its own set....Guess that can be changed for the next version.
Regarding 317-0432-jpn.data, that issue should actually be fixed in latest official cmpro (fixed: don't list existing parent roms in completely missing clones' output) and I cannot reproduce it
Stats count in general could be better with the latest nightly build