Xref: utzoo comp.sys.ibm.pc:46842 comp.sys.ibm.pc.programmer:507
Path: utzoo!attcan!uunet!cs.utexas.edu!news-server.csri.toronto.edu!qucdn!gilla
From: GILLA@QUCDN.QueensU.CA (Arnold G. Gill)
Newsgroups: comp.sys.ibm.pc,comp.sys.ibm.pc.programmer
Subject: Re: Path extension above 128 characters
Message-ID: <90079.083313GILLA@QUCDN.BITNET>
Date: 20 Mar 90 13:33:13 GMT
References: <5986@star.cs.vu.nl> <1990Mar16.123731.3224@world.std.com>
 <1034@manta.NOSC.MIL> <1990Mar20.014733.3747@eagle.lerc.nasa.gov>
Distribution: na
Lines: 27

In article <1990Mar20.014733.3747@eagle.lerc.nasa.gov>,
tfabian@mars.lerc.nasa.gov (Ted Fabian) says:
>
>the real issue here is not the length of the PATH.. rather it's the amount
>of environment space you've got allocated...
>
>as long as you don't load an RAM resident programs, you can use "ANY"
>amount of environment space you want to.. which means any length path...
>
>or you can use the /E switch on the SHELL command in your CONFIG.SYS
>to define a larger default environment.. something like
>
>   SHELL COMMAND.COM /E:1024
     In a word, nonsense.  I have exactly the above command in my CONFIG.SYS,
with no TSRs, and the PATH is still not capable of accepting more than 128
characters.  This is a MS-DOS defect, and if you have a fixed up version of
DOS, good for you.  Most of do not, and we have to work around this flaw by
writing directly to the environment.  Luckily, this is easy to do, as several
other postings have shown.
-------
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|  Arnold Gill                        |                                     |
|  Queen's University at Kingston     |     If I hadn't wanted it heard,    |
|  BITNET   : gilla@qucdn             |       I wouldn't have said it.      |
|  X-400    : Arnold.Gill@QueensU.CA  |                                     |
|  INTERNET : gilla@qucdn.queensu.ca  |                                     |
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-