From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10104232231.AA19751@clio.rice.edu>
Subject: Re: win2000/ntvdm/djgpp (fwd)
To: eliz AT is DOT elta DOT co DOT il
Date: Mon, 23 Apr 2001 17:31:43 -0500 (CDT)
Cc: theowl AT freemail DOT c3 DOT hu, djgpp-workers AT delorie DOT com
In-Reply-To: <2427-Tue24Apr2001004115+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Apr 24, 2001 12:41:16 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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?  If so, we could set the PSP in the exit code.  This would
> solve both the normal spawn and the case of abnormal termination via
> Ctrl-C, because the parent will restore its PSP just before it exits.

Reading through the thread, this was my thought on the way to fix it also.
I would also possibly set the PSP on the return from exec to help protect
from the case where we sometimes call _exit and don't go through the
exit handler.  Setting and re-setting the right value should not cause 
a problem...

To get W2K to see it, do we need to do a dpmi_int with the real mode PSP,
or a protected mode Int 21 with the PM selector for the PSP?