Hi Glenn,
Ummm, not quite :) But it's not really a big deal.
I use Netdial and a batch file with EPPPD. I never have a PPPDRC.CFG,
EPPPD needs the variables fed to it from somewhere, it's not pick on from
where, which can be an issue with Arachne.cfg if you switch ISPs to dial into.
(i.e. you have to keep all the Arachne.cfg files in synch since you can't
call the dial script separately).
Depending on the PC I tell it in the batch file either the COM port or the Base
address. Michael mentioned some time back if I recall that the serial port
library he used in Miniterm needed a COM n address stated and yes
that does mess up things with DOSPPPD if it finds a base address &
a COM n number. Michael's posting today sounds like he's solved it
though in what will be written out for pppdrc.cfg based on the
IRQ setting, but it should be based more on the Base address setting
I think.
Netdial is also a freebie and does not take as much memory as Miniterm.exe
does to run and lets you decide where the script file is <g> and didn't
have the problem with the base address/COM issue as much.
Bob ?:-)
==========
<<"Glenn McCorkle":
Miniterm.exe uses information from arachne.cfg (no other file is needed)
Core.exe creates pppdrc.cfg using information taken from arachne.cfg and
from the output of miniterm.exe
Epppd uses information from pppdrc.cfg (no other file is needed)
One piece of information which epppd.exe *absotutly must* have......
"base port address". (it *will not* work without it).
If the base port address is not shown in pppdrc.cfg, then epppd.exe
looks at the BIOS reporting table to find the address of the com port
which *is* shown in pppdrc.cfg
If the com port is not shown in pppdrc.cfg, then the base port address
*must* be shown. (if it's not, then epppd.exe has no way of knowing
which port address to use) >>
=============
