Path: utzoo!attcan!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!maytag!watstat!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.sys.ibm.pc
Subject: Re: How can I set a PATH longer than 128 bytes ?
Keywords: path environment
Message-ID: <1684@maytag.waterloo.edu>
Date: 8 Mar 90 15:06:36 GMT
References: <5762@ncrcae.Columbia.NCR.COM> <17140003@hplred.HP.COM> <1990Mar8.021622.13121@cec1.wustl.edu>
Sender: daemon@maytag.waterloo.edu
Reply-To: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Organization: U. of Waterloo, Ontario
Lines: 25

In article <1990Mar8.021622.13121@cec1.wustl.edu> jcb2647@cec1.wustl.edu (James Christopher Beard) writes:
>
>If your path is of horrible length for some reason other than trying
>to keep every known executable available at once, you can shorten the
>number of characters in the path by giving some of the directories
>"aliases" using the SUBST command a la 
>
>	SUBST E: C:\PROGRAMS\JOE\WORDPROC\WP
>
>Then you can include the virtual drive E: in your path.  Two notes,
>though: 1) SUBST mustn't be used in a networked environment, which
>seems like the place you're most likely to need it, and 2) for the
>above to work, you need a command of the form "LASTDRIVE=E" in
>CONFIG.SYS, where you replace "E" with the name of the
>highest-lettered drive or virtual drive you will ever want to refer
>to.

Just out of interest:  what goes wrong in a networked environment?  I've
been running for years (non-networked) with 
  SUBST E: C:\
in my autoexec; it makes it easy to maintain two views of the same disk,
since I can CD independently on C: and E:.  What's going to go wrong
if I ever hook up to a network?

Duncan Murdoch