1
clrmame Discussion / Re: What is CLRMAMEPRO doing when it “resizes” roms?
« on: 14 June 2018, 18:18 »
well, a wrong size is of course only fixable with a given hash for the correctly sized rom.
So assume you got a file with size 2kb and a hashvalue of let's say 0x12345678 and a given "right" size of 1kb. Now cmpro checks the first half of the 2kb file if it matches the checksum...or the 2nd half....or it starts to look at a block of 1kb size which matches the checksum etc...it does some checks like bitswaps, or fill with 0x00 / 0xff (when the right size should be bigger)....etc etc...some are done during the "fix checksum check (in combination with checksum analysis)...e.g. when the size is ok but the checksum is not
So it does not simply cut down the file ;-)
So assume you got a file with size 2kb and a hashvalue of let's say 0x12345678 and a given "right" size of 1kb. Now cmpro checks the first half of the 2kb file if it matches the checksum...or the 2nd half....or it starts to look at a block of 1kb size which matches the checksum etc...it does some checks like bitswaps, or fill with 0x00 / 0xff (when the right size should be bigger)....etc etc...some are done during the "fix checksum check (in combination with checksum analysis)...e.g. when the size is ok but the checksum is not
So it does not simply cut down the file ;-)
? It only happens when you check for an update....which happens when you either clicked "Check Now" in the about update -> dialog...or you've set the selection to check it daily/weekly/monthly......so go there and switch to "never"