Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Recoverable Ram Disks (Really, the VDK: disk)
Message-ID: <22308@ucbvax.BERKELEY.EDU>
Date: 24 Dec 87 19:41:48 GMT
References: <2982@cbmvax.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 32
Keywords: VDK: VD0: Survivor

In article <2982@cbmvax.UUCP> schein@cbmvax.UUCP (Dan Schein CATS) writes:
>
> VDK: works like the original RAM: in that it only
> uses memory as needed (IE: its always 100% full), and it was designed *NOT*
> to use C00000 memory.

Arhg!!  This is terrible!!  As an owner of 1.5 Megs of $C00000 memory and
NO OTHER EXTRA MEMORY this is really the pits, if true.

VD0: (and probably VDK:) works fine with $C00000 provided I can live with
these two bugs:

1> If a recoverable Alert() is posted, I loose my memory.  Deadend Gurus on 
the other hand are safe.
2> If the execbase checksum is changed, or if location 4 is mashed I also
loose the ram disk.

This is much beter than having the disk use up chip memory, especially since
chip has the EXACT SAME TWO BUGS.  And since I have long ago patched my
Kickstart to fix the bugs, it is not a problem anyway. **

VDK:'s good habit of recovering whatever files may be readable is nice in
contrast to VD0:'s "all or nothing" approach.  If it gives an error when
something had to be nuked, that would be even better. 


** You'll need to read the Transactor Amiga magazine for the patches.

|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (or try "cogsci")
 (")
  U	"Your theory is crazy... but not crazy enought to be true." -Niels Bohr