Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.14 $; site siemens.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!siemens!jrv
From: jrv@siemens.UUCP
Newsgroups: net.micro.pc
Subject: Re: COMMAND.COM and environment strings
Message-ID: <23900027@siemens.UUCP>
Date: Fri, 20-Jun-86 10:14:00 EDT
Article-I.D.: siemens.23900027
Posted: Fri Jun 20 10:14:00 1986
Date-Received: Sun, 22-Jun-86 04:19:00 EDT
References: <9889@ucsfcgl.UUCP>
Lines: 18
Nf-ID: #R:ucsfcgl:-988900:siemens:23900027:000:857
Nf-From: siemens!jrv    Jun 20 10:14:00 1986



When the environment is sized for the initial running of COMMAND.COM the
default of 160 bytes (or expanded if you have put in the proper options
on SHELL or pathed COMMAND.COM etc...) limits how big the operating
system copy of the environment can grow. When a transient program gets
loaded the copy of the environment it gets passed only contains the
part of the environment which is used. Any unused space does not get 
copied. The basic problem is to create some dummy space in the environment.
You might try defining several environment variables which take up a lot
of space. Then when the second copy of COMMAND.COM is run you can get
this space back by undefining the variables in the batch file run by this
transient COMMAND.COM.

Jim Vallino
Siemens Research and Technology Lab.
Princeton, NJ
{allegra,ihnp4,seismo,philabs}!princeton!siemens!jrv