Path: utzoo!attcan!uunet!pallas!kabra437
From: kabra437@pallas.athenanet.com (Ken Abrams)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Environment problems
Message-ID: <308@pallas.athenanet.com>
Date: 13 Mar 90 04:04:05 GMT
References: <1990Mar7.073215.23815@agate.berkeley.edu> <16558@orstcs.CS.ORST.E <699@pmday_1.Dayton.NCR.COM>
Reply-To: kabra437@pallas.UUCP (Ken Abrams)
Organization: Athenanet, Inc.,  Springfield, Illinois
Lines: 24

In article <699@pmday_1.Dayton.NCR.COM> dell@pmday_1.Dayton.NCR.COM (Jim Dell) writes:
>
>shell = c:\command.com /e:256 /p
>
>The e: parameter tells DOS how much to allocate, in this case 256 bytes
>
I thought I had seen this discussed on here.......
My shell statement is as shown above with /e:512.  Works fine.
My problem goes one step beyond this.  How do you get a child shell to
inherit more that the default amount of environment space?
Specifically, when I shell out of an application, I end up with only the
160 byte default environment in the child shell.  Since the child 
inherits about 155 bytes from the parent, this doesn't leave me much
to play with.
Now that I think about it a little more, it seems like I saw a post about
padding out the top level environment with a bunch of "filler" assignments
and them deleting them in the child environment.  Is there no better way?
This seems like a terrible kludge.

-- 
========================================================
Ken Abrams                     uunet!pallas!kabra437
Illinois Bell                  kabra437@athenanet.com
Springfield                    (voice) 217-753-7965