On Monday, 06 October, 2003 05:04, Basil Chupin wrote:
Bernd Koepsell wrote: <snip>
The way that I have executed my ATI commands, was to modify wvdial.conf, save it, then execute wvdial in the shell and view the output.
See the message from Joe Morris. Install minicom. I just installed it and it is exactly what I have been looking for for a while.
Thanks to Joe for minicom!!!
Run minicom and, in your case, type ATI4 and then ATI5 to see what settings are being used by the modem. The manual explains I4 and I5 commands.
Did that through wvdial just after my reinstall. ATI4 showed Y4 (factory configuration 2) being used. Because it was using that, for some wierd reason, dns wasn't working. Please don't ask me why! I have no idea what is contained in factory config 2. But when I switched to AT&F1(&F1=Y0=Hardware control template), the dns problem ended. I keep scratching my head, but it works now. That IS what matters.
The only thing I will add here is that if you can get the model number and/or the number Robotics has assigned to your modem then you could try and find what the init string is issued to it by Windows.
I pulled the log from windoze shortly after I started this thing in August, and used the same init string in linux, without success. This is why this thread is named the way it is. After reinstall, everything mysteriously was fixed, except for the dns problem. Which was fixed with AT&F1, even though I had used this same init before reinstall, without success. Who knows??? Oh well! I am now -consistently- connecting for 5 hours before my ISP drops me! YEAH!!! MMT Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery