wrong sys default paths:

- well...either you scanned/rebuilt once with sysdefpaths settings enabled and the other time with them disabled or the bios assignments have changed on database level.
Solution: Either pick the sets up and rebuild them again or move them manually to the correct sysdefpath (or disable the warning in scanner-advanced if you like)

- set exists in various rompaths: this could be caused by a similiar situation. Fixmissing/Rebuilder both decided on some set rules where to put rebuilt or fixed-missing sets. For example if sysdefpaths are used, the sysdefpath is used, no matter if the set exists somewhere else. If you toggled the options in the meantime, you will change the behaviour of fixmissing/rebuilder.
Solution: Same as above...simply rebuild them again or move them to backup and let fix missing fix them automatically with the next scan.


Roman Scherzer