Path: utzoo!mnetor!uunet!cbmvax!schein
From: schein@cbmvax.UUCP (Dan Schein CATS)
Newsgroups: comp.sys.amiga
Subject: Re: Recoverable Ram Disks
Message-ID: <3005@cbmvax.UUCP>
Date: 23 Dec 87 15:10:13 GMT
References: <2189@crash.cts.com> <887@rocky.STANFORD.EDU>
Reply-To: schein@cbmvax.UUCP (Dan Schein CATS)
Organization: Commodore Technology, West Chester, PA
Lines: 31

In article <887@rocky.STANFORD.EDU> rokicki@rocky.UUCP (Tomas Rokicki) writes:
>I tried out vdk: for a day or so.  The reason I decided not to
>use it was the fact that it can partially recover.  For instance,
>it could recover half of its files.  For me, this is no good; when
>I reboot and see vd0:c is still there, I want to be able to
>assume that vd0:c/dir, vd0:c/list, vd0:c/cc, and all the rest are
>too.
>
>P.S.  I could be wrong about this, but it's what I seem to
>recall happening at least once.
>
>-tom

  This very well could have happened. VDK checks each file to be sure it
  is valid before it returns the file for use. I have had VD0 give me a
  message that VD0 has a Read/Write error when trying to use a program
  in VD0 that has survived a Guru. My guess is that VD0 did not check for
  trashed memory and simply gave me back all my files. Then when I tried
  to use a program that now contains trashed memory, VD0 fooled Amy into
  giving me this phoney requestor as a way out. (I dont want to hear the
  bad ram chip story! I had this happen on 3 Amy's!)
-- 
   Dan Schein		 uucp: {ihnp4|allegra|burdvax|rutgers}!cbmvax!schein
   Commodore AMIGA			Bix: dschein	     Plink: Dan*CATS
   1200 Wilson Drive			phone: (215) 431-9100	   ext. 9542
   West Chester PA 19380
+----------------------------------------------------------------------------+
   All spelling mistakes are a result of my efforts to avoid education  :-)
+----------------------------------------------------------------------------+
        I help Commodore by supporting the AMIGA. Commodore supports
         me by allowing me to form my own suggestions and comments.