Mail Archives: djgpp/1996/03/24/07:02:06
Xref: | news2.mv.net comp.os.msdos.djgpp:2096
|
From: | mhobbs AT datacoreeng DOT com (Michael Hobbs)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | __dpmi _* or _go32_dpmi_* ?
|
Date: | Fri, 22 Mar 96 18:44:46 GMT
|
Organization: | Data Core Engineering
|
Lines: | 17
|
Message-ID: | <4iusbn$7ch@news.wko.com>
|
NNTP-Posting-Host: | 206.9.203.111
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
First off, I am working with v2 of djgpp. Second, I have an assumption
that I would like corrected if it is wrong: programs compiled with the v2
compiler do not use a go32 loader, rather they use DPMI to load.
Working with this assumption, I have generalized to a second
assumption: for programs built ground-up in v2 compiler, I should use the
__dpmi_ functions instead of the _go32_dpmi_ functions.
The reason I'm confused is 1) I'm not sure my assumptions are
correct. 2) A lot of the samples given in the v2 FAQ use _go32_dpmi_
functions.
As a side note, I used to call _go32_dpmi_allocate_real_mode_callback_retf()
to interface with a packet driver. With DPMI only, my only option is
__dpmi_allocate_real_mode_callback(). How can I make sure that my callback
routine ends with a retf and not an iret?
Thanks for any clarification,
Michael Hobbs
- Raw text -