Date: Sun, 18 Jun 2000 08:30:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: smile773 <smile773 AT bigfoot DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: __go32__dpmi ?
In-Reply-To: <O2T25.7196$C44.412796@bgtnsc05-news.ops.worldnet.att.net>
Message-ID: <Pine.SUN.3.91.1000618082459.14456L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 17 Jun 2000, smile773 wrote:

> Thankyou Eli,
> you replyed : Why would you need to implement it?
> 
> Because I still need all those troublesome 16 bit realmode utilities
> to operate.
> 
> I am trying to find a good place to CATCH them so they
> will leave screen color and text up to the user.

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.