Delaying wvdial? (dialup problem)
Posted: Tue 29 Sep 2009, 03:33
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.
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.