🚀 go-pugleaf

fac@burdvax.UUCP writes:
>> 
>> have a problem using the hard  drive.  I can't seem to run programs that
>> have support files associated with them (Procomm, Emacs, etc) from any
>> directory other than their resident directories.  Specifically, if I'm
>> in directory \games, and want to run, say PROCOMM in drive \comm, how do
>> I do this?
>Well, for Procomm, there is an environment variable which tells
>procomm.exe where to look for its initialization files. Mine is
>set procomm=c:\com\procomm since that is the directory where the
>initialization/config files are. If your application doesn't
>support environment variables (pc-write, forinstance) then
>make a bat file and store it in \bat.

I believe that such environment variables generally want a directory path that
is terminated with a slash; e.g. I use
	set PROCOMM=C:\TERMINAL\PROCOMM\
Also, I'm using PC-Write v2.55, and it does utilize an environment variable
(viz., set PCWRITE=C:\WORDPROC\).  In my experience the case was important --
all uppercase works, anyway.  And finally, some programs that want overlays and
don't know where to look, such as Wordstar, can be fooled by using a program
that takes the place of the PATH, such as Search or DPath.  I used Search with
version 3.7 microEmacs to find the emacs.rc file (but v3.8 knows to check the
PATH variable, now).
	p.s.  ARC uses the variable ARCTEMP to locate its working files (real
good if you're archiving onto a floppy).  Does anyone know offhand whether
PKARC uses an environment variable?  It just occurred to me that I never changed
that when I started using Katz's product.