Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!lll-tis!ptsfa!well!sjm
From: sjm@well.UUCP (Stephen Moehle)
Newsgroups: comp.sys.amiga
Subject: Re: Non-Recovering Recoverable Ram Disk
Message-ID: <4320@well.UUCP>
Date: Tue, 27-Oct-87 14:27:03 EST
Article-I.D.: well.4320
Posted: Tue Oct 27 14:27:03 1987
Date-Received: Fri, 30-Oct-87 03:19:49 EST
References: <7200019@uiucdcsm> <996@cg-atla.UUCP>
Lines: 17
Summary: vd0: and slowmemlast


 In article <7200019@uiucdcsm> schwager@uiucdcsm.cs.uiuc.edu writes:
 >
 >expansion.  I've got ASDG's recoverable ram disk.  It doesn't recover!
 >I use Manx Aztec C 3.4a, and I like to put everything on ram disk when
 >I work- includes (the ones I need, anyhow), compiler, assembler, linker,
 >c.lib, and microemacs; in addition to my most often used cli commands.

	  If you have an A500 or A2000 with some true fast memory (more than 
the 1 Meg of chip bus memory) and use slowmemlast to place the 512k of
slow fast memory at the end of the free memory list, vd0: will allocate
first out of this slow fast memory which is at a fairly low address.  When
a reboot occures, this memory is likely to get trashed and bye-bye vd0:.
It seems that slowmemlast confuses vd0: in its attempts to allocate memory
from high addresses down.

Stephe