From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9910042104.AA17222@clio.rice.edu>
Subject: Re: __dpmi_set_coprocessor_emulation
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Mon, 4 Oct 1999 16:04:08 -0600 (CDT)
Cc: dj AT delorie DOT com, djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.991004102711.23739B-100000@is> from "Eli Zaretskii" at Oct 4, 99 10:27:28 am
X-Mailer: ELM [version 2.4 PL20]
Content-Type: text
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

I don't have time right now to plow through all this stuff, so...

CWSDPMI doesn't futz with the bits - it just sets the emulation
handler.  There is some stuff I forget about task swaps and 
setting a bit so you can save/restore the FPU state.  This is the
trigger which causes emulation/execution.

Some of this was due to some architecture change between 386/486
that I don't remember.  Some was just convenience that never got
fixed.

As far as the flags for the DPMI calls - I don't remember the details
but I do remember the triad of Win 3.0, Win 3.1, and OS2 pretty
much required what was there - so I'd be very careful changing it
without testing those three.

Sorry to not be much help - but I just messed with my stepdaughter's
wedding this weekend and am trying to get caught up at work as a 
byproduct