Date: Tue, 5 Oct 1999 09:48:28 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com
Subject: Re: __dpmi_set_coprocessor_emulation
In-Reply-To: <9910042104.AA17222@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.991005094804.2899D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Mon, 4 Oct 1999, Charles Sandmann wrote:

> 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.

Oh, yeah.  Forgot about that.  Thanks.

> 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.

Does anyone here have access to OS/2 and an hour to run a test on it
with modified npxsetup?