> I used WinHex to look at the file I produced from Gzip > and see that the Checksum in the Gzip trailer doesn't match > the checksum produced by WinZip, 7-Zip or a standalone > CRC utility. The size in the trailer matches the original file > size however.
Use the 'gz' file extension for the archive and WinRar. Otherwise, I believe WinZip is the problem - WinZip incorrectly states that the archive is damaged. Jeff On 7/27/09, ErieGuy <[email protected]> wrote: > > I had been using Gzip in one application for compression and Gunzip in > another application to decompress the data produced by Gzip. This > worked without problems. I now have to use a different application > written in C# to decompress the data produced by Gzip. I find that > the C# library is unable to decompress the data produced by Gzip. I > also tried to use WinZip and 7-Zip to decompress the data and these > also report the file as corrupt. I used WinHex to look at the file I > produced from Gzip and see that the Checksum in the Gzip trailer > doesn't match the checksum produced by WinZip, 7-Zip or a standalone > CRC utility. The size in the trailer matches the original file size > however. I don't believe that this is the only problem though. I can > partially decompress large files with the C# library and see that > initially the decompression looks good, with incorrect characters > being slowly introduced and then finally an exception is thrown. I've > tried this with VS2008 and VS2005 on XP and Vista. The same results > are produced regardless of compiler or OS. Is there a bug in Gzip? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
