Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!qantel!lll-lcc!lll-crg!seismo!columbia!caip!brl-adm!brl-smoke!smoke!prindle@nadc.ARPA
From: prindle@nadc.ARPA
Newsgroups: net.micro.cpm
Subject: re: automatic disk logging
Message-ID: <4185@brl-smoke.ARPA>
Date: Fri, 26-Sep-86 15:16:59 EDT
Article-I.D.: brl-smok.4185
Posted: Fri Sep 26 15:16:59 1986
Date-Received: Tue, 30-Sep-86 19:25:45 EDT
Sender: news@brl-smoke.ARPA
Lines: 11

CP/M 3.0 (A.K.A. CP/M-Plus) does automatic disk logging as a matter of course.
It does this two ways - first by comparing the allocation tables of the disk
and BIOS, as suggested by Mr. Sage, and secondly, if operating with a drive
that can detect disk removal/insertion (by interruptions of the write-lock
photocell), by using that information.  And as Mr. Sage suggests, there are
some problems when swapping formats (this, on a C-128/1571 CP/M system), but
it largely works just fine.  C-128 CP/M 3.0 supports a virtual drive (E:), and
as expected, disk swaps to honor requests for the virtual drive do not trigger
the automatic logging.
Frank Prindle
Prindle@NADC.arpa