> On Sat, 19 May 2001, Robert Davies wrote:
>
> >Anyway eventually I switched it to pulse dialing (simply by altering ATDT
to
> >ATDP in Minicom), the call goes through and a modem answers and the
> >connection is made. Having gone back and configured wvdial to use pulse
> >dialing, Kinternet connects to. So When I reboot, both Debian (using
chat
> >rather than wvdial) and Windows connect as usual using Tone dialing
without
> >problems. I thought that the dialing of modem, could not be altered by
the
> >OS as it's just sending an ATD string.
>
> Is either windows or linux sending an initialization string to the
> modem before it dials?
> It's possible the modem defaults to .us tones & windows is switching
> it to .uk, or it defaults to .uk and linux is switching to .us (or
> maybe .de if it's suse 8-)
They do have UK pre-setup ISP, like Freeserve, so they're not totally
euro-centric.
> If you've got the problem with a freshly powered up modem & manually
> dialling the first is more likely than the second.
That's what's very odd, because after power off, it only gets :
ATZ /* Re-initialise */
AT&W=2 /* Report bit rate rather than the baud rate eg) 49333 or
50667 */
and SuSE is sending the same before the dialing according to the logs with
wvdial, and the init strings I set, and I powered off using Minicom, and got
a consistent result. Previously I connected to a different ISP with same
modem using wvdial, and SuSE 6.1 so I wasn't expecting any trouble.
Perhaps it's a late night funny, in which case the problem will have gone
away, but I don't think so, and enough new installers have reported problems
connecting to NTL in news groups, when others had no trouble.
Scratching head
Rob
--------------------------------------------------------------------
http://www.lug.org.uk http://www.linuxportal.co.uk
http://www.linuxjob.co.uk http://www.linuxshop.co.uk
--------------------------------------------------------------------
This archive was generated by hypermail 2.1.3 : Thu 22 Nov 2001 - 13:12:57 GMT