Path: utzoo!news-server.csri.toronto.edu!rutgers!ucla-cs!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!rphroy!caen!news.cs.indiana.edu!know!cs.utexas.edu!ut-emx!boerner
From: boerner@ut-emx.uucp (Brendan B. Boerner)
Newsgroups: comp.sys.ibm.pc.misc
Subject: shrinking enviroment size
Message-ID: <45673@ut-emx.uucp>
Date: 16 Mar 91 02:37:41 GMT
Distribution: usa
Organization: UT Austin
Lines: 20

My configuration:
	HP Vectra QS/16S w/4MB
	HP DOS v3.30
	Qualitas 386Max v5.1

I've found that when trying to run batch files from within/when
shelled out from other programs (from the process buffer in Epsilon,
in the Windows DOS box, shelling out from Turbo C++, etc...), I have
very little enviroment room to add variables to.  I should have enough
room, I'm setting my enviroment size to 4K in config.sys (I bumped it
up there I noticed this happening and haven't dropped back down.
Doing a SET > TMP.TXT reports that TMP.TXT is less than 1K in size).
I'm now guessing that either DOS will take the current size of the
enviroment and use that for spawned programs, or the programs will
limit the enviroment themselves.

Does anyone know how I can get around this behavior?

Thanks in advance,
Brendan