Path: utzoo!attcan2!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!acornrc!bob From: bob@acornrc.UUCP (Bob Weissman) Newsgroups: comp.sys.ibm.pc Subject: Re: Another twist on DOS environment sizes. Message-ID: <849@acornrc.UUCP> Date: 1 Jun 88 20:09:30 GMT References: <629@fxgrp.UUCP> <4598@dasys1.UUCP> <835@acornrc.UUCP> <14488@mirror.TMC.COM> Organization: Acorn Research Center, Palo Alto, CA Lines: 26 In article <14488@mirror.TMC.COM>, jvc@mirror.TMC.COM (Jim Champeaux) writes: > I must be missing something. Why patch command.com when you can use > the config.sys file to specify an environment size larger than the > default (versions 3.xx and up, maybe not 3.0)? I would understand it > if secondary shells always used the default size, but they don't. > The environment of the secondary shell is always at least as large as > the shell it was started from. The environment of the secondary shell > can even be made larger than its parent's environment (by using the > /e switch). Because, as mentioned in an earlier article today, specifying shell=command.com /e:nnnn in config.sys prevents execution of autoexec.bat. I too tried various combinations of /e, /c, and /p but could not get the default behavior to occur. Also because I enjoy hacking on this machine :-) and feel that MicroSoft's default of only 160 bytes is too low and a one-word patch takes care of the problem once and for all. I.e., why *not* patch command.com? -- Bob Weissman Internet: bob@acornrc.uucp UUCP: ...!{ ames | decwrl | oliveb | pyramid }!acornrc!bob Arpanet: bob%acornrc.uucp@ames.arc.nasa.gov