Path: utzoo!attcan!uunet!peregrine!elroy!spl1!laidbak!att!osu-cis!tut.cis.ohio-state.edu!rutgers!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: SEZ: a suggestion for the next version...
Keywords: Self-extracting ZOO archives
Message-ID: <8837@spl1.UUCP>
Date: 29 Oct 88 14:42:07 GMT
References: <5450@sdcsvax.UCSD.EDU> <4529@bsu-cs.UUCP> <23402@amdcad.AMD.COM> <5452@sdcsvax.UCSD.EDU>
Sender: news@spl1.UUCP
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Distribution: na
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 30

I think there may be a misunderstanding about some things.

1.   If the entire self-extracting archive were to be loaded in memory,
then you would need as much main memory (main memory, also called RAM,
not disk space) as will hold the entire archive.  So to extract a 300 K
archive you would need 300 K of free main memory.  This means that you
would not be able to conveniently extract such an archive in a small
memory partition such as those that can be obtained with DoubleDOS or
(presumably) Deskview and Microsoft Windows, or if you were shelling to
MS-DOS from a large program like BRIEF or PROYAM.

2.   No, it is not necessary to copy the self-extracting archive to the
directory where you wish to extract the files.  For example, if you
wish to extract the files on disk B: and the self-extracting archive is
A:runme.exe, do the following:

     a.   Change to B: and execute the self-extracting archive with the
	  command

               A:RUNME

     b.   When it says "CAN'T FIND RUNME.EXE" and asks you for
          "File to extract: ", give it the full filename of itself
          by typing:

               A:RUNME.EXE

          The self-extraction will now take place.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee}!bsu-cs!dhesi