gonzalez@bbn.com (Jim Gonzalez) (01/25/91)
I'm in the process of getting UNARC16 working on my Cromemco under CDOS. Since CDOS provides only CP/M 1.3 calls, it complains when UNARC16 does a call to the CP/M 2.x function 0x1F. For those who don't have their function tables handy (add another Post-It note to your favorite email/readnews terminal :-), 0x1F is Get Disk Parameters Block, which is used to get a pointer in order to query and (possibly) alter aspects of the disk via this DPB. This function is used mostly by file compression and disk directory programs like Super Directory. What I need to know is the format of a DPB. Armed with that knowledge, I can patch UNARC16 to request the same information from with appropriate (non-CP/M 1.3) CDOS call. It only uses one entry from the DPB, so I'm sure it's just looking for the block size. By the way, Waite & Lafore's _Soul_Of_CP/M_ has been no help in this regard. They acknowledge the existence of function 0x1F, but say nothing more about it or DPB's. So much for getting to the "soul" of CP/M. What they *do* cover they explain pretty well, but it's annoying what they leave out. -Jim.
jm59@prism.gatech.EDU (MILLS,JOHN M.) (01/26/91)
In article <62314@bbn.BBN.COM> gonzalez@bbn.com (Jim Gonzalez) writes: >I'm in the process of getting UNARC16 working on my Cromemco under CDOS. >Since CDOS provides only CP/M 1.3 calls, it complains when UNARC16 does a >call to the CP/M 2.x function 0x1F. .. deletions .. > >What I need to know is the format of a DPB. Armed with that knowledge, I ^^^^^^^^^^^^^^^^ ..etc.. Alan R. Miller, _Mastering_CP/M_, Sybex 0-068, 1983, ISBN 0-89588-068-7, has about 5 pages on this. There is also some in the DRI manual on adapting/modifying cp/m 2.2 (I forget the exact title.). -- MILLS,JOHN M. Georgia Institute of Technology, Atlanta Georgia, 30332 uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jm59 Internet: jm59@prism.gatech.edu