From: "The Owl" <theowl AT freemail DOT c3 DOT hu>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date: Tue, 24 Apr 2001 14:02:36 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: win2000/ntvdm/djgpp (fwd)
CC: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com
Message-ID: <3AE5877C.20112.5DE2349@localhost>
In-reply-to: <2427-Tue24Apr2001004115+0300-eliz@is.elta.co.il>
References: <3AE4B120 DOT 2679 DOT 298CA28 AT localhost> (theowl AT freemail DOT c3 DOT hu)
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I have an idea.  Is it true that _running_ when _CurrentPSPSelector is
> zero is okay, and that only _exiting_ when it is zero causes NTVDM to
> crash?

yes, that's right. to be more precise, exiting while _CurrentPSPSelector
is 0 will not crash ntvdm per se, it will 'only' make ntvdm free the
wrong memory blocks (whose 'owner' field is 0, which happens to be true
for this exception stack and god knows what else), and next time any
hardware interrupt is going to be reflected - page fault.

>  If so, we could set the PSP in the exit code.

yes, this was my idea too, but i did not know the djgpp code that well
(mind you, at all), so probably suggested the wrong place to patch ;-).