🚀 go-pugleaf

mrestifo@wizvax.net (Mark J. Restifo) wrote:

" On Sat, 17 Feb 1996 20:46:07 GMT, in comp.archives.msdos.d,
" zil@azstarnet.com (Zilbandy) recently put forth:
" 
" >| George Seaman  CRL <hi-tech@aloha.com> wrote:
" 
" >| >The best way if you wish to extend the path is to use a diffrent dos
such 
" >| >as "4DOS " in lieu of that you should shorten the directory names. ie. 
" >| >Windows becomes win or w \ lotus becomes 123 or SSL (spread sheet
lotus).
" 
" >| I did this once. (shorten directory names) Boy what a pain...
" >| Unless you want to spend a couple of hours changing every
" >| c:\windows line to c:\win in all the ini files and for many icons
" >| in various groups,
" 
" Actually, many programs automatically look in the c:\WIN or c:\WIN\SYSTEM
" directories for various dll's. Shorter dir names do help, but if you have
" to have a lot of them in the path, after a while it becomes the law of
" diminishing returns. What I do is use the full C:\blah\blah path in my
" program groups, as windows doesn't really need to search the path most
" times - it already has the program paths stored. I then use the SUBST
" command in my autoexec.bat for any of the longer directory paths I wish to
" use in the path. This way my path is shorter and the net effect is
" achieved:
" 
" path=c:\;c:\win3;d:\;e:\bin;etc

I'm confused.  According to the on-line help in DOS 6.22:

	"Do not use the SUBST command when Windows is running."

Can I infer that one shouldn't SUBST drive ID's while Windows is running, but
that any drive ID's created before Windows starts (as in autoexec.bat) will be
handled properly by Windows?

--
Ron Hill (ron@canuck.com)