Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!aero-c!gumby.dsd.trw.com!deneva!wiley!rich
From: rich@wiley.uucp (Rich Messenger)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Environment Space
Summary: some hacks
Keywords: n
Message-ID: <28210533.D0@wilbur.coyote.trw.com>
Date: 3 May 91 06:37:38 GMT
References: <8361@drutx.ATT.COM>
Sender: news@wilbur.coyote.trw.com (News Software)
Distribution: comp
Organization: TRW, Redondo Beach, CA
Lines: 27

In article <8361@drutx.ATT.COM> fjb@druwa.ATT.COM (Jeff Bogart) writes:
>When I run a non-windows application from windows, I seem to create a "default"
>environment that is too small to add new environment variables or to extend my
>PATH.  Is there some way of telling windows what size to reserve for
>environment variables?
>
>I can't seem to find anything mentioned about this topic in the Windows
>documentation.

How about a simple hack: before you invoke windows, set a scratch
environment variable (making sure your command.com has a big enough
environment space):

	SET scratch=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Then, instead of invoking the non-windows application directly, call a
batch file which first unsets the environment variable.  This will
free up that space in the environment.

	SET scratch=
	...rest of batch can now add to path, etc...

I know: UGLY.  But it probably works.
     _ __
    ' )  )      /                      ... Rich Messenger
     /--' o _. /_                          rich@wilbur.coyote.trw.com
    /  \_(_(__/ /_                         {uunet,cit-vax,trwrb}!wiley!rich