after looking at the source I found out that the 'decompress and check crc32' option actually decompresses each file of an archive to memory. So it only checks the integrity of the data but it doesn't actually compare the hash against the datfile.

SHA1/MD5 checks do of course.

I will now add a real decompress and check crc32 and rename the old one to something like "test archive" or something.

In your case the data was successfully decompressed but it didn't most likely match the crc32 value of the datfile but it wasn't reported since you didn't scan for sha1 or md5 (if that's available in the datfile).

So...look out for the next version then...(don't ask me when though)


Roman Scherzer