Path: utzoo!mnetor!uunet!husc6!mit-eddie!bbn!rochester!ur-tut!sunybcs!ugpete
From: ugpete@sunybcs.uucp (Peter Theobald)
Newsgroups: comp.sys.amiga
Subject: Re: A FaccII suggestion !?!?
Message-ID: <9220@sunybcs.UUCP>
Date: 11 Mar 88 21:02:49 GMT
References: <2126@mit-amt.MEDIA.MIT.EDU>
Sender: nobody@sunybcs.UUCP
Reply-To: ugpete@sunybcs.UUCP (Peter Theobald)
Distribution: na
Organization: SUNY/Buffalo Computer Science
Lines: 27
Keywords: FaccII


In article <2126@mit-amt.MEDIA.MIT.EDU> ralph@atrp.media.mit.edu (Ralph L. Vinciguerra; Amiga-Man) writes:

(talking about FACC II...)
>I wish it could keep track of it's buffers with respect to specific DISKS
>instead of DRIVES.

>Let's say you have an Amiga with some memory, and
>one (or even 2 drives). You typically are poping disks in and out all the
>time. It's too bad that FaccII dumps all the buffers for each drive
>when the disk is ejected. If instead it tracked the buffers with the DISK
>then when that disk got put back in it (and those related buffers were still
>in FaccII) they would still be available.

FACC can't do this. What would happen if you popped a disk out, put it in
another Amiga and changed some files. Now when you pop it back in the first
Amiga, FACC's buffers contain the wrong information.
	I wish FACC could buffer disks intead of drives (I often pop out a
disk, put another in to check for a file, and put the first back in), But
unless you can think of something tricky, I don't see how FACC could do this
and insure the right information is still there.


Peter Theobald				SUNY/Buffalo Computer Science
internet: ugpete@cs.buffalo.edu		bitnet: ugpete@sunybcs.BITNET
uucp: ..!{ames,boulder,decvax,rutgers}!sunybcs!ugpete
csnet:	ugpete@buffalo.CSNET