Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!CCV.BBN.COM!haverty From: haverty@CCV.BBN.COM Newsgroups: comp.protocols.tcp-ip Subject: Re: TAC "noise" Message-ID: <8708061239.AA12746@ucbvax.Berkeley.EDU> Date: Thu, 6-Aug-87 08:40:57 EDT Article-I.D.: ucbvax.8708061239.AA12746 Posted: Thu Aug 6 08:40:57 1987 Date-Received: Sat, 8-Aug-87 10:09:56 EDT References: Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 9 Frank -- from my experience, it would be worth looking at "stop bits" in addition to clock tolerances. If a receiver expects more stop bits than a sender sends, things tend to work when there is a non-continuous stream of characters, but get garbled when the line is running flat out - the first bit or two of the "next character" get eaten up as if they were stop bits for the current character. You can test this hypothesis by comparing the characters as received with those as sent, and seeing if bit-shifting would cause a match. Jack