Date: Mon, 22 Feb 1999 13:26:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp AT delorie DOT com
Subject: Re: Does Windows 98 lose DMPI descriptors?
In-Reply-To: <Pine.A41.4.05.9902190949200.50776-100000@ieva01.lanet.lv>
Message-ID: <Pine.SUN.3.91.990222132507.15762C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Fri, 19 Feb 1999, Andris Pavenis wrote:

> Here is some example I used to test this.
> 	Win95 (also OSR2) and Win98 - yes all these versions lose
> 				descriptors
> 	WinNT 4.0+SP3 - seems that this problem is not present
> 
> Don't ask me about numbers there. Simply I have thrown latest source
> of program I haven't run about a month.

A slightly modified version of this program fails on my Windows 95
system after 2040 calls to spawn, and the error message says "No DOS 
memory" (probably because the Windows DPMI server runs out of selectors 
for DOS memory).

The DOS box doesn't crash after that, btw.  I'm just dumped to the
command prompt and if I invoke the test program again in the same DOS
box, it again loops 2040 before failing.

So it seems that when the outmost DPMI program exits, Windows does
clean up.  The problems are with nested invocations.