From: danny DOT attar AT bt DOT com (Danny Attar)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: biosdisk & int 13 extensions
Date: 6 Jan 2000 10:11:08 GMT
Organization: BT plc
Lines: 32
Message-ID: <8EB36B5C1dannyattarbtinternet@132.146.16.23>
References: <BBJc4.756$uk DOT 9236 AT news3 DOT mia>
NNTP-Posting-Host: 10.242.188.51
X-Trace: pheidippides.axion.bt.co.uk 947153468 22550 10.242.188.51 (6 Jan 2000 10:11:08 GMT)
X-Complaints-To: postmaster AT axion DOT bt DOT co DOT uk
NNTP-Posting-Date: 6 Jan 2000 10:11:08 GMT
User-Agent:  Xnews/2.11.08
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

thane AT nospam DOT net (Angelene and Klaus Thane) wrote in
<BBJc4.756$uk DOT 9236 AT news3 DOT mia>: 

>Does anybody know if I can use biosdisk for int 13 extensions (0x48(Get
>Drive Parameter) 42(Ext. Read), and 43(Ext. Write).)  0x2, 0x3 and 0x8
>don't cut it anymore.
>    My attempt to use them have been futile.  I get nothing but random
>    crap 
>in the buffer.
>
>TIA
>kt
>
>

I don't believe it can be done. The int 13 extensions are different in
that the registers contain pointers to areas in (real) memory which hold
the disc addressing parameters or the returned disc geometry information,
whereas the original int 13 functions use the registers directly for
these purposes. 

One solution is to set up the registers explicitly and then call
__dpmi_int to perform the interrupt. I use the transfer buffer to contain
the device address parameters and the read/write data. I found the DJGPP
FAQ very helpful, as always. 

Hope this helps.

Danny Attar
===========
Disclaimer: the views expressed here are my own personal opinion and are
in no way connected with my employer.