Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!ucsd!sdcsvax!amos!hartung
From: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d
Subject: SEZ: a suggestion for the next version...
Keywords: Self-extracting ZOO archives
Message-ID: <5450@sdcsvax.UCSD.EDU>
Date: 28 Oct 88 04:45:08 GMT
Sender: nobody@sdcsvax.UCSD.EDU
Reply-To: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Followup-To: comp.binaries.ibm.pc.d
Distribution: na
Organization: Univ. of Calif., San Diego
Lines: 26

I decided to use a couple of Rahul Dhesi's ZOO programs that I had not
tried yet today and used ATOZ and SEZ to turn the archive vm1088.arc
into a self extracting file, vm1088ar.exe.  Everything worked fine as
far as creating the new zoo archive and making it executable were
concerned.  I then copied the file onto a floppy and put it in the A:
drive of another machine which had a close-to-full hard disk and
intended to extract the files directly onto the hard disk without
having to copy the SEZ-created .EXE file onto the C: drive.  To do
this, I cd'd into the directory I wanted the files to be extracted into
and entered A:VM1088AR, expecting this to work.  The file began
extracting in that I got the usual salutations, version number, etc.,
but this was followed by a statement that the file VM1088AR.EXE could
not be located (presumably because it was looking in the current
directory on the C: drive and not the directory in which the executable
was.

Is there some way this could have been done (maybe even quite an
obvious one) which I may have overlooked?  Is there some reason that
this could *not* be incorperated into SEZ as a feature or option?  It
would seem to be most useful to have this if it didn't kill the
efficiency of the program or make the self-extracting archive
considerably larger.  Comments?  Rahul?

 --Jeff Hartung--  	
 Disclaimer: "Nobody here really cares what I think anyhow."
 ARPA - hartung@amos.ling.ucsd.edu          
 UUCP - !ucsd!ling!amos!hartung