On Tue, 27 Feb 2001 08:06:12 -0500 (EST) Howard Eisenberger wrote:
On Mon, 26 Feb 2001 09:55:31,
"Samuel W. Heywood" <[EMAIL PROTECTED]> wrote:
Quoting Howard Eisenberger:
> > I normally load the packet driver before running Arachne (see
> > Alejandro's message), so this is something I overlooked.
And I replied:
>> If you load the packet driver *before* loading Arachne, then you
>> can easily produce PATH.CFG by a routine you would include in the
>> batch file for loading the packet driver.
And Howard said:
> Of course, which is more or less what I do, although I put
> everything in wattcp.cfg and don't use include=path.cfg. I
> also configure config.tel for NCSA apps and autoexec.net/nos
> for KA9Q.
Then I said:
>> Please post your method of calling up and running Arachne
>> after you have first loaded the packet driver.
Howard replied:
> I run Arachne like any other Wattcp application by calling
> arachne.bat or a.bat. My arachne.cfg looks something like:
> [profile]
> Profile FASTPC.ACF
> Connection READY
> Hangup NUL
> [dialer]
> ;empty
> [tcp/ip]
> IP_Address WATTCP
> TCPconfig WATTCP.CFG
> [mail]
Thanks Howard. I just tried that myself and I really like it. Works great!
Some people prefer to load the packet driver from within Arachne. Since
reading your post and experimenting with your ARACHNE.CFG, it will be my
personal preference from now on to dial up and load the packet driver
*before* starting Arachne. Also it will be my personal preference to copy
PATH.CFG to the directory where Arachne is located and have the first line
of WATTCP.CFG say "include=path.cfg". Writing one's WATTCP.CFG file in
this way lends itself better to experimentation with the values used in this
file for different applications. I am not convinced that all WATTCP
applications will all run just as well with identical WATTCP.CFG files.
All the best,
Sam Heywood
.
..
