🚀 go-pugleaf

In-Reply-To: message from gjs@inmet.inmet.com
> One method is to use SUBST to assign some of the directories in your
> path to "virtual drives," then include the drives in your path.  For
> example:
> 
> subst E: C:\utility\word
> subst F: C:\utility\database
> subst G: C:\utility\sprdsht
> subst H: C:\utility\comm
> 
> path C:\bin;E:;F:;G:;H:
> 
> Double check my syntax.

Your syntax is fine!  I completely forgot about the SUBST command, and the
other uses I have found for it.  Here's a tip I discovered while hating
programs that require being in the path during use.  In your path, similar to
the above, include a dummy drive to be substituted.  When you call the program
via batch file, for example Word Perfect, you would SUBSTitute the dummy drive
with C:\WP50 or whatever.  Then, after WP is called, you can SUBST E: /d to
remove it, where E: is the dummy drive you've chosen.  I use this to get
around problem programs.  There is a problem with this, however.  First off,
instead of getting BAD COMMAND OR FILE NAME, you will get that and INVALID
DRIVE IN SEARCH PATH.  You may want to keep your dummy drives pointing to some
arbitrary place while not in use to avoid this.  Secondly, too many
substituted drives can fool many programs into believing you have seventeen
zillion drives installed.  The easiest solution I know of is to avoid a
CONFIG.SYS statement LASTDRIVE=X: that has a "far down the list" dummy drive. 
In other words, don't skip from E: right down to U:. 

Does anyone have any other tips, or ways to circumnavigate these problems?

                                                  
Eric W. Lund *DISCLAIMER "Disclaimers are for weak people."* Prodigy: xcbr22b
UUCP: ...crash!pro-graphics!elund *COWS FOR RENT* ProLine: elund@pro-graphics
Internet: elund@pro-graphics.cts.com ** ARPA/DDN: pro-graphics!elund@nosc.mil