Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!gargoyle!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uicsrd!krause
From: krause@uicsrd.csrd.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: PK ARC, Another View
Message-ID: <42900006@uicsrd>
Date: Sat, 11-Jul-87 10:32:00 EDT
Article-I.D.: uicsrd.42900006
Posted: Sat Jul 11 10:32:00 1987
Date-Received: Tue, 14-Jul-87 03:19:45 EDT
References: <287@cpsc6b.cpsc6a.att.com>
Lines: 25
Nf-ID: #R:cpsc6b.cpsc6a.att.com:287:uicsrd:42900006:000:838
Nf-From: uicsrd.csrd.uiuc.edu!krause    Jul 11 09:32:00 1987


/* Written  5:36 pm  Jul  8, 1987 by crs@cpsc6b.cpsc6a.att.com in uicsrd:comp.sys.ibm.pc */
/* ---------- "PK ARC, Another View" ---------- */


		insufficient memory.


Chris Seaman
.signatures? We don't need no steenking .signatures!
crs@cpsc6a.ATT.COM or
..!ihnp4!cpsc6a!crs
/* End of text from uicsrd:comp.sys.ibm.pc */

What you have found is indeed a bug in some older versions of the PK ARC
distribution.  It is indeed related to the environment size.  I would
recommend digging up a newer version....

Another thing to watch out for is that PKXARC has trouble de-archiving
files that have been corrupted in transmission...hung my machine every
time.  But dig out ARC and what happens?  It unpacks what it can and
has a nice error message saying that the archive is corrupt.  And it
gives me my machine back....

					James Krause