Xref: utzoo comp.os.msdos.misc:1113 comp.os.msdos.programmer:3290 comp.os.msdos.apps:1021
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!ucsd!qualcom.qualcomm.com!rdippold
From: rdippold@qualcomm.com (Ron Dippold)
Newsgroups: comp.os.msdos.misc,comp.os.msdos.programmer,comp.os.msdos.apps
Subject: Re: PATH statement
Message-ID: <1991Feb11.201752.17466@qualcomm.com>
Date: 11 Feb 91 20:17:52 GMT
References: <26780@uflorida.cis.ufl.EDU>
Organization: Qualcomm Inc., San Diego, CA
Lines: 24

In article <26780@uflorida.cis.ufl.EDU> jdb@reef.cis.ufl.edu (Brian K. W. Hook) writes:
>
>My path statement has exceeded the legal limit allowed by DOS.  Is there
>any way to extend this?  I thought the standard way would be to do:
> [CONFIG.SYS Stuff]
>Since my environment space was initially set to 256bytes.  Adding another
>256 did not help.  I have one hard drive, so I have lots of stuff like:

Your line to increase the environment space was correct, but no matter how big
you make your environment, your PATH still has a limit of 127 bytes.  There's
no easy way around it except the standard methods:
  * Move your directories up in the tree
  * Shorten some directory names
  * Combine directories (move NORTON stuff into UTIL, etc.)
  * Don't include something in the PATH if you can make a batch file that
    will find it for you and run it.

A lot of software insists that you have its directory in the PATH.  This is a
bogus statement so they won't have to explain to you how to make a batch file
to run it...  For instance I don't have XTree in my path, I just have a file
called X.BAT in my \UTIL directory that invokes it at the correct location.
You will find that you can do this with most of your programs.

    D