| |
PA2AGA > PACDIG 25.02.99 13:35l 177 Lines 7086 Bytes #-9944 (0) @ EU
BID : PR_99_41
Read: GUEST
Subj: PacketRadioDigest 99/41
Path: DB0AAB<DB0PV<DB0MAK<DB0BOX<DB0ABH<DB0SRS<DB0AIS<DB0NDK<DB0ACH<DB0ACC<
PI8DRS<PI8DAZ<PI8GCB<PI8WFL<PI8VNW
Sent: 990225/0624Z @:PI8VNW.#ZH2.NLD.EU #:29673 [HvHolland] FBB7.00g $:PR_99_41
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : PACDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA14684 ; Thu, 25 Feb 99 06:09:40 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00012563 ; Thu, 25 Feb 99 06:47:13 MET
Date: Thu, 25 Feb 99 06:37:09 MET
Message-Id: <pr_99_41>
From: pa2aga
To: pr_broadcast@pa2aga
Subject: PacketRadioDigest 99/41
X-BBS-Msg-Type: B
Packet-Radio Digest Wed, 24 Feb 99 Volume 99 : Issue 41
Today's Topics:
Thief
Why a TNC? (2 msgs)
Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu>
Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives/packet-radio".
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: Packet-Radio:99/41
----------------------------------------------------------------------
Date: Tue, 23 Feb 1999 21:18:59 -0600
From: "Kurt A. Freiberger" <kurt@cs.tamu.edu>
Subject: Thief
Git a rope......
Man, that's really rude!
kf
gfbike wrote:
>
> I wanted to get the word out to all the sites about a thief by the name
> of Glen Verasso of
> Newark, Ohio. He entered into a trade agreement with me when he saw my
> listing of
> my Henry 2KD5 in one of the various ham sites, among which this was one.
> He offered to trade me an FT1000 (presumably an early one) for my Henry.
> This seemed like an odd, but certaily reasonable trade so I went for it.
> I carefully packed up the Henry in 3 boxes and sent it to him UPS, the
> same time he sent a package to me, again UPS. What I received today was
> a nicely wrapped box with three concrete blocks inside, total value
> about $1.50.
--
Kurt A. Freiberger, WB5BBW Network Environmentalist Austin, TX
Published 12/12/98, Saint Paul Pioneer Press Bulletin Board:
Redmond, WA (AP) -- Microsoft announced today that the official release
date for the new operating system "Windows 2000" will be delayed until
the second quarter of 1901.
>.
------------------------------
Date: Sat, 20 Feb 1999 15:54:25 -0500
From: Bill Smith <whsmith@radix.net>
Subject: Why a TNC?
SV - I too am new to ham radio. In fact I just took the exams this
morning and became a 'Technician' today. I have a lot of experience in
LAN/WAN networks and now want to get a handle on RF networks, so I've
been looking at the literature on packet radio real close. OK, now to
get to the question you asked, I'll give you a squirt from my limited
experience. I haven't seen a TNC yet, so be kind.
First, it will depend on the TNC and software selected, as to how many
'functions' it and the accompanying workstation software accommodate.
The one function that you must have in the TNC is the 'modem'. This
function will convert 'analog' radio and 'digital' computer signals
between your radio and the computer. RTTY uses only this function and
terminal emulation software in your computer. A TNC is itself a
programmable device and you will be sending it commands to activate
available modes and make settings. The flexibility of both the device
and the the software that runs on your workstation varies in
capabilities and costs. I am far from an expert, remember. Auto-sensing
data rates and KISS are examples of hardware features. Various terminal
modes capability such as RTTY, AX25, AMTOR, TCPIP, etc. are workstation
programs. Exactly what the hardware does and what the software does
probably varies to some extent depending on the hardware manufacturer's
implementations, but generically speaking, TNC2 hardware is a standard.
TNC2 operations are discussed in an article on Packet Radio in the ARRL
Operations Manual and if you can get out on the Web you'll find a site
on Packet Radio with lots of info -try
http:\\www.tapr.org/tapr/html/pktf.html
Bill Smith
whsmith@radix.net
SV Windigo wrote:
>
> I'm an experieced computer type and a long time Ham. However, I am new to
> digetal radio. My question is do I really need a TNC? It appears to me
that
> all the TNC does as make the computer act as a dumb terminal. It would
seem
> that the whole thing can be done with software and a xcvr. I'm probably
wrong
> but had to ask.
>
> 73
> Chuck
>.
------------------------------
Date: Sat, 20 Feb 1999 16:23:32 -0500
From: Bill Smith <whsmith@radix.net>
Subject: Why a TNC?
SV - I too am new to ham radio. In fact I just took the exams this
morning and became a 'Technician' today. I have a lot of experience in
LAN/WAN networks and now want to get a handle on RF networks, so I've
been looking at the literature on packet radio real close. OK, now to
get to the question you asked, I'll give you a squirt from my limited
experience. I haven't seen a TNC yet, so be kind.
First, it will depend on the TNC and software selected, as to how many
'functions' it and the accompanying workstation software accommodate.
The one function that you MUST have in the TNC itself is the 'modem'.
This function will convert 'analog' radio and 'digital' computer signals
between your radio and the computer. RTTY uses only this function and
terminal emulation software in your computer. A TNC is itself a
programmable device and you will be sending it commands to activate
available modes and make necessary settings. The flexibility of both the
device and the the software that runs on your workstation varies in
capabilities and costs. I am far from an expert, remember. Auto-sensing
data rates, efficiently handling the data stream, and KISS are examples
of hardware features (I think). Various terminal modes capability such
as RTTY, AX25, AMTOR, TCPIP, etc. are workstation programs. Generically
speaking, TNC2 hardware is a standard.(I forget where I saw it but at
least one manufacturer was working on a 'software" implementation that
would take care of everything except the modem, so your idea isn't far
off.) TNC2 operations are discussed in an article on Packet Radio in
the ARRL Operations Manual and if you can get out on the Web you'll find
a site on Packet Radio with lots of info -try
http:\\www.tapr.org/tapr/html/pktf.html
Bill Smith
whsmith@radix.net
_*_*_*_*_*_*_*_*_*_*_*_*_*_*
SV Windigo wrote:
>
> I'm an experieced computer type and a long time Ham. However, I am new to
> digetal radio. My question is do I really need a TNC? It appears to me
that
> all the TNC does as make the computer act as a dumb terminal. It would
seem
> that the whole thing can be done with software and a xcvr. I'm probably
wrong
> but had to ask.
>
> 73
> Chuck
>.
------------------------------
End of Packet-Radio Digest V99 #41
******************************
You can send in your contribution to this digest by
sending an e-mail to: packet-radio@pa2aga.ampr.org
or (via BBS-net) to: praga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
