> Correct. The internal SHA1 will be identical, but the file hashes will be completely > different.
I was trying to fight the apparently hysterical "OMG v5 is completely busted" reactions which followed Arbee's post on his blog. weird, since that post makes quite clear that now the format is solid not only locally (as it already was) but also across multiple OSes
maybe he could have stressed that no CHD for CD or GD have ever been reported to be damaged by the previous chdman (the one between 0.146 and 0.146u2), but probably he did not see it as important given that all GD-ROMs were anyway in need of a redump due to a different (and older) problem in the code...
in conclusion, the uninitialized variables could theoretically bust some files under corner-case circumstances, and even if no one reported it to happen (not even in the conversion of MESS lists), it's good to have them fixed now. no expected breakage and consistent results across OSes are minimum requirements if we ever want the CHD format to be taken seriously by other emulators