|
I'm scanning a no-intro NES set, the dat of which points to an xml header file. When I load the profile and run a full scan on the set everything scans fine- no errors with all fix options enabled. If I go into the settings for the profile I see that the correct header xml file is checked. When I load the profile as a batch scan (the only scan option checked in the batch menu is "Don't show statistics"), it proceeds to fix every single rom in the set. When I look at the fixed roms it looks like the scanner is removing the header that the xml file says to skip (at least, that's my assumption as to what the xml file is trying to say and what's going on- there is a chunk missing from the start of each fixed rom).
Now when I go BACK and rescan the set in non-batch mode, everything scans fine! This seems strange. First, that batch scan and non-batch scan produce different results. Second, that two different sets (one with and one without headers, or at least that's what I'm assuming the difference is) scan perfectly fine in non-batch mode.
Am I missing something? Is my understanding of the purpose of header xml files wrong? Is this a bug or am I just doing something dumb?
Thanks for a great program Roman. Keep up the good work.
|
