Hi Rich,
Ok, this has nothing to do with the modem, it is the chat script
I ran accross similar problems , It was just hanging there !! and I had
the same idea how does it know what device it will connect to.
The thing is as minicom works the modem works. So now the chat script !!
the problem is around the CR and the script, I solve this by :
- Open an xterm and do tail -f /var/log /messages so I can see what
diald says.
- Then I trieed to write a script until I get an answer from the modem
and good feedback in the /var/log/messages basically I did this by
incrementally building the script
start with
ABORT BUSY
"" +++ATZ OK
Look at the messages you should get something like
ABORT (BUSY)
....expect (OK) --got it
If you don't, play with the end of your lines in the shell
like
"" +++ATZ OK \
ATDT 002211
Ok the explantion are not very clear, but I hope you see the point.
The script I have working now seems no diferent from the one which was
NOT working, just because the CR character has moved to the right place
( I don't know how to visualize it)
So I had to play till it works, then I backed up the file just in case.
I hope this will help you
best regards
Gh Portefait
Richard King wrote:
>
> I'm finally able to use both kppp and wvdial successfully with my USR
> Sportster Flash modem (v90) but its really bugging me that I am totally
> unable to get CHAT to work...
>
> When I run chat, and believe me I've tried just about every INIT string I
> can think of, I get zero reaction from the modem - no blinking of lights or
> result codes - and chat just times-out....
[deleted....]
--
----------------------------------------------------------------
Life must be understood backwards. But it must be lived forwards
- Søren Kierkegaard -
S/MIME Cryptographic Signature
