On Tue, 27 Feb 2001 06:33:51 -0500 (EST), Thomas Mueller wrote:
> from Sam Heywood:
>> I have had the experience of finding that WATTCP.CFG in some DOS internet
>> apps require that the location of PATH.CFG be specified as a relative
>> pathname instead of as an absolue pathname. This means that
>> "include=C:\ARACHNE\PATH.CFG" would not work in WATTCP.CFG in some apps
>> such as Bobcat or Lynx386. You might get an error message saying
>> "unable to locate path.cfg", even though the file does exist in the path
>> where you have specified it as an absolute path name.
> Or maybe some apps don't recognize the include? I think that's happened to me a
> few times with DOS Internet apps. In that case, specifying a relative path name
> instead of absolute path name won't save you. Besides, what if PATH.CFG is on a
> different drive letter? If necessary, you could copy PATH.CFG to every
> directory where needed.
I also have experienced the same king of problems, and for that reason I
also had adopted the procedure you recommend long before I even read your
post. I think your recommendation is a very good one.
All the best,
Sam Heywood
-- See our Big Gizmotimetemp at
-- http://banners.wunderground.com/banner/gizmotimetempbig/US/VA/Mt_Jackson.gif
