X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112111444.AA18461@clio.rice.edu>
Subject: Re: go32-v2 memory chompage [was: Re: v2.03 refresh ...]
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 11 Dec 2001 08:44:38 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au
In-Reply-To: <Pine.SUN.3.91.1011211130101.1978A-100000@is> from "Eli Zaretskii" at Dec 11, 2001 01:03:14 PM
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 don't see how a child program could know if it was run from 
> > go32-v2
> 
> I will try to think if there's a way, but even if there isn't, we could 
> arrange to have some way from now on.

I thought about comparing the results of getpsp with the si
I thought about comparing the results of a _dpmi_int getpsp (rm) with si

> > (If there is a way in dosexec to make it call go32-v2 less frequently,
> > should we consider that?)
> 
> I think the CVS version already does that.

Yes, but there are like 15 changes (some really major) in dosexec vs
2.03 - including all sorts of things we can't support.  If someone who
understands it bettter would point me at the revision which improved
this - great.  (If only the coff exists I don't see any way to avoid
calling go32-v2, but maybe we search for extensions if none?)