Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!osu-cis!osupyr!bodo!talley
From: talley@bodo.UUCP (James T. Talley)
Newsgroups: comp.sys.mac
Subject: Re: RAM disk info requested
Message-ID: <113@bodo.UUCP>
Date: 5 Mar 88 03:03:29 GMT
References: <475@Lindy.STANFORD.EDU>
Reply-To: talley@bodo.UUCP (James T. Talley)
Organization: The Ohio State University, Computer-Based Instruction Group
Lines: 17
Keywords: RAM disk

In article <475@Lindy.STANFORD.EDU> iris@Lindy.ARPA (AIR-IRIS) writes:
>... RamStart 1.23 seems to be a bit flakey.  For some reason, it
>doesn't always boot up with the disk size we originally specified.
>
>Does anyone have an explanation for this behaviour?  

I've noticed this same behavior with RamStart 1.3 and 1.4.  It seems
to happen to me whenever the amount of memory in use changes.  For
example, when I turn the RAM cache off or on the ram disk seems to
change size.  I've been assuming that RamStart tried to preserve a
constant amount of free memory for your applications, but I could be
wrong.

James
-- 
UUCP    : ...!cbosgd!osu-cis!bodo!talley
Internet: talley-j@osu-20.ohio-state.edu
Bitnet  : ts0183@ohstmvsa