Problems with Info-ZIP

[Black Dog]

[face=courier]This is about zip.exe v.2.3 from zcr23xN.zip distributive (last version with encryption support).

1. If you use zip.exe instead of internal ZIP packer, it doesn't add spaces to archive names by default, e.g. if you packing folder with a name "Long name folder" it gives you "Longnamefolder.zip". Actually Info-ZIP's zip.exe is win32 executable with long name support, etc. and "U&se ZIP-NT 2.01" in "Zip packer" configuration is checked. The funny thing is if you add some parameter to "Pack files" dialog path, e.g.

zip: -9 -! -S -v -e "Long name folder.zip"

archive name would be correct, i.e. "Long name folder.zip".

2. Commander can't use Info-ZIP's zip.exe as ZIP UnPacker - it lists archive well, but can't unpack files from it, it looks like some problems with parameters sending from Commander to zip.exe in this case.

3. Commander doesn't play "Pack complete" sound after external zip.exe packing unless you sent it to the background.[/face]

[Black Dog]

[face=courier]Christian, actually this is a bug report. Any comments?[/face]

[ghisler(Author)]

1. This is by design. Some versions of zip.exe have problems with spaces in names.

2. Indeed currently only pkunzip.exe is supported. But why would you need an external zip unpacker?

3. Hmm, odd, I will check that.

[Black Dog]

[face=courier]On 16-09-2004 22:32:29 +0000 ghisler(Author) wrote:

Well, better late than never, yeah? %).

g> 1. This is by design. Some versions of zip.exe have problems
g> with spaces in names.

It looks like you didn't read this part of my post:

BD> Actually Info-ZIP's zip.exe is win32 executable with long
BD> name support, etc. and "U&se ZIP-NT 2.01" in "Zip packer"
BD> configuration is checked.

...and from your Help file:

Use ZIP-NT 2.0.1 (supports long names!)

The packer specified is Info-Zip for Windows NT 2.0.1 or later (ZIP-NT). Zip 2.0.1 must be patched in order to work with Total Commander. Otherwise files containing spaces in their names will not be packed! Total Commander does this patch automatically if it detects an unpatched version of info-zip 2.0.1. Btw, you can find Zip-NT as ftp://ftp.uu.net/pub/archiving/zip/ on the Internet (use Internet Explorer, Netscape or Total Commander to retrieve it with this address).
If you have a later version of ZIP-NT, this patch isn't necessary any more. In this case, you can answer 'yes' to the question if you want to use the packer anyway, but you should pack a test-archive with files containing spaces in their filenames.

So in God's sake, what else is needed to tell Commander that this "versions of zip.exe" does not "have problems with spaces in names", Christian?

g> But why would you need an external zip unpacker?

Sorry, but what's the problem here? I just want Info-ZIP's zip.exe to be my ZIP-Unpacker, what's wrong with it? 8\

g> Hmm, odd, I will check that.

Yeah, do it please.[/face]

[ghisler(Author)]

So in God's sake, what else is needed to tell Commander that this "versions of zip.exe" does not "have problems with spaces in names", Christian?

This was referring to files packed inside the archive, not to the archive name itself!

[Black Dog]

[face=courier]On 20-09-2004 18:40:39 +0000 ghisler(Author) wrote:

g> This was referring to files packed inside the archive, not
g> to the archive name itself!

Well, if archiver can handle LFN inside archive content, what's wrong with archive name?! 8\[/face]

[ghisler(Author)]

The archive name is passed on the command line, while the files to be packed are passed within a list file. Some versions of zip.exe have problems parsing a command line when the archive file name contains spaces, because the parts of the names were interpreted as separate parameters...

[Black Dog]

[face=courier]On 23-09-2004 19:05:39 +0000 ghisler(Author) wrote:

g> The archive name is passed on the command line, while the
g> files to be packed are passed within a list file.

8\

Actually what's the difference - if ZIP-NT 2.0.1 can work with long names, it doesn't matter how one will send them to it, via command line or list file, in one parameter or another.

g> Some versions of zip.exe have problems parsing a command line
g> when the archive file name contains spaces, because the parts
g> of the names were interpreted as separate parameters...

Well, I sent a letter with description of situation you mentioned to Info-ZIP support and get the brilliance answer from Mike White:

BD> The question is - I was told that ZIP-NT v.2.01 has some
BD> problems with spaces in archive names 'cause it interpreted
BD> the parts of the names after space as separate parameters.

MW> Enclose your file names in quotes. That should take care of the
MW> issue.

Well, may be he is right? ;)

P.S. Delenda est Carthago! © Marcus Porcius Cato Major

%)[/face]