| |
PA2AGA > HDDIG 04.02.00 21:13l 147 Lines 5420 Bytes #-9591 (0) @ EU
BID : HD_2000_32A
Read: DL6KCF GUEST
Subj: HamDigitalDigest 2000/32A
Path: DB0AAB<DB0PV<OE2XOM<OE5XBL<OE3XSR<OK0PPL<OK0POK<OK0PAB<HA5OB<HA3PG<
SV1AAW<EA7URC<PE0MAR<PI8VNW
Sent: 000201/2250Z @:PI8VNW.#ZH2.NLD.EU #:48651 [HvHolland] FBB7.00g24
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA29586 ; Tue, 01 Feb 00 19:12:33 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.70/7.5.3) with SMTP
id AA00017752 ; Tue, 01 Feb 2000 18:26:25 MET
Date: Tue, 01 Feb 00 18:24:04 MET
Message-Id: <hd_2000_32A>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 2000/32A
X-BBS-Msg-Type: B
Ham-Digital Digest Tue, 1 Feb 2000 Volume 2000 : Issue 32
Today's Topics:
ARE YOU A YOUNG TEEN MODEL WHO WANTS TO MAKE IT BIG? 17526
Kantroncs bugs? (3 msgs)
YAM 9k6 FSK modem
Send Replies or notes for publication to: <Ham-Digital@UCSD.Edu>
Send subscription requests to: <Ham-Digital-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Ham-Digital Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives/ham-digital".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
Loop-Detect: Ham-Digital:2000/32
----------------------------------------------------------------------
Date: 31 Jan 2000 21:32:24 GMT
From: g345cde@aol.com (G345CDE)
Subject: ARE YOU A YOUNG TEEN MODEL WHO WANTS TO MAKE IT BIG? 17526
You will be running your own server from behind bars!!! Please write again
from there.
G345CDE
>.
------------------------------
Date: Mon, 31 Jan 2000 22:24:50 GMT
From: chris@cvine--nospam--.freeserve.co.uk (Chris Vine)
Subject: Kantroncs bugs?
On Mon, 31 Jan 2000 09:56:18 GMT, nomail@rob.knoware.nl (Rob Janssen)
wrote:
[snip]
>
>It does not work like that... the UART does not automatically stop output
>when CTS is low. Some UARTs in computer history could do that, but the
>function was usually riddled with problems. The UART used in the PC will
>only present the status of the CTS input as a bit in a register, and will
>optionally issue an interrupt when the status changes. The other UARTS
>have this mode as well (and are usually operated in this mode).
>
>The software needs to catch those interrupts, and twiddle its state to
>not send more output to the UART when CTS state says it shouldn't.
>But the bytes that were already put in the UART will still be sent out
>to the line. The driver cannot reliably "cancel" bytes already written
>to the UART.
>
>Traditionally, this could be up to two bytes: one in the transmitter
>shift register (the one currently being shifted out), the other in the
>transmitter holding register (the next one to be clocked into the shift
>register).
>However, with the advent of FIFO buffers, there can be more bytes waiting
>in the UART. The popular 16550A has a 16-byte FIFO, although it can be
>configured to contain fewer bytes.
Thank you. A most interesting analysis. Presumably, it would be wise
for a TNC (or any other serial device) to take CTS low well in advance
of running short of buffer space. Is that what most modems do?
Chris.
--
If replying by e-mail, remove the --nospam--
>.
------------------------------
Date: Mon, 31 Jan 2000 21:53:22 -0500
From: "Rob" <Pse@NoEmail.Com>
Subject: Kantroncs bugs?
Hank,
The CTS hardware handshaking does NOT work in the KANTRONICS KAM, KPC-3 and
possibly other KANTRONICS TNC's even with expensive computer cables
connecting all the right pins!
I agree that it shouldn't be hard for KANTRONICS to fix this type of bug. A
lot of the code is probably very easy to find. Unfortunately, there isn't
much political will.
Many Hams use a HOSTMODE program which constantly checks the amount of free
space left in the TNC buffer. This approach has two advantages -- one can
always send a command to the TNC since there is always some buffer space
left in the TNC. Secondly, one can make sure the buffer will never get full
and lose characters due to KANTRONICS' poorly written handshaking protocol
firmware in their TNCs. Consequently, many HAMS don't ever see the bug.
But some of use like using the terminal mode!
73's
Rob
"Hank Oredson" <horedson@att.net> wrote in message
news:%Opl4.243$6B1.41661@bgtnsc06-news.ops.worldnet.att.net...
>
> "Chris Vine" <chris@cvine--nospam--.freeserve.co.uk> wrote in message
> news:38960b4c.1275448@news.freeserve.net...
> > On Mon, 31 Jan 2000 09:56:18 GMT, nomail@rob.knoware.nl (Rob Janssen)
> > wrote:
> >
> > [snip]
> > >
> > >It does not work like that... the UART does not automatically stop
> output
> > >when CTS is low. Some UARTs in computer history could do that, but the
> > >function was usually riddled with problems. The UART used in the PC
will
> > >only present the status of the CTS input as a bit in a register, and
will
> > >optionally issue an interrupt when the status changes. The other UARTS
> > >have this mode as well (and are usually operated in this mode).
> > >
> > >The software needs to catch those interrupts, and twiddle its state to
> > >not send more output to the UART when CTS state says it shouldn't.
> > >But the bytes that were already put in the UART will still be sent out
> > >to the line. The driver cannot reliably "cancel" bytes already written
> > >to the UART.
> > >
> > >Traditionally, this could be up to two bytes: one in the transmitter
To be continued in digest: hd_2000_32B
Read previous mail | Read next mail
| |
