Date: Wed, 28 Sep 94 07:45:41 -0400
From: dj AT stealth DOT ctron DOT com (DJ Delorie)
To: buers AT dg1 DOT chemie DOT uni-konstanz DOT de
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: int86 vs. _go32_dpmi_simulate_int, bug?


First off, the 0x0100 flag is "resume nested task" which is a
system-level flag.  You're right, it probably should be masked.  The
documentation recommends you use memset() to initialize the structure
to all zeros, which would happen to fill this register also.

Secondly, in djgpp 2.0, int86 will be handled by calling
_go32_dpmi*(), as there will be no extender at that point.  It will
still be functional for those things supported by exphdlr.c now, but
even now there are lots of functions it doesn't support.