Date: Sun, 3 Oct 1999 13:24:32 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT delorie DOT com>, sandmann AT clio DOT rice DOT edu,
        djgpp-workers AT delorie DOT com
Subject: Re: __dpmi_set_coprocessor_emulation
In-Reply-To: <Pine.SUN.3.91.991003115450.16555A-100000@is>
Message-ID: <Pine.SUN.3.91.991003132224.16939M-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 Sun, 3 Oct 1999, I wrote:

> The DPMI v1.0 Spec explains on p.150, under the decscription of
> function 0E01h, that bit 0 specifies the new value of the MPv bit,
> whereby 0 disables the coprocessor, and then says in the Notes:
> "Floating point emulation can be tested on a system with a numeric
> coprocessor by using this function to enable client handling of
> coprocessor exceptions and disable the coprocessor."  Here, ``disable
> the coprocessor'' seems to imply that the MPv bit should be reset.

FWIW, I've run several FP programs after changing the startup code to 
call __dpmi_set_coprocessor_emulation with an argument of 2 instead of
3, under CWSDPMI, QDPMI and Windows, and didn't see any differences.