Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!OPAL.BERKELEY.EDU!mwm
From: mwm@OPAL.BERKELEY.EDU (Mike  Meyer, I'll be mellow when I'm dead)
Newsgroups: mod.computers.68k
Subject: Re: Questions!
Message-ID: <8606040528.AA07275@ucbopal.Berkeley.Edu>
Date: Wed, 4-Jun-86 01:28:28 EDT
Article-I.D.: ucbopal.8606040528.AA07275
Posted: Wed Jun  4 01:28:28 1986
Date-Received: Wed, 4-Jun-86 20:15:18 EDT
Sender: mwm@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: info-68k@ucbvax.berkeley.edu

My cp/m-80 system (RIP) did track buffering. They solved the problem
of disk changes by caching door open interrupts from the 8" drives.
Amigados does the same kind of trick on 3" drives, so I would
assume that both 5" and 3" drives (of the correct make) supplied that
interrupt, or something similar (door closed?).

After the disk changed, the cp/m-80 system would beep at you and say
"Put that disk back! Buffers not flushed!" After you put the disk in,
it would say "That better be the same disk!" (gee, it must have had
both open and close interrupts.)  It wasn't kidding; flushing the
directory cache on the wrong disk produced to pretty much garbaged
both disks.

	<mike