🚀 go-pugleaf

In article <tsalagiDMDnwC.Gr3@netcom.com>, tsalagi@netcom.com writes:
>In article <311238e8.2685430@news.internetmci.com>,
>tomkat <tomkat@enterway.net> wrote:
>>On Thu, 01 Feb 1996 22:49:23 GMT, dhensley@connect.net (Dave Hensley)
>>wrote:
>>
>>>On 29 Jan 1996 17:49:57 GMT, John McDougall <johnm> wrote:
>>>
>>>>>>>>>Can I extend the length of the PATH somehow ?
>>>>>Cut your present Path line in about half and on the next line in your
>>>>>Autoexec.bat type
>>>>>path %PATH%;c:\etc etc etc
>>>>>Of course replace the etc's by the rest of your path statement
>>>>>
>>>>This will not extend your path. 
>>>
>>>Uh, yeah it will. If the first path statement in autoexec.bat is:
>>>
>>>path c:\123;c:\abc;c:\456;c:\def
>>>
>>>and a subsequent statement in autoexec.bat is:
>>>
>>>path %PATH%;c:\789;c:\ghi
>>>
>>>Then if you type PATH at the DOS prompt, it will return:
>>>
>>>path=c:\123;c:\abc;c:\456;c:\def;c:\789;c:\ghi
>>>
>>>and your path will indeed have been extended exactly as noted.
>>>
>>>
>>>				____
>>>				Dave
>>>
>>Dave is right.
>>
>
>Yes, but the question is:  When does the %PATH% expand itself?  Does
>"path %PATH%;c:\789;c:\ghi" get interpreted as
>"path=c:\123;c:\abc;c:\456;c:\def;c:\789;c:\ghi" right away, or does it
>indeed collapse the first path bit down?
>
>I think it gets expanded right away.... meaning that using %PATH% does not
>allow you to have longer paths than just doing it normally.
>
>-- 
The problem with this method is that the path can still become too long, and
MSDOS indiscriminately lops it off. I'm not sure what the limit is (I would
guess around 128 characters). I work in a computer lab where we run MS-Win/
dos and this is the brick wall we are beginning to run into. My solution is
to use append with the x:on option, however this can cause problems in 
certain situations.

Later,

TurboDave
dlpearce@eos.ncsu.edu
David L. Pearce
1984 Laser XE Turbo