Jeff, at 16:17 on Sat, Apr 29 1995, you wrote to Bill Grimsley ...

JG> Thats' the only command in the modem maual that mentions error correction.

BG> It's a fucked Series 3 Netcomm then.

JG> Yes :-(

Why not piss it off then?  Surely you can find some poor unsuspecting
bastard who'd be silly enough to buy it?  Some of the kiddies around these
days have likely never heard of the S3 anyway, so why not rip THEM off?

BG> Does your manual have anything to say about the \Nn command
BG> (defaults to \N3 from memory)?

JG> Yep, it's set to \N3. It doesn't mention anything about being used with 
JG> error correction. It only mentions setting the modem to constant or 
JG> auto-reliable speed. \N3 is auto-reliable.

That just means it'll try for MNP first, but fall back to a normal connect
if the other end doesn't support MNP.  No LAPM in these old beasties.  |-)

BG> Also, if yours is set to &K9, you should alter it to &K3
(but check the 
BG> docs first, as it's a long time since I last used a S3 Netcomm).

JG> Yep, it's set to &K3. The book doesn't mention error correction connects. 

That is forced CTS/RTS flow control, I think, whereas &K9 enables
XON/XOFF as well, which has been known to cause problems with the S3s.

JG> It does mention data loss due to buffer overflow, but that's not a 
JG> transmit/recieve error due to the type of connect. That's hardware AFAIC.

True, but if you're not toggling CTS/RTS in your modem, you will get data
overflows, hence the &K3.  Nothing to do with negotiating the actual
REL connect though.

Regards, Bill
@EOT:

--- Msgedsq/2 3.05