"Bob Buckland ?:-\)" <[EMAIL PROTECTED]> wrote:
>
>> Howard Eisenberger:As far as I know, PPPDRC.CFG contains the arguments
>> to EPPPD and WATTCP.CFG contains the arguments to the stack (and
>> application). Idon't think that EPPPD looks at WATTCP.CFG.
>
> Correct. Sometimes it's hard to explain what I'm seeing to
> others who are viewing from a different perspective :)
I know what you mean. :-)
> What I was saying was that using Netdial I don't
> use the PPPDRC.CFG file and (separately) that the inclusion
> of a COMn value for EPPPD to work is not required, except
> for Arachne's MiniTerm dialer if I recall.
It is these kinds of considerations that, IMHO, make it
preferable keep the arguments to the dialer (if you don't
use chat) separate from the arguments to epppd and separate
from the arguments to the stack/application. I find that
putting them all in one configuration file (arachne.cfg)
is confusing and can cause problems which are difficult to
troubleshoot.
> The Include capability I was mentioning for WATTCP was that
> taking BobCat for an example, I can, in that apps config file
> include 1 or more Include = c:\path\filename here lines
> in the Config file to make it part of th configuration file,
> something I had hoped Arachne.cfg would have so that when
> we get a new version we could separate the parts that we want
> to keep constant from the parts that are variable by machine,
> dial in number etc.
For me, something like the following accomplishes the same thing,
I think.
- ------ arachne.cfg -------
[profile]
Profile RESIDENT.ACF
Connection READY
Hangup NUL
# [dialer] none
[tcp/ip]
IP_Address WATTCP
TCPconfig WATTCP.CFG
- -------------------------
>> my batch file uses the environment variables from IP-UP.BAT
>> to write to WATTCP.CFG much like Netdial and the samples
>> in the Dospppd documentation.
> Yep, same thing except I don't write to a different file name and
> don't use the IP-UP as a separate .bat file, just an implementation
> variance :) I prefer the Netdial scripts to the Chat scripts
> because I can use comments and still read the thing when I don't
> change it for 6-8 months and figure out what I was doing <g>.
I like the chat scripts because they are exactly the same as the
ones I use in Linux (epppd is a DOS port of Linux pppd).
However. I think the main point in all of this is that, whatever
method you use, that once you've rolled your own that works, you've
probably got a pretty good understanding of what is going on and
you can be fairly confident that your setup will work with the
many different PPP applications.
I think it's one of those things that may seem incomprehensible
at first, but once you "get it", it seems almost trivial. I believe
that if people spent the time to learn how to load the packet
driver (the Dospppd documentation is quite good) and experiment a
bit, before diving into the larger applications, they wouldn't
have to spend so much time trying to troubleshoot the different
problems associated with different implementations.
--
Howard Eisenberger * Ottawa, Canada * <URL:http://www.ncf.ca/~ag221/>
