Date: Sun, 30 Apr 2000 08:45:46 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
cc: djgpp AT delorie DOT com
Subject: Re: 3rd Try: Maybe an asm problem? (Problems linking)
In-Reply-To: <390B87A0.2DDBDC4F@mtu-net.ru>
Message-ID: <Pine.SUN.3.91.1000430084510.27839B-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 Sun, 30 Apr 2000, Alexei A. Frounze wrote:

> > BTW, doesn't __dpmi_int switch to
> > real or virtual mode and do an interrupt (INT ##)?
> 
> Yes, it does. :) int*86*() also does the same because your program runs in
> PMode, so you must do a switch to RM/VM in order to access BIOS services. 

No, int86 issues the INT nn instruction in protected mode.