Xref: utzoo comp.sys.ibm.pc:32238 comp.binaries.ibm.pc.d:3969
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d
Subject: Re: Zoo: FATAL: out of memory
Message-ID: <8453@bsu-cs.bsu.edu>
Date: 27 Jul 89 21:08:32 GMT
References: <956@swdev.Waterloo.NCR.COM>
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 35

In article <956@swdev.Waterloo.NCR.COM> neil@swdev.Waterloo.NCR.COM (Neil A.
Law) writes:
>     F:\> zoo e disk_c autoexec.bat
>     Zoo: FATAL: Ran out of memory.
...
>When running zoo I have 545KB of memory available.  I am using zoo 2.1 on an
>NCR PC-916 (80386).

At extraction time zoo 2.01 allocates memory for each filename being
extracted (without freeing it, unfortunately).  It will probably run
out of memory only after a lot of pathnames (several hundred to a
couple of thousand, depending on name length).  It doesn't use long
pointers and so is limited to 64K data.  (This will be fixed in the
next release.)

Possible work-arounds:
1.   Make a fresh copy of the archive, eliminate most files from 
     the copy it by selecting with wildcards, then extract needed
     files.  E.g.

          copy disk_c.zoo G:x.zoo
          zoo D G:x *.com *.exe *.c *.h *.i
          zoo PE G;x
          zoo e G:x autoexec.bat

     You will need enough disk space to copy the archive and pack it.

2.   Extract the archive on another system on which the 64K segment
     limit doesn't apply.  (VAX/VMS, BSD, System V, Amiga, Atari).

3.   Use looz to extract.  It doesn't do anything special with filenames
     and allocates no memory for them.
-- 
Rahul Dhesi <dhesi@bsu-cs.bsu.edu>
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi