🚀 go-pugleaf

I recently set up PPP on my father's computer, and discovered that the 
initialisation string for his modem is nothing like mine, which caused 
all sorts of errors.
Anyway, I determined the correct string by reading through either 
Autorun.inf or some obviously named file on the windows driver CD, can;t 
remember what the keyword was, and he took the disk away. Anyway, might 
be worth a look.

Bob Wightman wrote:

> Key words for search engines:
> ppp, pppd, LCP Echo failure, modem init string
> 
> Thanks for the info guys. I now have an up and running ppp connection to 
> my ISP.
> 
> The problem was the init string for my modem. AT&F works fine but I 
> shall have to check for the most suitable string for my particular modem 
> to get the best performance. I also changed the asyncmap line in 
> /etc/ppp/options line to 0 (zero).
> 
> The command that I succeeded with was:
> 
> /usr/sbin/pppd /dev/ttyS1 115200 connect "/usr/sbin/chat -v '' AT OK 
> ATDT1234567890 CONNECT '\d\c'"
> 
> Which came from Bill Unruh's web page on PPP. Part of my problem was 
> that I was following those instructions when I came across a  script 
> written specifically for my ISP and somehow the two got crossed. Mea 
> culpa. Somewhat confusingly the chat.script that the ISP specific script 
> used did use AT&F whereas the chat.script file for the above command did 
> not. The asyncmap 200a00 line came from the ISP specific script.
> 
> Somewhat bizarrely I have set kppp up with the same parameters as far as 
> I can tell and ppp doesn't like it, but that is another problem to 
> solve. Most probably there is a config file somewhere that kppp is using 
> without me knowing about or without kppp telling me it is using.
> 
> Thanks again.