Path: utzoo!utgpu!watmath!clyde!att!rutgers!deimos!uxc!tank!nic.MR.NET!xanth!ames!killer!texbell!sugar!uunet!mcmi!hdr!unocss!ca063
From: ca063@unocss.UUCP (Thomas Davis)
Newsgroups: comp.sys.amiga
Subject: Re: path: & 1.3 (also RAD: recovering)
Message-ID: <537@unocss.UUCP>
Date: 2 Dec 88 17:41:49 GMT
References: <385@solaria.csun.edu>
Distribution: na
Organization: U. of Nebraska at Omaha
Lines: 29

From article <385@solaria.csun.edu>, by ecphssrw@solaria.csun.edu (Stephen Walton):
> In article <284@gtss.UUCP> chas@gtss.UUCP (Charles Cleveland) writes:
>>This is under 1.3 Kickstart on an Amiga 1000 with a Michigan Insider.
> 
> 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.
> 
     Almost right.  C00000 RAM will recover, IF you don't reset all the
way back to Kickstart.  I know.  My 1000 and it's Squeeze ram (1meg @ C00000)
does.  Even RAD: (althougth I don't use it.  I did test it out though.)
The only time I don't get a recovery is if VD0: get fulls, and the system
gurus, or some wild pointer mashes the magic cookies that VD0: stashes
in memory.  Now, if your using VD0:, check to see what version it is.  The
version I have is 3.0;  to find out what version your using, use

1> type devs:asdg.vdisk.device opt h

     You'll see a hex dump with the printable ascii on the side;  part of
the ascii will have something like 'version 3.0, date xxxxxx'.

     Also make sure vd0: has a ODD number of cylinders; even will cause
weird problems to develop!


-- 
Internet : ca063%unocss.unl.edu@RELAY.CS.NET | Thomas Davis
BitNet   : conslt16@unoma1                   | Consultant, Campus Computing
UUCP     : uunet!btni!unocss!ca063           | U. of Neb. @ Omaha, NE