Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site anasazi.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!hao!noao!terak!anasazi!chad
From: chad@anasazi.UUCP (Chad R. Larson)
Newsgroups: net.arch
Subject: Re: All the Chips that (Don't) Fit
Message-ID: <660@anasazi.UUCP>
Date: Wed, 19-Mar-86 21:15:18 EST
Article-I.D.: anasazi.660
Posted: Wed Mar 19 21:15:18 1986
Date-Received: Tue, 25-Mar-86 04:03:08 EST
References: <5100022@ccvaxa> <615@hoptoad.uucp>
Reply-To: chad@anasazi.UUCP (Chad R. Larson)
Organization: Anasazi, Phoenix Az.
Lines: 29
Keywords: EBCDIC
Summary: Some people do!

In article <615@hoptoad.uucp> Jim Gilmore writes:
>The problem was that the chip is configurable to: 1 start bit, 8 data
>bits, 1 parity bit (whose value is ignored) and 1 stop bit.  Nobody, I
>mean nobody, sends data that way; they send 1 start, 8 data, 1 stop.
>(One of the data bits might be a parity bit, if desired.)

Not true!  I have worked in many commercial systems where we had
to send 8-bit EBCDIC over asynchronus lines.  We always sent parity
on those charaters (one start, 8 data, one parity, one stop = 11 bits).

Same goes for several simple-minded binary upload/download protocols--
again 8 bit data (the bytes) with start, stop & parity.  Parity, in
conjuction with a longitudinal check character is pretty reliable,
and doen't take as much computing as a CRC-16 (for instance).

You need to be careful when you say nobody :-)

	-crl

-- 
"It's not the years, it's the mileage!"
	-Indiana Jones
_____________________________________________________________________
UUCP:    {mot!terak}!anasazi!chad               Voice: Hey, Chad!
Ma Bell: (602) 870-3330                         ICBM:  N33deg,33min
Surface: International Anasazi, Inc.                   W112deg,03min
         7500 North Dreamy Draw Drive
         Suit 120
         Phoenix, AZ 85020