Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!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: Re: shrinking enviroment size
Message-ID: <45968@ut-emx.uucp>
Date: 21 Mar 91 20:22:12 GMT
References: <45673@ut-emx.uucp> <2419@umriscc.isc.umr.edu>
Distribution: usa
Organization: UT Austin
Lines: 19

In article <2419@umriscc.isc.umr.edu> mcastle@mcs213e.cs.umr.edu (Mike Castle {Nexus}) writes:
>Sounds less like running out of environment space than not quite knowing how
>DOS handles child processes.

Sorry if I was unclear, the problem is not that I want to change
the enviroment and have the changes propagate up, but rather, when
I am in Window's DOS box, or have spawned to DOS in another program,
I have problems since the batch files which I use to run programs
cannot add to the enviroment (because DOS shrinks it when I run
the program I've spawned out of).

In any case, one of the programs you mentioned may do what I want:
>ENV.ARC      PD1:<MSDOS.SYSUTL> Keep environment full size for child processes

Thanks for the response.  Thanks also to Richard Brittain
<richard@calvin.ee.cornell.edu> for his response.  He recommended
that I dump command.com in favor of 4Dos.

Brendan