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:20:28 -0500
Newsgroups: fidonet.linux
From: Ed_Hulett@f789.n123.z1
Reply-To: kc7flr@arrl.net
Date: Sun, 23 Oct 2005 22:34:42 -0400
Subject: software for linspire
Message-ID: 
References: 
Organization: Veritas vos Leberabit!
 456
 205/1
 267/200
Lines: 66
NNTP-Posting-Host: 24.48.121.215
 properly
Xref: number1.nntp.dca.giganews.com fidonet.linux:137

WAYNE CHIRNSIDE -> CHARLES ANGELICH wrote:
 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.

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

Commas are a standard device for introducing a pause in the dialing and modem
negotiation process. Knoppix has nothing to do with it. You can do the same with
any dialer.

 ->> 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').

 WC> 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.

 WC> Not me, I hit a snag I hammer away at it until, usually,
 WC> I overcome it quickly.

Back before broadband connections and graphical interfaces were the norm
everyone had to do just that. I was using linux back when you had to lift the
hood to get things working the way you wanted. Back then, X was more of a luxury.
We used pine or elm for email and slrn or tin for usenet and lynx for WWW as a
necessity. Now only the diehards use text based apps.

 WC> Not ashamed to admit I employ google to keep from reinventing the
 WC> wheel.

Goggle is your friend.

 ->> 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.

 WC> I just adjust at this end :-)

That's the only place to adjust it. Most ISPs use one flavor of *nix or other
so it shouldn't be too difficult to get your connection up and running.

BTW, did you finally get a hard drive for that machine? I saw Sakowski giving
you some info regarding that a while back.

Ed