Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!ejkst
From: ejkst@cisunx.UUCP (Eric J. Kennedy)
Newsgroups: comp.sys.amiga
Subject: Re: Infinite loop in a directory..
Message-ID: <12361@cisunx.UUCP>
Date: 7 Sep 88 16:31:44 GMT
References: <385@unocss.UUCP> <8818@swan.ulowell.edu>
Reply-To: ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 28

In article <8818@swan.ulowell.edu> page@swan.ulowell.edu (Bob Page) writes:
>ca063@unocss.UUCP (Thomas Davis) wrote:
>>Is there a recoverable ram disk that can survive the reboot from
>>Kickstart of an Amiga 1000?

>The KS process clears all memory.  So unless somebody has a write
>lock switch on their RAM board, no (I think you'd have to have it
>write enabled for config and autosizing, then know when to flip it
>to protect it from being cleared.  Not an easy task).

This is not true.  I don't know the details, but I do know that it is
possible.  I've crashed all the way to the kickstart prompt and had vd0:
still recover.  In the "old days" when I would have to switch back and
forth between KS 1.1 and 1.2 to run Transformer 1.1, I would use the
ChangeKickStart utility.  I would run ChangeKickStart, reboot, insert
Kickstart 1.1, Workbench 1.1, run Transformer, reboot, run
ChangeKickStart, insert KS 1.2, WB 1.2, and VD0: was still there.  Every
time.

VD0: was in my external 2Meg Starboard II, and I did _NOT_ configure the
StarBoard II under 1.1.  Doing so would clear it out, and VD0: would go
bye bye.


-- 
------------
Eric Kennedy
ejkst@cisunx.UUCP