Date: Tue, 14 Mar 2000 09:52:03 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
cc: "'djgpp AT delorie DOT com'" <djgpp AT delorie DOT com>
Subject: Re: loosing DOS memory by Windows NT
In-Reply-To: <13288F4408ADD11186FF0060B06A431303341383@MSGWAW1>
Message-ID: <Pine.SUN.3.91.1000314095146.4527J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 13 Mar 2000, =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= wrote:

> My apologies if I should have written this to the newsgroup instead of a
> private message. 

You did post this to the news group.

> I'm referring to section 3.3 of the DJGPP FAQ. I wonder if you could point
> me to more descriptive explanation of  what "loosing DOS memory  by Windows
> NT" means so that I could work over this.
> 
> The messages "No DPMI memory" and "No DOS memory" become more annoying as
> the development on long filename support progresses and I need to find a way
> to avoid them 

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.

I don't think anyone knows more than what the FAQ already says,
because we don't have any access to NT sources.