Click here to view the original newsgroup article (read only).
Is there any plan to support larger file size in the future? I am using c1zip to compress our sql backup and the backup size is over 4.2g now. c1zip did not throw any exception when it tried to compress the 4.2g file but created a invalid zip file that is way smaller than it should. I think an exception will help so the calling program can at least find out the compression was not successful.
Hello,
Thanks for reporting this issue to us. I would suggest you to please send an email to support@componentone.com so that we can look further into this.
Best Regards,
James Smith
<saint168> wrote in message news:201399@10.0.1.98... Is there any plan to support larger file size in the future? I am using c1zip to compress our sql backup and the backup size is over 4.2g now. c1zip did not throw any exception when it tried to compress the 4.2g file but created a invalid zip file that is way smaller than it should. I think an exception will help so the calling program can at least find out the compression was not successful. http://helpcentral.componentone.com/cs/forums/p/50497/201399.aspx#201399
James,
You work for C1, why don't you forward it to support? Saint168 has done his bit reporting the problem. Now you want him to report it again? I don't think that's the kind of service C1 was built on.
We would love to support larger files, but we don't own the zip file specification, so unfortunately we cannot change it.
The root of the problem is the fact that the zip format uses 4-byte integers to store file sizes, so the maximum size that can be represented is uint.MaxValue (4294967295) bytes.
I agree with you 100% that the C1Zip component should detect error conditions and report them rather than quietly create defective files. I will check the situation you reported and if it is still a problem, I will make sure it is fixed.
Thanks for reporting this issue.