> > As said before: several fix missing options will fix that automatically and
> both
> > clrmamepro's setname and romname check work correctly.
>
> As you can see in the picture, I have those options enabled and they still don't
> fix the situation...

Hehehe...look at your files...and you should easily see what's wrong with your sets:

1) you got correct Setnames
2) you got correct Romnames
3) you got invalid (exchanged) checksums

so you can easily see what's happening:

- set + name check doesn't need to fix anything
- rom + name check doesn't need to fix anything
- rom + checksum check tells you the file is bad

And since nothing's moved to the backup folder (unless you use popupmenu->delete->all not fixed), fix missing doesn't pick anything up.


Your problem is that the rom name and set name is still correct, so only the checksum check detects the bad checksum.


If you simply exchange the names of two sets the other method I told you works fine (although you need 2 scans, the 1st removes the unneeded, the second picks up the missing).


So in your case you simply have to use the delete not-fixed method to put bad checksums to backup where it'll be picked up later.


All these stands in no contrast to the scanner and its purpose how it works and not a bug at all. All checks/fixes react correctly. What you want is what the rebuilder does, since it's not setbased but filebased. The scanner is setbased (+ parent/clonerelationship). Everything which is out of this parent/clonerelationship scope (except a set + name check based on unneeded sets) is not expected to be found/fixed and there is no intention to cross-test on a rom (not set) based level. Think about it how long a scan would take if every set is compared against each of the other sets....enjoy ;)




Roman Scherzer