Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!pbhyd!ldcol
From: ldcol@pbhyd.PacBell.COM (Larry D Colton)
Newsgroups: comp.sys.apple
Subject: Re: ShrinkIt 1.0 Limits
Message-ID: <1327@pbhyd.PacBell.COM>
Date: 7 Mar 89 04:35:44 GMT
References: <8903061036.AA22851@batman.moravian.edu>
Reply-To: ldcol@pbhyd.PacBell.COM (Larry D Colton)
Organization: Pacific * Bell, San Diego
Lines: 30

In article <8903061036.AA22851@batman.moravian.edu> nicholaA@moravian.EDU writes:
>
>There are a few limits that ShrinkIt has that everyone needs to be aware of.
>I got a bug report back tonight after someone tried to archive their entire
>hard drive and then found that they couldn't extract all the files.
>
  [detailed list of limits deleted]
>
>-------------
>Andy Nicholas                  CsNET: shrinkit@moravian.edu
>Box 435, Moravian College   InterNET: shrinkit%moravian.edu@relay.cs.net 
>Bethlehem, PA  18018                  liberty!batman!shrinkit@sun.com
>                                uucp: rutgers!lafcol!lehi3b15!mc70!shrinkit
>AppleLink PE: ShrinkIt                rutgers!liberty!batman!shrinkit

Andy, I hope version 1.0 does not kill the /ram drive without at least 
a warning that it is going to ignore and destroy anything that might be
there.  I'm a little suprised that I have not seen anyone else mention
this in the discussion over the last couple of weeks.

I have a 2e with an Applied Engineering memory card and software.  The
AE ram software does not use the lower 64k since so many programs need
the 128k to run.  This means you should be able to leave the /ram in
place and still have 128k for Shrinkit.

If for some reason you opt to leave the ram eater in, Shrinkit should
at least warn the user before it starts munching.

-- 
Larry Colton                {att,bellcore,sun,ames,pyramid}!pacbell!ldcol