Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!caip!ucla-cs!cc1
From: cc1@locus.ucla.edu (Michael Gersten)
Newsgroups: net.micro.amiga
Subject: Re: ASDG recoverable ramdisk (review of same)
Message-ID: <1530@curly.ucla-cs.ARPA>
Date: Tue, 16-Sep-86 00:43:47 EDT
Article-I.D.: curly.1530
Posted: Tue Sep 16 00:43:47 1986
Date-Received: Tue, 16-Sep-86 05:54:55 EDT
References: <167@picuxa.UUCP>
Reply-To: occ4mgk@oac.ucla.edu, cc1@LOCUS.UCLA.EDU (Michael Gersten)
Distribution: net
Organization: Ucla Computer Club (disclaimer)
Lines: 17

Wait a second...it DOESN'T use AllocMem()? Then it CANT be compatible.

Consider what happens if an interrupt routine wants to write to a file,
and writes out to this ram disk. THERE IS NO GUARANTEE THAT AllocMem()'s
DATA WILL BE CONSISTENT. The Ram disk looks at inconsistent data, grabs
memory that may be returned by AllocMem, presto!

This obviously means that the Ram: disk cannot work during interrupts,
but it has no way to tell if its caller was working from an interrupt
routine or not. And there is no problem with writting to disk files
during an interrupt routine.

No flames, please--if I'm missing something here, I think others will
be missing something too. But I don't trust something like that.
			Michael Gersten
      Views expressed here may not be those of the Computer Club, UCLA, or
  anyone in their left OR right mind.  And that's the name o' that tune.