Has anyone ever successfully corrected a corrupt zip archive? If so is there a "wiz-bang" Linux app/tool that can achieve this? Already tried basic zip fix commands. I think the corruption may have come from tar'ing the file, zipping the file then including it within another file. Really can't remember exactly what I did to be honest. I've DL'ed and used an eval windows program that claims to fix 40% but the other 60% is skipped. Any ideas on what may be tried?

If the situation is that bad (about half and half), I doubt if anything saves you, at least anything auto-magical. Any un/archiving tool should work so that the unarchiving an archived data results in the original data; if you've archived it several times over, something is not working right if the outcome of reversing the process is not the original data. I'd say you should dump that corrupt file into trash, get the original data again and start all over. If you can't get the original data....well, you should have made backups (or whoever gave it to you).

One of the great things about zip is the simple ways it uses to test archive. It was the best way and still is in my opinion to send files. The problem is the simple test used is not very good at providing guidance when fixing, it only knows damage. I think it is a parity along with filesize.

have you looked at the "help" page ?
or the man page ?
if you did that on Linux then not likely the problem

now if you did that ON a windows OS then ?????


but if you made a tarball first THEN zipped it , that is normal
it would be a *.tar.gz , *.tar.bz2 ,*.tgz,


try untaring it

The turn-key zip repair programs don't fix corrupted data, they just fix bad checksums or bad internal directory information, which enables unzip programs to extract something, corrupt or not.

A common scenario for zip file corruption is FTP transfer in ASCII mode (which systematically destroys some of the data -- say, 0.15% of the bits can be lost). That's very hard to fix but not impossible; I documented an example of a successful receovery at my web site. It's not a turn-key process, though: it requires knowledge of the correct format of the uncompressed file, and lots of computation to perform a heuristic search. Brute-force search of all possible repairs does not work (except for tiny files) because the search space is huge. So for truly important and otherwise irretrievable data, it's possible, but it's a consulting project.

I'm convinced that the zip file was ftp'ed in ascii mode which explains the issue. If I remember correctly it was transferred by a .ksh ftp script that I never fully worked out the kinks of determining weather files were exe's or txt/(ascii/bin). I'd like to revisit this script along with 1000+ others but it's in this corrupt zip file...lol Thanks for your input though. Might be a little over my head but nothing I can't keep learning about. Thank you again.