Date: Wed, 15 Jul 1998 10:11:05 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Mariano Alvarez Fernández <malfer AT teleline DOT es>
cc: djgpp AT delorie DOT com
Subject: Re: About DJGPP v2.02
In-Reply-To: <35AB757C.3DDD@teleline.es>
Message-ID: <Pine.SUN.3.91.980715101047.10743G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Tue, 14 Jul 1998, Mariano Alvarez Fernández wrote:

> I saw in the docs _dpmi_yield calls int
> 2Fh, function 1680h. Do you know if it works with 16-bit programs too?.

It is documented to work with any program.

Please note that the stock library version of __dpmi_yield calls
Interrupt 2Fh by emitting an INT instruction.  It turns out that doing
that with INT 2Fh hangs the calling program after it launches a child
DJGPP program, on certain rare variants of Windows 95 (seems like a
Windows bug).  It has been determined that calling INT 2Fh via
__dpmi_int avoids this problem.  So I suggest to write your own
version of __dpmi_yield that uses __dpmi_int, and use that (DJGPP
v2.02 will have this change in the library).

The last consideration pertains only to 32-bit DPMI programs such as
what DJGPP produces.  I don't know if this problem exists in other
types of programs that can be run from a DOS box.