Herb,
I am out of town and away from my computer with your Arachne.cfg file posted,
so excuse me if I am not remembering something.
(See embedded comment near end of quoted part.)
In your post of 12 October 2000, you wrote:
>>My last posting on this topic did not make it to the digest. So I am
reposting it. I appologize if anyone receives it twice.
2000/10/07
Dear Listers
Still no cigar I am afraid.
As a definitive test of the serial port gap possibility, I disabled
the serial ports on COM1 and COM2 and reconfigured the modem to COM1.
The serial ports are on the mother board so they had to be disabled in
setup. This made no change in the situation.
Question: Would the modem initializing string cause a problem even
though it works that far.
Responses to the last messages:
Roger Turk wrote:
>I don't follow the, "waiting for >" lines as you did not indicate
>anything like this in describing you manual logins. I have added
>recommendations on your Arachne.cfg post:
Actually, neither did I. It was already embedded in the default script
and I did not know what to do with it. Leaving it blank as you and
Clarence Verge suggested got me past that road block. However, no
change in the problem. Here is a screen dump of the automatic dialog.
It looks normal to me up to loading the packet driver.
CONNECT 9600/ARQ/V34/LAPM/V42BIS
* Autologin is enabled in Arrachne.cfg ---etc----
* Trying login. -----etc------
* [1] waiting for login:
Welcome to 3 Com ------blah, blah,
Networks that go -----blah,blah
login:
* [1] Received: 'login'
* [1] answering: Pvalliant
* [2] waiting for "sword"
Pvalliant
Password:
* [2] Received: "sword"
* [2] Answering: "******"
* [3] Answering: PPP <---Do you have, "PPP" in your script? If
so, why?
* Leaving miniterm and trying SLIP/PPP etc
PPP Link is down: driver not installed.
After a pause a screen entitled "Unable to initialize PPP" <<
Can't think of any other comment at this time.
Hope this helps.
Roger Turk
Tucson, Arizona USA
