Date: Fri, 16 Jun 2000 06:03:43 +0600 (LKT)
From: Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender: kalum AT roadrunner DOT grendel DOT net
To: djgpp AT delorie DOT com
Subject: Re: dos color ?
In-Reply-To: <200006151721.WAA00659@midpec.com>
Message-ID: <Pine.LNX.4.21.0006160556580.1153-100000@roadrunner.grendel.net>
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 Thu, 15 Jun 2000, Prashant TR wrote:

> The DPMI spec., AFAIK, never tells you that calls like "INT 10h" are
> passed to real mode. That's what the function "simulate real-mode
> interrupt vector" is for.


But Eli clarified and said  that *all* interrupts are passed to real
mode..

IIRC the simulate real mode is really needed when you want to pass the
address of a buffer, ie to specify value for the segment registers...IMHO
it is no use if all one wants to do is to chage the screen resolution..ie
a simple int 10 in aassembly would do the trick...

 
> You also can't blame an extender for not passing INT 10h since you
> ought to be using the "right thing" to get the right results ;-).

Well a extender as it's name implies makes such operations *transparent*
to the user...all the extenders I know do a extrememly good job of
handling the segment registers etc during the DOS and BIOS function calls
it knows...for example it is possible to send a create directory request
under certain extenders with the buffer containing the text residing
completely in > 1mb memory...the extender copies the buffer to <1mb
changes the segment registers to appropriate values and executes the DOS
call..all tranparent to the user...magic indeed

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)