Message-ID: <00e401be5062$64696b40$1e2d87ca@default>
From: "Maki Yoshimura" <maki DOT mail AT ibm DOT net>
To: <djgpp AT delorie DOT com>
Subject: RE: executible formats
Date: Fri, 5 Feb 1999 02:18:18 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-MIME-Autoconverted: from 8bit to quoted-printable by out5.ibm.net id RAA84454
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA07841
Reply-To: djgpp AT delorie DOT com

Somithing is wrong with your mailing list.
I have never register to your list.
So please do not send these kines of message again,
because I don't understand English language.

Regards

-----Original Message-----
差出人 : Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
宛先 : silkwodj AT my-dejanews DOT com <silkwodj AT my-dejanews DOT com>
CC : djgpp AT delorie DOT com <djgpp AT delorie DOT com>
日時 : 1999年2月5日 2:10
件名 : Re: executible formats


>
>On Wed, 3 Feb 1999 silkwodj AT my-dejanews DOT com wrote:
>
>> P.S.  I tried to reproduce a DPMI call (segment_to_selector) by preparing
my
>> own NASM function, based on the wrapper source.  Worked fine in DJGPP.
Took
>> the same module with the int 33h call and assembled to WIN32 (OBJ) and
linked
>> with MSVC(either 4.2 or 5.0, I forget) compiled fine, but execution
locked up
>> the machine with a black screen (really scarry).  Am I bumping into
something
>> new?
>
>AFAIK, this is just one of those free gifts you get from Microsoft:
>Win32 programs cannot issue software interrupts, including Int 31h
>(I'm guessing you meant 31h and not 33h, which is a mouse interrupt),
>because the software interrupt handler is in the VMM which assumes the
>caller is 16-bit code, and thus only saves the 16-bit registers on the
>stack.
>