Date: Tue, 10 Feb 1998 21:32:57 -0800 (PST)
Message-Id: <199802110532.VAA05896@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Eugene N. Trofimov" <eugene AT uniyar DOT ac DOT ru>, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: INT calls int DJGPP
Precedence: bulk

At 02:16  2/10/1998 +0300, Eugene N. Trofimov wrote:
>  Could anybody point me all distinctions between following functions :
I think the docs tell it very well, but here's a summary.
>
>  __dpmi_simulate_realmode_int(...)
Btw, it's spelled `__dpmi_simulate_real_mode_interrupt'.
Simulates a real-mode interrupt, filling in *all* the registers from the
register struct. This means that unless `ss', `sp' and `flags' are set to
appropriate values or zero (which makes them be set to "sensible defaults"),
bad things will happen.
>  __dpmi_int(...)
Same as above, except it zeros `ss', `sp' and `flags' for you, yielding the
sensible defaults. That's why it's the one normally recommended to use.
>  _go32_dpmi_simulate_int(...)
Same functionality as `__dpmi_simulate_real_mode_interrupt', just a
different (obsolete) name and interface. Kept for hysterical reasons. :) (It
was the standard method in DJGPP v1.)

Nate Eldredge
eldredge AT ap DOT net