| |
PA2AGA > HDDIG 09.02.00 17:41l 243 Lines 7759 Bytes #-9586 (0) @ EU
BID : HD_2000_37E
Read: GUEST
Subj: HamDigitalDigest 2000/37E
Path: DB0AAB<DB0KFB<DB0CZ<DB0LX<DB0RBS<DB0SWR<DB0FP<DB0SRS<DB0AIS<DB0ME<
ON6AR<PI8HWB<PI8HGL<PE1MVX<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 000209/0742Z @:PI8VNW.#ZH2.NLD.EU #:50068 [HvHolland] FBB7.00g24
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA29981 ; Wed, 09 Feb 00 05:28:32 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.70/7.5.3) with SMTP
id AA00017850 ; Tue, 08 Feb 2000 18:17:20 MET
Date: Tue, 08 Feb 00 18:11:14 MET
Message-Id: <hd_2000_37E>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 2000/37E
X-BBS-Msg-Type: B
>terminal program is written, and whether it is configured to properly
>deal with the connected device, and whether ALL the control lines
>are connected, or some subset. HP published an exceptionally good
>book on these topics.
>The above only starts to scratch the surface.
You are not getting it. As usual. Are you really that stupid, or
do you only play the dumb guy?
Rob
--
+----------------------------------+--------------------------------------+
| Rob Janssen pe1chl@amsat.org | WWW: http://www.knoware.nl/users/rob |
| AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+----------------------------------+--------------------------------------+
>.
------------------------------
Date: Tue, 01 Feb 2000 23:13:09 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: Kantroncs bugs?
"Rob Janssen" <nomail@rob.knoware.nl> wrote in message
news:slrn89e6qg.9gb.nomail@linux.pe1chl.ampr.org...
> Chris Vine <chris@cvine--nospam--.freeserve.co.uk> wrote:
> >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?
>
> Yes. And most other "RS232 serial devices with RTS/CTS handshake" as
well.
> Apparently the Kantronics TNCs don't.
>
> A possible catch is that the number of bytes one has to have available
> in the buffer when CTS is lowered has increased over time. But so has
> the average size of memories, and hence of buffer spaces. So this should
> not really be a problem, except when development has stood still over the
> last 15 years. This may be the problem with TNC firmware.
However it is easy, as I've mentioned, to deal with this in the terminal
program, and most are able to handle the situation without any trouble.
As far as TNCs are concerned, at least the following have had this
problem, or other problems involving flow control:
GLB had "unsurmountable flow control problems".
TAPR TNC1 prior to firmware version 3.2.
(Both hardware and software flow control failed).
TAPR TNC2 prior to firmware version 1.3, and a few later releases.
(Various flaws or inconsistencies in both hardware and software flow
control.)
AEA PK-232, many firmware revisions.
Kantronics KAM, some early firmware.
Ditto the various KPC versions of the hardware.
Tereleader uTNC-21, only the beta firmware.
Heathkit - see equivalent hardware above. The 4040 tended to be
one rev behind the TAPR releases. The HK-21 used only the post-
beta uTNC-21 firmware.
Etc. etc.
Since this is ".digital.misc" and not ".tnc.misc" I should point out that
other modems in common use by hams also have these same problems,
or others that can produce similar symptoms in poorly written terminal
programs. Several of the HAL controllers were (and still may be) difficult
to program correctly wrt flow control. The PCI4000 and P38 are easy
to deal with, although they have exceptionally complex interfaces.
But this is a "terminal program" issue, nothing to do with the TNCs or
other controllers. They "do what they do", and the terminal program
must take account of whatever that might be. Ain't no harder than
BISYNC, UDLC, 2780/3790, etc. ad nauseum.
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: Wed, 02 Feb 2000 19:27:16 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: Kantroncs bugs?
"Rob Janssen" <nomail@rob.knoware.nl> wrote in message
news:slrn89g6fa.hmv.nomail@linux.pe1chl.ampr.org...
> Hank Oredson <horedson@att.net> wrote:
>
> >Consider RTS/CTS vs. DSR/DTR vs. ^S/^Q.
>
> >Many different behaviors are possible, depending on how well the
> >terminal program is written, and whether it is configured to properly
> >deal with the connected device, and whether ALL the control lines
> >are connected, or some subset. HP published an exceptionally good
> >book on these topics.
>
> >The above only starts to scratch the surface.
>
> You are not getting it. As usual. Are you really that stupid, or
> do you only play the dumb guy?
Like I keep saying: learn how to choose and use a terminal program.
Then you have no problems.
Think about the TNC1 (you *are* familiar with how it does flow
control, right?) RTS/CTS will not work with that device. So everyone
learned to set their terminal program correctly, or built strange serial
cables to allow the cross-over of the control signals. People do this
all the time, it's called "cleverness" or "ingenuity".
Same for the older KPC firmware, and *any* other connected
devices. They "do what they do". You deal with it.
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: 2 Feb 2000 01:53:34 GMT
From: jeffreyh@Hawaii.Edu (Jeffrey Herman)
Subject: List of the rec.radio newsgroups
Archive-name: radio/personal-brief-introduction
In an effort help ensure a poster's article reaches the appropriate
audience, below is a list of the rec.radio newsgroups. In most cases,
a group's name will explain its purpose. Cross-posting should rarely
be necessary.
rec.radio.broadcasting (devoted to the broadcast industry; moderated)
rec.radio.cb
rec.radio.info (periodic informational bulletins; moderated)
rec.radio.scanner
rec.radio.shortwave
rec.radio.swap (for buying, selling, and trading; not a discussion group)
rec.radio.amateur.antenna
rec.radio.amateur.boatanchors (tube-type communications equipment)
rec.radio.amateur.digital.misc (packet, pactor and other digital modes)
rec.radio.amateur.dx (long-distance amateur communications)
rec.radio.amateur.equipment (questions, comments regarding commercially-
built amateur gear; not for buying/selling)
rec.radio.amateur.homebrew (devoted to home-building ham gear)
rec.radio.amateur.policy (issues include code, restructuring, local
restrictions in conflict with FCC R&R)
rec.radio.amateur.space (satellites, meteor scatter, EME)
rec.radio.amateur.misc (any topic not covered in the above groups)
(At least two other English language radio hierarchies exist, prefixed
with "uk" (United Kingdom), and "aus" (Australia), in place of "rec.")
Again, cross-posting should rarely be necessary. Many times, a long-
running thread results from a single cross-posted article, and its
content drifts further and further away from being "on-topic" in the
various NGs which receive each and every followup.
For more detailed information, see "Guide to the Rec.radio Newsgroups"
posted on the 15th of each month.
Jeffrey Herman, KH6O
>.
------------------------------
Date: Sat, 5 Feb 2000 19:23:02 +0100
From: "Agabus" <agabus@hotmail.com>
Subject: Optoelectronics SCOUT and AOR AR8200
How do I get the SCOUT to "transfer" a frequency to my AR8200?
I do have the correct cable, but do I need to do any settings in my
AR8200 before it will work?
/AgaBus
>.
------------------------------
Date: 04 Feb 2000 13:19:02 GMT
From: ralphmw@aol.com (RalphMW)
Subject: Packet software for Palm III
Check out:
http://www.tapr.org
Look under the APRS software page, there is APRS packet software there for the
Palm operating system.
Ralph NH6QT/3
>.
------------------------------
Date: 06 Feb 2000 02:26:23 GMT
From: pmunsel@aol.com (PMunsel)
Subject: PSK31 on Six?
To be continued in digest: hd_2000_37F
Read previous mail | Read next mail
| |
