Date: Thu, 30 Sep 1999 15:45:34 +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: DJ Delorie <dj AT delorie DOT com>, djgpp-workers AT delorie DOT com
Subject: __dpmi_set_coprocessor_emulation
Message-ID: <Pine.SUN.3.91.990930153805.21365C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com

I have bumped into this while updating the docs of the DPMI 1.0 functions 
in libc.info.  The DPMI spec says that bit 0 of the argument, if set, 
enables the coprocessor for the DPMI client.  Bit 1, if set, means the 
client will supply the emulation.

If that is true, how come the startup code (in npxsetup.c) does this:

    /* Flags value 3 means coprocessor emulation, exceptions to us */
    if (__dpmi_set_coprocessor_emulation(3)) {
      _write(2, "Warning: Coprocessor not present and DPMI setup failed!\r\n"

Shouldn't it pass 2, not 3, as the argument?