Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!psuvm!psuecl!d6b
From: d6b@psuecl.bitnet
Newsgroups: comp.sys.amiga.tech
Subject: Re: Recoverable ramdrive doesn't
Message-ID: <20522.26db896f@psuecl.bitnet>
Date: 29 Aug 90 13:22:54 GMT
References: <15892@s.ms.uky.edu>
Distribution: na
Organization: Engineering Computer Lab, Pennsylvania State University
Lines: 27

In article <15892@s.ms.uky.edu>, kherron@ms.uky.edu (Kenneth Herron) writes:
> My apologies if this is an old topic, but it's new to me.
>
> Last weekend I installed a Rejuvenator board in my Amiga 1000.  I also
> have a 2-meg board in the expansion slot and an Insider 1-meg board
> inside (which isn't contributing anything because I don't have an
> addmem program right now).
>
> My usual boot floppy mounts a rad: and copies itself over.  Warm-booting
> is from the rad:, and has always performed flawlessly until now.
> Now, on every boot, cold or warm, my machine asks for a boot disk.  And
> it always has to remount rad: ("assign rad: exists" always fails).
> Once it is mounted rad: works fine, except that it doesn't recover
> on the next reboot.

[stuff deleted]

It sounds like you encountered one of the popular bugs in the Exec startup
routine. The problem is that up to 2MB of chip RAM is recognized and
added, but then - after reboot - >512K is considered invalid! What makes that
devastating is that when Exec finds its structures to be invalid, it does
the favor of clearing all local memory (how nice of it!)

A partial and temporary solution is to use the "-r" option of SetPatch.
We may safely assume that this is fixed in 2.0. I hope they also got rid
of the useless and annoying code that clears local memory.

-- Dan Babcock