muCommander refuses to open ridiculously huge archives

[davydm@…]

muCommander opens most archives just fine -- but recently, when trying to open an 8.8 gig archive of a backup of some stuff on my system before the last reload, muCommander just "opens" a "blank" archive -- opening the archive just gives me the same view as if I had opened an empty directory. Opening the archive with jZip presents no problems. I have to assume that this is file-size related, since another archive (weighing in at 600-odd MB) made at the same time for other backup purposes, works swimmingly in muCommander.

I don't know if there is any more information I can furnish -- if so, I will gladly do so.

[maxence@…]

Hi Davyd,
This weird behavior is certainly caused by muCommander not being aware of Zip32 limitations and not having support for Zip64 extensions.

muCommander will fail to properly write Zip archives that :
- contain more than 65535 entries
- contain entries than are larger than 4GB
- are larger than 4GB as a whole

muCommander will also fail to open Zip archives that have been packed by another program using Zip64 extensions.

In both cases, muCommander will fail silently (bad).

I started working on detecting such cases and failing gracefully but quickly stopped, realizing it would only take that much more effort to add support for Zip64 and remove those limitations altogether.

I've filed an RFE under bug #113 and I'm marking this bug as depending on it.

[davydm@…]

Excellent! Thanks Maxence (: