Puppy Linux Discussion Forum

sky king · Joined: 08 Apr 2009 Posts: 72

So here I am, happy as anyone with Puppy 4.2. Then the dialup provider does something to screw up my connection.

XP will connect fine, and I'm posting now from Puppy 2.16. GKDial works most of the time for me. But with 4.1 and 4.2, pupdial will not successfully connect. It seems like from the text box that WVDial gives up too soon between when the server asks for the password and their reply. Sometimes it gives up at different times in the dialup sequence. I have even had blinky working a couple of times, thought I was on, but still not connected.

I'm wondering if there's a way, using commas or something, to add time between lines in the config file. (I would need exact help here - where to put commas, etc. Even a good way to use terminal to find out exactly what's going on would help. (I'm not all that familiar with the process). To understand it better, I'm willing to type in commands, wait for the reply, type in commands to see how long it takes, and so on.

Or getting another dialer (maybe GKDial, as that seems to work most of the time with Puppy 2.16) that will hook me up like before.

I haven't called the tech support line, as they will probably say they don't support Linux.

So here I am begging for help, the most painless way possible, please. Another dialer to try in 4.2 maybe?

Thank you.

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

sky king,
Sorry to be so long in responding, but I just now spotted your posting. I do not have an answer for you for puppy 4.2, as all my recent work is part of puppy 4.3/4.3.1. But the pupdial part of that work is in my 3G-wireless project. But before anything else, you might try adding either or both of the following commands to the second initialization string in pupdial:
S10=20
S25=50
These values are only my guess for increasing some timeouts. Here are the explanations from the modem-command list: