Howard_Spindel@busker.UUCP (Howard Spindel) (08/02/88)
Is there an easy fix for this, so that I may extend the environment
> space as needed in AUTOEXEC.BAT?
Yes, stick this in your config.sys file:
shell=c:\command.com /P /E:<desired environment size>
The environment size is specified in 16 byte paragraphs for DOS 3.1. In
later versions (I think starting with DOS 3.3) the environment size is
specified in bytes.
--
Howard Spindel - via FidoNet node 1:105/14
UUCP: ...!{uunet!oresoft, tektronix!reed}!busker
!Howard_Spindel
ARPA: Howard_Spindel@busker.UUCPRalf.Brown@B.GP.CS.CMU.EDU (08/03/88)
In article <1676@microsoft.UUCP>, jimw@microsoft.UUCP (Jim Walsh) writes: } A utility called SETENV.EXE has been shipping with Microsoft compiler }products for some time. It will modify your COMMAND.COM (Versions 2.0 }through 3.1) to set the size of your environment space to anywhere from }160 bytes (default COMMAND.COM) to 65,520 bytes. The syntax is Are you sure about the 65520 bytes? There is code in several places that flags environments larger than 32K as invalid and returns an error (error code 0Ah is "invalid environment", which is produced on environments >32K). -- UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=-=-=- Voice: (412) 268-3053 (school) ARPA: ralf@cs.cmu.edu BIT: ralf%cs.cmu.edu@CMUCCVMA FIDO: Ralf Brown 1:129/31 Disclaimer? I |Ducharm's Axiom: If you view your problem closely enough claimed something?| you will recognize yourself as part of the problem.