On Tue, Nov 14, Robert G Palmer Jr wrote:
I modified the init string and that still didn't work. I played around some more and I'm pretty sure that the problem is that the wrong end-of-line character is being sent. The modem expects a <CR> (0x0D or ctrl-M - all the same thing, just different names) as the end-of-line. I tested this by doing the following:
You mean the modem wants always a "0x0d" as CR value and the "0x0a" or "0x0d 0x0a" doesnt work? Thats a real bug in the modem.
So now - how do I tell wvdial to use the correct character when sending an end-of-line, or is there something else wrong?
We need a hacked wvdial for that modem bug. The guy who maintain the wvdial package is back from vacation tomorrow. I will ask him to add a workaround. You could try a hexeditor like khexedit to add "0x0d" to the wvdial.conf. But it is possible that wvdial filter that byte. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...