From: "smile773" <smile773 AT bigfoot DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000618082459 DOT 14456L-100000 AT is>
Subject: Re: __go32__dpmi ?
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <vI535.7379$Uw3.474577@bgtnsc04-news.ops.worldnet.att.net>
Date: Sun, 18 Jun 2000 15:15:39 GMT
NNTP-Posting-Host: 12.72.66.121
X-Complaints-To: abuse AT worldnet DOT att DOT net
X-Trace: bgtnsc04-news.ops.worldnet.att.net 961341339 12.72.66.121 (Sun, 18 Jun 2000 15:15:39 GMT)
NNTP-Posting-Date: Sun, 18 Jun 2000 15:15:39 GMT
Organization: AT&T Worldnet
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


>
> The calls to Int 10h made by real-mode applications cannot be caught by
> hooking a protected-mode interrupt, because the RM programs don't call
> these interrupts in protected mode.
>
> What you need is to hook Int 10h in *real* mode.  One way of doing so is
> to install a real-mode callback as a handler for Int 10h.  The DJGPP FAQ
> describes how to do that in section 18.8.
>
> I should warn you up front that real-mode callbacks have some downsides;
> for starters, they are non-reentrant.
*********************************************************************
Does non-reentrant mean that the attributes bytes can be swapped only as
they
are caught and not after the application completes ?