Path: utzoo!utgpu!watmath!clyde!att!rutgers!ucsd!orion.cf.uci.edu!oberon!nunki.usc.edu!castor.usc.edu!raddison
From: raddison@castor.usc.edu (Richard Addison)
Newsgroups: comp.sys.amiga
Subject: Re: path: & 1.3 (also RAD: recovering)
Summary: My VD0: recovers in 0xC00000
Keywords: VD0:,recover,0xC00000
Message-ID: <2056@nunki.usc.edu>
Date: 1 Dec 88 07:47:50 GMT
References: <284@gtss.UUCP> <385@solaria.csun.edu>
Sender: news@nunki.usc.edu
Reply-To: raddison@castor.usc.edu (Richard Addison)
Organization: University of Southern California, Los Angeles, CA
Lines: 16

In article <385@solari.csun.edu> ecphssrw@trantor.csun.edu writes:
>This is why RAD: doesn't recover.  No recoverable RAM disk can survive
>in C00000 RAM, because of the way Kickstart 1.2 (and 1.3) check for
>its existence.  Only true FAST RAM will work.

Funny thing, I've not had any major problems recovering VD0: in 0xC00000
ram on my 2000 (with standard 512K chip, 512K "sync" memory).  Am I
doing something wrong? (-;  I've even rebooted to disks without the VD0:
driver (like the standard workbench, with the standard screen size) to
do something quick and then have rebooted by customized environment with
VD0: and have the contents remain.  This works only because I didn't
make heavy memory demands in between.

So what is the real story?

Richard Addison  (Charles Rocket plays me on Moonlighting)