From:	"Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: loosing DOS memory by Windows NT
Date:	Tue, 14 Mar 2000 18:07:05 +0100
Organization:	http://news.icm.edu.pl/
Lines:	27
Message-ID:	<8alrke$r1r$1@sunsite.icm.edu.pl>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000314095146 DOT 4527J-100000 AT is>
NNTP-Posting-Host:	plus77.polkomtel.com.pl
Mime-Version:	1.0
X-Trace:	sunsite.icm.edu.pl 953053646 27707 212.2.96.204 (14 Mar 2000 17:07:26 GMT)
X-Complaints-To:	abuse AT news DOT icm DOT edu DOT pl
NNTP-Posting-Date:	14 Mar 2000 17:07:26 GMT
X-Newsreader:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii wrote
>
>On Mon, 13 Mar 2000, =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= wrote:
>
>What do you want to know?  AFAIK, NT simply leaks DPMI resources, that
>is, it doesn't free all of them in nested DPMI programs.  So after a
>while you are left with no selectors or no DPMI memory.
>


Perhaps it is possible to force to free selectors  that were used by a a
DPMI program
and that program have just finished executing. If this were possible would
it help?

My knowledge about DPMI has completely evaporated over last 4 years but is
it possible to distinguish if a particular selecter is "used" or not by a
program?

I assume it is not possible to allocate more selectors as this is a limited
resource

Just some ideas ...

- Raw text -