From mboxrd@z Thu Jan 1 00:00:00 1970 From: jarmo Subject: Re: Protocol error Date: Mon, 18 Nov 2002 13:58:08 +0200 Sender: linux-hams-owner@vger.kernel.org Message-ID: <200211181358.08540.oh1mrr@nic.fi> References: <3DD7E005.25470.636F19D@localhost> <3DD8D4BF.27441.288F6F3@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7BIT Return-path: In-Reply-To: <3DD8D4BF.27441.288F6F3@localhost> List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-hams On Monday 18 November 2002 11:53, Demetre Valaris wrote: > > Thanks for reply. I wonder if this causes any problems. At this end when I > had a P133 AMD with 32MB RAm, sometimes my radio would key the TNC and TX > nothing. Now I am not sure whether this is a TNC or computer problem. > Eversince I upgraded my hardware to a faster PC (P433 Celeron with 128MB > RAM) I have not observed this problem although the "protocol 0000 is buggy, > dev ax0) is still there. I am not sure what caused the problem though, > although it seems that the old slower PC with the 32MB RAM was at fault, > but this problem was not persistent!! Hi We have here in OH1RCF 4 tnc's and only one is giving protocol is buggy info...Same as bad checsum messages... I myself have only one tnc and i get every now and then bad checksum but no protocol buggy. We are using 6pack in tnc's...And now we have started thinking that errormsg's migth come because of bad groundings..ie. Tnc's cases are grounded too lightly and RF could cause some weird things... PC is something 333MHz and 64M ram in oh1rcf...I have amd xp-1700+ with 512M ram... 73 de Jarmo,OH1MRR