Very Computer

I swear it's chat's problem.

I can get linux to connect using xisp and x-windows, not a worry. I can also
get it working by pressing activate on the Network configurator. I can get
my modem dialing into my ISP from the command line using minicom. I have the
right pot: cua0, ttyS0, and modem. (using /dev/modem works with x-windows
and minicom)

However, if I follow the How-to's and set up a pppd/chat script combination,
it will not work.

When executing the script, I can see that the ATZ command gets through...
the modem hangs up. Great. But then it makes no attempts to dial. No lights
flicker, no sound comes out. I tried running just chat without pppd to see
the output, and it runs... ATZ command is sent, then nothing else.

Connect script is:

pppd connect 'chat "" "ATZ" "" ATD 90917055 CONNECT "" ogin: login word:
password' /dev/modem 57600 modem

All the information is correct (except passord and login of course) But the
modem doesn't even seem to dial.

I've tried to echo commands to the modem:

echo ATZ > /dev/modem

I dont get an error message, but it doesnt do anything (Like it would in
DOS). Any help would be appreciated... WHY WONT IT WORK FROM THE COMMAND
LINE!!!!! *grrrrr*

: I swear it's chat's problem.

:)

: Connect script is:

: pppd connect 'chat "" "ATZ" "" ATD 90917055 CONNECT "" ogin: login word:
: password' /dev/modem 57600 modem

Maybe your problem is related to the fact that the space in ATD 90917055
causes 90917055 to be an chat expect string and so hangs chat.

--

/* I gave up on politics when no matter who I voted for, I regretted it.
 *    -- Pepper...and Salt, WSJ */

Why write a script file?  KDE makes an auto-dialer and PPP starter for
Internet connections.

You could always use linuxconf to connect also.

Because they make assumptions about how the connection should be maade and are difficult to
debug if they do not work