EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Ecco on 11 December 2010, 19:30

Title: Clrmamepro isn't able to check 7z sets bigger than 4 GB
Post by: Ecco on 11 December 2010, 19:30

Hi,

I always check my own Dumps and making my own dats.
I have now a problem with clrmamepro. My iso's are t7z packed. The rebuilder works fine with them.

But if I use the scanner to check the files with the Option "Decompress Rom & check crc32 + run analysis + fix file (if possible)" I get following error message checking my Dumps:

Archive Header crc32 doesn't match crc32 of decompressed data for file ...
I get this message only for sets which are over 4 GB. This are mostly compressed isos

Do I something wrong???
Or is this a issue of clrmamepro scanner or even t7z.

I have allrdy tried the 64bit version of 7zip, but it don't work with clrmamepro.

Do you have some suggestion for this?

Edit: Sry for the Poll Question!!! I have just a problem and need help and I am a noob in this forum. ^^

Title: Re: Clrmamepro isn't able to check 7z sets bigger than 4 GB
Post by: Roman on 11 December 2010, 20:24

64 bit version of 7z works fine. Im using it myself. The problem is not in the external packer Guess the 4gb limit is based within the 7z reader which comes from an old 7z sdk....which lacks all kind of stuff not to even mention the code quality of the sdk.

I may have a look at it next week.

Title: Re: Clrmamepro isn't able to check 7z sets bigger than 4 GB
Post by: Ecco on 11 December 2010, 21:15

Okay, thanks for the support :-)

I hope this issue can be fixed in the future.

Title: Re: Clrmamepro isn't able to check 7z sets bigger than 4 GB
Post by: Roman on 13 December 2010, 20:48

Ah...I guess I see now what you mean...well, actually the >4GB support of 7z files works fine.

The problem is more likely that when you got the "Decompress Rom & check crc32" or similar options enabled which try to decompress files into memory, you run into an out of memory error of 7z since it tries to decompress the full file into memory. You should see an error like "7z: ERROR SZ_ERROR_MEM -> ...." in the warnings window.

So...solution is: if you work with such big files, don't use such options...or switch to decompressed files. For 7z you currently got the limitation that it tries to decompress the full file.

I don't know if I find the time to look at the lates 9.x versions of 7z before xmas...