Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!hplabs!decwrl!labrea!rocky!rokicki
From: rokicki@rocky.STANFORD.EDU (Tomas Rokicki)
Newsgroups: comp.sys.amiga
Subject: Disk cache
Message-ID: <333@rocky.STANFORD.EDU>
Date: Sat, 30-May-87 03:46:43 EDT
Article-I.D.: rocky.333
Posted: Sat May 30 03:46:43 1987
Date-Received: Sun, 31-May-87 20:37:08 EDT
Organization: Stanford University Computer Science Department
Lines: 25

Now that my hard disk is gone and I'm back to floppies, I've decided
I need a disk cache.  A good one.  One with the following features:

	- Uses *available memory* exclusively, from the end of the
		free list to the front
	- Intercepts AllocMem to invalidate some cache buffers
	- Is public domain
	- Is *fast*
	- Is write through
	- Works with multiple drives; invalidate on eject

Perhaps I am wrong, but I estimate a few days should be all it takes.
I can handle everything off the top of my head but the intercept of
the trackdisk.device calls, which I've never done before.  Perhaps
someone would like to help me with this?

I know about Perry's facc, but does that use free memory, or is it
like vd0: in requiring a certain amount of memory be put aside?

Are there other programs which intercept AllocMem that I should be
careful of, so I don't step on their toes?

I mean, this could make things a *lot* faster than vd0:.  Comments?

-tom