Hi Roman,

I was wondering if you had any plans (or if it's there already!) to use SHA1 in the Rebuilder? With some people releasing fake roms lately (choko & driveyes), using SHA1 in the Rebuilder process would catch it straight away rather than letting it rebuild in bad roms. I know it catches them in the Scanner if you tick the option, but why build in roms when they don't actually match the information you have at hand? :)

A second thought is about the auto-save / delete fixdat. What would be cool is an option to save the fixdat in the same structure as the datfiles / logs / settings, etc files. It would be nice if this setting was independant from the current option, for the following reason :

I would like to use the auto-save / delete feature, but when a new Mame comes out, I do a scan fixing everything I can then save a fixdat. This essentially becomes my 'diff fixdat' that Mamediff could create. But, if I am using this feature, when I rebuild in the roms required, my fixdat would be deleted. That's just an example, of course, not the entire reason I'd want it.

So, I guess what I'm asking is : Could you put in a 'Auto-save / Delete Structured Fixdat' option that does the above, basically disregards the 'Scanner_LastFixDatFile' setting and saves the file under '{CMP_Path}\fixdats', and in the same folder as the datfile.

Hope that makes sense.....I await your reply of 'bugger off' ;)

SK.