All of lore.kernel.org
 help / color / mirror / Atom feed
From: jarmo <oh1mrr@nic.fi>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Protocol error
Date: Mon, 18 Nov 2002 13:58:08 +0200	[thread overview]
Message-ID: <200211181358.08540.oh1mrr@nic.fi> (raw)
In-Reply-To: <3DD8D4BF.27441.288F6F3@localhost>

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



      parent reply	other threads:[~2002-11-18 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 16:29 Protocol error Demetre Valaris
2002-11-18  0:40 ` Jorge Matias
2002-11-18  9:53   ` Demetre Valaris
2002-11-18 10:52     ` Sandor Dibuz
2002-11-18 11:31       ` Jorge Matias
2002-11-18 11:27     ` Jorge Matias
2002-11-18 11:58     ` jarmo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200211181358.08540.oh1mrr@nic.fi \
    --to=oh1mrr@nic.fi \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.