[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: /RAM help...



In article <CrFxL1.2KJ@theseas.ntua.gr>,
Theofanis Kontogiannis (TEI A.) <tkonto@theseas.ntua.gr> wrote:
> 
>  I would like to use /RAM to unshrink from there some files. I own a
> //c and one 5.25" drive. However (ProDOS8, 128K) I can't make SHRINKIT
> to recognise it. 

Not surprising.  ShrinkIt uses all the 128k RAM for its own code and
data, and for buffers while shrinking and unshrinking.  The /RAM disk
is disabled when you enter ShrinkIt, and reinstalled when you leave.

This is a common technique used in ProDOS applications which need all
128k (such as AppleWorks 3 or later).

> What can I do....any suggestions...

Use UNSHRINK.IIPLUS, which runs in 64k and leaves the RAM disk intact.
As I mentioned in an E-Mail message to you, you can either unshrink
from a 5.25" disk to the RAM disk, then copy the file back to a
floppy, or copy the archive to the RAM disk and unshrink it to a floppy.

To do this, you'll have to use a copy program which doesn't destroy
the RAM disk.  One example is the FILER program included on early
ProDOS-8 system disks.  I don't know if SYS.UTILS uses 128k.

At least some versions of Copy II+ give you the option of leaving /RAM
intact.

>  Doesn't SHRINKIT suppose to have the OA-<space> option to unshrink
> files in a diferent disk for those who have one drive and "big" files
> to exctract? 

That is not what this feature is for.  If you select a file using
OA-<space>, you are prompted for a destination directory for that
file, which may be a different directory from the one you are using to
unshrink the rest of the files.

This feature is of no help on a single drive system - you must have the
source and destination disks online during the unshrink operation.  The
same applies to all versions of ShrinkIt (II+, IIe/IIc and IIgs).
-- 
David Empson
dempson@actrix.gen.nz
Snail mail: P.O. Box 27-103, Wellington, New Zealand