Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 26 Oct 2005 21:18:48 -0500
Newsgroups: fidonet.linux
From: WAYNE_CHIRNSIDE@f140.n123.z1
Date: Sun, 23 Oct 2005 18:55:28 -0400
Subject: software for linspire
Message-ID: 
Organization: Try Our Web Based QWK: DOCSPLACE.ORG
 456
 205/1
 267/200
Lines: 43
NNTP-Posting-Host: 24.48.121.215
 properly
Xref: number1.nntp.dca.giganews.com fidonet.linux:121

-> WC> Just gave it the ISP PH. number, COM port /dev/ttyS0, user
-> WC> name and password. 

-> WC> My connection speed dramatically increased. 

-> Getting a decent connection speed is a factor of what _your_
-> software/modem is doing AND what the software/modem is doing at
-> the server. The design has always been to "fall back" after
-> attempting the optimum connection. If anything interrupts or
-> interferes during this "handshaking" process the fallback can
-> be too fast not unlike when humans make too many assumptions
-> and then make mistakes. 

Knoppix allowes one to adjust the negotiation timing
as will some commas in the init string, used this to allow my 14,400
to connect after the ISP went 56K protocols and the 
gong sounding negotiation confused the modem.
Couple of commas fixed it right up.

-> As I've already said the MSCHAP is supposed to fallback but at
-> what point and how much time must pass? Some earlier software
-> for DOS will give up the connection attempt waiting for MSCHAP
-> to fallback to regular CHAP (it 'times out').
 
On CHAP here I can set the timeout interval as well.

-> Some years ago experienced computer users were more aware of
-> these timing errors and a portion of the discussions would be
-> how to overcome these errors. Now I see people collecting
-> 'distros' in an attempt to avoid minor glitches that do not
-> necessarily condemn the entire install. 

Not me, I hit a snag I hammer away at it until, usually,
I overcome it quickly.
Not ashamed to admit I employ google to keep from reinventing the
wheel.

-> Everyone can't be a programmer, I realize this, but it is
-> unfortunate for a collection of software to be faulted based on
-> one very tiny application that has timing mismatches with the
-> software installed on an ISP's server. 

I just adjust at this end :-)