From:	"west.usenetserver.com" <glenm AT myself DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<Jrgd5.4951$mL5 DOT 200531 AT news-west DOT usenetserver DOT com> <8l4a7o$rpc$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
Subject:	Re: Updating the program caller's environment from the called program
Lines:	13
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID:	<pCkd5.153$2M5.5697@news-west.usenetserver.com>
X-Abuse-Info:	Please be sure to forward a copy of ALL headers
X-Abuse-Info:	Otherwise we will be unable to process your complaint properly
X-Complaints-To:	support AT usenetserver DOT com
NNTP-Posting-Date:	Wed, 19 Jul 2000 12:23:49 EDT
Organization:	WebUseNet Corp http://www.usenetserver.com - Home of the fastest NNTP servers on the Net.
Date:	Wed, 19 Jul 2000 18:23:44 +0200
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Within the limits of 'documented' DOS services, you can't do that. You
> have to do some dirty undocumented tricks to walk the chain of memory
> blocks managed by DOS, and find the environment of the calling
> program. One big problem with this is that this environment block will
> often not have enough 'slack' space to store big changes in,
> i.e. you'll likely end up with 'out of environments space' situations.

True enough...  Any idea where one can find these "undocumented tricks"?

- Raw text -