Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 (Fortune 01.1b1); site graffiti.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!ut-sally!ut-ngp!shell!graffiti!peter
From: peter@graffiti.UUCP (Peter da Silva)
Newsgroups: net.unix-wizards
Subject: Re: lost characters in serial I/O
Message-ID: <319@graffiti.UUCP>
Date: Wed, 16-Oct-85 22:30:28 EDT
Article-I.D.: graffiti.319
Posted: Wed Oct 16 22:30:28 1985
Date-Received: Mon, 21-Oct-85 00:42:06 EDT
References: <1553@uwmacc.UUCP>
Distribution: net
Organization: The Power Elite, Houston, TX
Lines: 16

> We have an 11/70 running 2.8BSD, and are trying to send in data from
> a remote site that supports only a crude protocol.  The remote person
> logs into the 11/70, and types "cat > filename"...

I'd guess that you're using DEC serial cards, which are notoriously
flakey. A lot of them (no names come to mind) can only support better
than 300 baud for short bursts... that is, they can accept people's
typing but file transfer just fills their little silos and they crater.

If the device driver is trying to cover for this by throwing CPU cycles
at it, then strange things will start happening as the load goes up. First
file transfers will die, then you'll start losing characters from normal
typing... which seems to be what's happening.

I don't know of any solution except to go for a more accurately rated serial
card.