🚀 go-pugleaf

In article <1346@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
>It's a .ZIP file, and my copy of UNZIP.EXE cannot make the directories
>needed when the zip file specifies something like include/foo.h
>
>It is probably that pesky '/' instead of '\', which probably exists
>because the archive was made on a *NIX system.

Unlikely.  The "/" and "\" are equivalent to DOS in path names.  It's
only the pathetic excuse for a shell COMMAND.COM that gets confused by
forward slashes.  Unless UNZIP.EXE is doing something really
brain-damaged like 'system("mkdir ...")' the forward slash shouldn't be
causing your problem.  Even DOS PKZIP uses "/" as the path name
delimiter when creating archives with directories.

>Anybody have a better UNZIP, or a better solution?

"PKUNZIP -d" has always worked for me.  None of the unzip programs I
have used will create directories by default -- perhaps yours requires
a -d switch?
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)