www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/01/07/13:25:58

From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: real-mode functions
Date: 7 Jan 2000 17:46:46 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 18
Message-ID: <8558q6$og5$1@nets3.rz.RWTH-Aachen.DE>
References: <fyoofqnexgrpubet DOT fnysxw0 DOT pminews AT nntp DOT generation DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 947267206 25093 137.226.32.75 (7 Jan 2000 17:46:46 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 7 Jan 2000 17:46:46 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

sl <junk AT bbs DOT darktech DOT org> wrote:
> 	DJGPP provides a couple of functions to handle calling of real-mode
> functions, unfortunately I am somehow suppose to know if the real-mode
> function terminates with a 'iret' or something else. 

Of course you are supposed to know that. For calling them from real
mode, you'ld have to know it, too. There's no particular difference in
handling, here.

If you don't even know if the routine you're calling is an interrupt
handler (terminating with iret) or not, you may have to re-think if
you know enough about it to use it, at all.

(In case of doubt, use the non-iret version).

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019