Path: utzoo!mnetor!uunet!husc6!uwvax!dogie!uwmcsd1!ig!agate!ucbvax!RAND-UNIX.ARPA!bridger%rcc
From: bridger%rcc@RAND-UNIX.ARPA (Bridger Mitchell)
Newsgroups: comp.os.cpm
Subject: CP/M dir. extents - correction
Message-ID: <KPETERSEN.12382664566.BABYL@SIMTEL20.ARPA>
Date: 15 Mar 88 17:05:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34

In my posting yesterday:
	Date: Mon, 14 Mar 88 12:01:05 PST
	From: Bridger Mitchell <bridger%rcc@rand-unix.ARPA>
	Subject: CP/M directory extents

I got my tongue (keyboard?) twisted in describing two
examples.  Here's the corrected excerpt, in "<<<...>>>"

examples:
(with S2 and EXT appropriately masked to remove internal bdos flag bits)

#1	S2  = 0,  EXT = 1, RC = 7fh 

	If there is 1 <<<logical extent per directory entry>>>, then
	this is the second directory entry; its final record is 7f=127.

	If there are 2 or more <<<logical extents per directory entry>>>
	this is the first directory entry; its final record is
	80h + 7fh = 255.

#2	S2 = 0, EXT =1, RC = 80h

	If there is 1 <<<logical extent per directory entry>>>, then
	this is the second directory entry; its final record is 80h = 128

	If there are exactly 2 <<<logical extents per directory entry>>>
	this is the first directory entry; its final record is
	80h + 80h = 256, and this entry is full.  

	If there are more than 2  <<<logical extents per directory entry>>>
	this entry is not full; the next record would result in
	EXT = 2, RC = 1.

--bridger