Path: utzoo!mnetor!uunet!husc6!bbn!gatech!gtss!chas
From: chas@gtss.UUCP (Charles Cleveland)
Newsgroups: comp.sys.amiga
Subject: Re: A FaccII suggestion !?!?
Message-ID: <224@gtss.UUCP>
Date: 13 Mar 88 14:08:57 GMT
References: <2126@mit-amt.MEDIA.MIT.EDU> <9220@sunybcs.UUCP>
Reply-To: chas@gtss.UUCP (Charles Cleveland)
Distribution: na
Organization: Georgia Tech School of Physics
Lines: 25
Keywords: FaccII

In article <9220@sunybcs.UUCP> ugpete@sunybcs.UUCP (Peter Theobald) writes:
)
)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.
)	. . . . 
)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.
)
Well, couldn't FACC just check the date and time the volume was last altered,
which is recorded in the disk's boot block, and only keep the old buffers if
it hadn't changed?

-- 
-Life would be so much easier if we could just look at the source code.-

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