Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!microsoft!michaelt
From: michaelt@microsoft.UUCP (Michael THURLKILL)
Newsgroups: comp.windows.ms
Subject: Re: Increasing command.com's environment space
Keywords: command.com
Message-ID: <55117@microsoft.UUCP>
Date: 11 Jun 90 00:31:14 GMT
References: <6574@vax1.acs.udel.EDU>
Reply-To: michaelt@microsoft.UUCP (Michael THURLKILL)
Distribution: usa
Organization: Microsoft Corp., Redmond WA
Lines: 22

In article <6574@vax1.acs.udel.EDU> bill@vax1.udel.edu (William Tsai) writes:
>Does anybody know how to increase the environment space used
>by variables when executing command.com in a window?
>Seems like SHELL= .. /E .. doesn't affect the copy of comman.com
>being executed in a window.
>
You need to create a .PIF file for command.com. In the 'Optional
Parameters' field, put in /E:xxxx. 
Also, when you spawn a command.com under Windows only the environment
space currently in use will be reserved. Thus if you have specified
/E:1024 in the shell line of config.sys, but you have only defined
256 bytes of environment variables, only 256 bytes will be reserved in
the spawned DOS VM. Use the above method to explicitely reserve the
desired environment space. Likewise, if you run an application that
requires addtional environment space, you create a .PIF with 
command.com as the 'Program Filename', and '/E:xxxx /C xxx.EXE' as 
the 'Optional Parameters.

Mike Thurlkill

Disclaimer: These are my opinions. They should be in no way misconstrued
as being correct or in any way related to my employer.