Xref: utzoo comp.os.msdos.misc:1150 comp.os.msdos.programmer:3357 comp.os.msdos.apps:1054
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!decwrl!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!IDA.ORG!rlw
From: rlw@IDA.ORG (Richard Wexelblat)
Newsgroups: comp.os.msdos.misc,comp.os.msdos.programmer,comp.os.msdos.apps
Subject: Re: PATH statement
Message-ID: <1991Feb14.123101.683@IDA.ORG>
Date: 14 Feb 91 12:31:01 GMT
References: <26780@uflorida.cis.ufl.EDU> <1991Feb11.201752.17466@qualcomm.com>
Reply-To: rlw@IDA.ORG.UUCP (Richard Wexelblat)
Organization: IDA, Alexandria, VA
Lines: 22


A good way to handle long paths and infrequently used directories that
will work both in windows and outside is to set up a series of bat
files in your local equivalent of /bat or /usr for these infrequently
used directories.

Thus, the way I get into Norton or my infrequently used database of
stickylabels is through a bat file that does the following:

save the path
set the path to just the directory of current interest (+ root)
run whatever I want to run
restore the path

If you call one of these things recursively, you'll loose the original
path, though.  But there are ways to get around this, too if you really
need to recurse.  The disadvantage of this is having to have extra bat
files and ending in semi-limbo if you ^C out of the bat file.  So there's
an oops.bat that restores the original path for me.
-- 
--Dick Wexelblat  (rlw@ida.org) 703 845 6601
  Only vampires don't have to look at themselves in the mirror.