Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!hp-pcd!hplsla!davidr
From: davidr@hplsla.HP.COM (David M. Reed)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Run out Environment in DesqView Windows
Message-ID: <5190008@hplsla.HP.COM>
Date: 24 Apr 89 18:21:01 GMT
References: <8904211719.AA24430@decwrl.dec.com>
Organization: HP Lake Stevens, WA
Lines: 19

I do not know the reason for the problem.  I suspect that, though you may
reserve extra environment space with the /E option in CONFIG.SYS, if that
space is not all in use when DESQview starts up then you lose most of it
(as though it were "free" memory).  To deal with this, I create a variable
in my AUTOEXEC.BAT file that fills up a lot of space:

SET XX=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

You could do this with one or more variables, each using as much space as you
want to reserve.  Then I have DESQview start programs with a BATch file that
specifies

SET XX=

This will free up all of the environment space used by the variable, which
will then allow longer PATH or PROMPT definitions, or the defining of other
variables unique to that window/program.

It certainly is not glamorous, but it really works well for me.