Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!ugmiker
From: ugmiker@sunybcs.uucp (Michael Reilly)
Newsgroups: comp.sys.amiga
Subject: Re: A FaccII suggestion !?!?
Message-ID: <9324@sunybcs.UUCP>
Date: 15 Mar 88 17:08:59 GMT
References: <2126@mit-amt.MEDIA.MIT.EDU> <9220@sunybcs.UUCP> <224@gtss.UUCP> <9279@sunybcs.UUCP> <225@gtss.UUCP>
Sender: nobody@sunybcs.UUCP
Reply-To: ugmiker@sunybcs.UUCP (Michael Reilly)
Distribution: na
Organization: SUNY/Buffalo Computer Science
Lines: 22
Keywords: FaccII
Summary: a Facc III suggestion

In article <225@gtss.UUCP> chas@gtss.UUCP (Charles Cleveland) writes:
>
>I was not trying to make a case for tracking disks in FACC, merely trying
>to address what seemed to me an invalid objection.  Frankly however I would
>like to be able to reserve FACC buffers for a particular disk and not to
>have them cleared when it is ejected temporarily.

	Now that is an idea, how about a way of "promising" to facc that you
will not change a disk, so just hold onto those buffers for a few minutes while
I pop this other disk in here for a minute... If you could do that you could 
have 100 buffers for one disk, 100 buffers for another disk, and so on, because
you and I both know, most people don't have another amiga right next to the one
they are using, and don't swap disks between them....

>Charles Cleveland    Georgia Tech School of Physics    Atlanta, GA 30332
>UUCP: ...!gatech!gtss!chas         INTERNET:  chas@ss.physics.gatech.edu


Mike Reilly  President of UGCSA           University of Buffalo Computer Science
csnet:	ugmiker@buffalo.CSNET 
uucp:	..!{nike|watmath,alegra,decvax}!sunybcs!ugmiker
BITNET:	ugmiker@sunybcs.BITNET   <-OR->   ACSCMPR@ubvmsc.BITNET