Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!oliveb!pyramid!prls!philabs!ttidca!svirsky
From: svirsky@ttidca.TTI.COM (Bill Svirsky)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Re^2: Paths > 128 characters AND OTHERS "FLAME"
Message-ID: <3971@ttidca.TTI.COM>
Date: 1 Mar 89 17:33:01 GMT
References: <IXzd6py00W0Z824VRm@andrew.cmu.edu> <455@ambone.UUCP> <7011@siemens.UUCP>
Reply-To: svirsky@ttidcc.tti.com (Bill Svirsky)
Organization: Citicorp/TTI, Santa Monica
Lines: 19

In article <7011@siemens.UUCP> jrv@siemens.siemens.com (James R Vallino)writes:
+ What you are confusing here is what DOS can internally handle
+ for an environment variable and the DOS command line buffer.  The
+ command line buffer is around 128 characters long.  This is what limits
+ the size of the environment variable when using the SET command. 
+ 
+ DOS itself can handle a PATH variable longer than 128 characters.  The
+ problem is how to get the value set in DOS's environment space.  I have
+ seen one or two utilties which directly mess around with DOS's internal
+ environment space to create very long PATH variables.  Unfortunately I
+ do not remember the names of them

I just confirmed this.  I used "nset" from the PICNIX toolset to set
PATH=<approx. 160 characters of directories>;c:/bin, and was able to
execute a program from /bin.
-- 
Bill Svirsky, Citicorp+TTI, 3100 Ocean Park Blvd., Santa Monica, CA 90405
Work phone: 213-450-9111 x2597
svirsky@ttidca.tti.com | ...!{csun,psivax,rdlvax,retix}!ttidca!svirsky