From: "Marp" <marp AT 0 DOT 0 DOT 0 DOT 0>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: int86 problems
Date: Sun, 22 Apr 2001 20:42:39 -0400
Organization: MindSpring Enterprises
Lines: 28
Message-ID: <9bvtmv$r9r$1@slb1.atl.mindspring.net>
References: <3AE34C5A DOT CDD4F2E5 AT jps DOT net>
NNTP-Posting-Host: 9e.fc.1f.4b
X-Server-Date: 23 Apr 2001 00:41:03 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Dennis Yelle" <dennis51 AT jps DOT net> wrote in message
news:3AE34C5A DOT CDD4F2E5 AT jps DOT net...
> I would like to call int 0x21 to get the disk's
> device parameters.
>

<snip>

> So I see that 44h is NOT one of the supported functions.
> What is the best, (or any) way to do this?

You should put the parameters you need into a __dpmi_regs structure and call
the function __dpmi_int (see also __dpmi_simulate_real_mode_interrupt). You
will need to use memory in the real mode address space, so use the transfer
buffer, or allocate it using __dpmi_allocate_dos_memory if the transfer
buffer is insufficient. Be sure to read chapter 18 of the djgpp faq because
it describes this stuff in more detail,  and see the documentation for the
functions I mentioned.

>
> Dennis Yelle
> --
> I am a computer programmer and I am looking for a job.
> There is a link to my resume here:
> http://table.jps.net/~vert/