Date: Mon, 15 Nov 93 20:43:06 PST
From: Info-Hams Mailing List and Newsgroup <info-hams@ucsd.edu>
Errors-To: Info-Hams-Errors@UCSD.Edu
Reply-To: Info-Hams@UCSD.Edu
Precedence: Bulk
Subject: Info-Hams Digest V93 #1352
To: Info-Hams
Info-Hams Digest Mon, 15 Nov 93 Volume 93 : Issue 1352
Today's Topics:
A/D for DSP
Elmers are dead, god help us HAMS!
FT727 Schematic
Guide to the Personal Radio Newsgroups
ORBS$316.2L.AMSAT
RS FREQ COUNTER HOLD MOD!!!!!!!!!
SAREX Keps & Update 10/28
STUCK KEY -- turn it off?
Telescoping antenna on HT
The firestorm
Send Replies or notes for publication to: <Info-Hams@UCSD.Edu>
Send subscription requests to: <Info-Hams-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Info-Hams Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/info-hams".
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.
----------------------------------------------------------------------
Date: 15 Nov 93 23:18:01 GMT
From: news-mail-gateway@ucsd.edu
Subject: A/D for DSP
To: info-hams@ucsd.edu
Text item: Text_1
In the Nov QST, page 79, some specs are given for the TRFT-550
Backpacker II transceiver. The blocking dynamic range is 100 db
and the two-tone intermod distortion dynamic range is 81 db. Is
this enough information to answer the following question?
If one were trying to do some state-of-the-art Digital Signal
Processing on the audio from this direct-conversion receiver, how
many bits of A/D would one need?
Thanks and 73, Cecil, kg7bk@indirect.com (I do not speak for Intel)
------------------------------
Date: Mon, 15 Nov 1993 04:37:27 GMT
From: mvb.saic.com!unogate!news.service.uci.edu!usc!sol.ctr.columbia.edu!news.kei.com!ub!csn!hellgate.utah.edu!math.utah.edu!cosmic.physics.utah.edu!levin@network.ucsd.edu
Subject: Elmers are dead, god help us HAMS!
To: info-hams@ucsd.edu
Hi,
I have received several responses to my earlier post and feel that
I need to correct and clarify a few points.
First, I apologise for the old farts comments. Just as not all
of us new hams are ignorant, not all older hams are old farts.
I do apologise for this. I had ment to make the point that
new hams seem to be looked down on by the ham community as a
whole.
Second, several people have commented on my tech license plus
transmission on HF bands. I have NOT done this except in
the company of a HAM with the appropriate license. This was
also ment to make a point however in the heat of the moment
I seem to have mis-quoted myself. I have the utmost respect
for the rules of amature radio and would never intentionaly
violate them.
Most of your responses have been very positive, thanks for
all the replies and I look forward to discussing this issue
in more detail. I don't believe in complaining about a problem
without working towards a solution. I hope that all of us
in this news group can work together and make this aspect
of the hobby as informative and fun as possible. The internet
is a powerful medium for the excange of ideas. I would hope
that in this group we can use it this way and not turn it
into a huge international flame war. I Look forward to hearing
from everyone out there in internet land.
Chris Levin (KB7YOU)
levin@cosmic.physics.utah.edu
------------------------------
Date: 16 Nov 93 02:54:24 GMT
From: news-mail-gateway@ucsd.edu
Subject: FT727 Schematic
To: info-hams@ucsd.edu
I am in search of a schematic for a YAESU FT727. Please mail me
directly if you can help. Thank you for your help in advance.
Name: Lesa Skipper
Call: KB5GMW
Land Line: 405-524-9222
Internet: Lesa@Regentdb.osrhe.edu
------------------------------
Date: Mon, 15 Nov 1993 12:00:25 GMT
From: nevada.edu!news.unomaha.edu!news@uunet.uu.net
Subject: Guide to the Personal Radio Newsgroups
To: info-hams@ucsd.edu
Posted-By: auto-faq 2.4
Archive-name: radio/personal-intro
Revision: 1.5 09/18/93 16:49:31
Changes: new mailing lists, .packet rmgroup, and .policy updates
(Note: The following is reprinted with the permission of the author.)
This message describes the rec.radio.amateur.*, rec.radio.cb, rec.radio.info,
and rec.radio.swap newsgroups. It is intended to serve as a guide for the new
reader on what to find where. Questions and comments may be directed to the
author, Jay Maynard, K5ZC, by Internet electronic mail at
jmaynard@oac.hsc.uth.tmc.edu. This message was last changed on 18 September
1993 to add the mailing lists for the new rec.radio.amateur newsgroups, to
note the rmgroup of rec.radio.amateur.packet, and to officially retire some
(in)famous threads of discussion on rec.radio.amateur.policy.
History
=======
Way back when, before there was a Usenet, the Internet hosted a mailing list
for hams, called (appropriately enough) INFO-HAMS. Ham radio discussions
were held on the mailing list, and sent to the mailboxes of those who had
signed up for it. When the Usenet software was created, and net news as we
now know it was developed, a newsgroup was created for hams: net.ham-radio.
The mailing list and the newsgroup were gatewayed together, eventually.
As the net grew, and as packet radio came into vogue, packet discussion began
to dominate other topics in the group and on the list. This resulted in the
logical solution: a group was created to hold the packet discussion, and
another corresponding mailing list was created as well: net.ham-radio.packet
and PACKET-RADIO, respectively.
These two groups served for several years, and went through Usenet's Great
Renaming essentially unchanged, moving from net.ham-radio[.packet] to
rec.ham-radio[.packet]. Readership and volume grew with the rest of the
network.
The INFO-HAMS mailing list was originally run from a US Army computer at
White Sands Missile Range, SIMTEL20. There were few problems with this
arrangement, but one was that the system was not supposed to be used for
commercial purposes. Since one of hams' favorite pastimes is swapping
gear, it was natural for hams to post messages about equipment for sale
to INFO-HAMS/rec.ham-radio. This ran afoul of SIMTEL20's no-commercial-use
restriction, and after some argument, a group was created specifically
for messages like that: rec.ham-radio.swap. This group wasn't gatewayed to
a mailing list, thus avoiding problems.
While all this was happening, other folks wanted to discuss other aspects
of the world of radio than the personal communications services. Those
folks created the rec.radio.shortwave and rec.radio.noncomm newsgroups,
and established the precedent of the rec.radio.* hierarchy, which in turn
reflected Usenet's overall trend toward a hierarchical name structure.
The debate between proponents of a no-code ham radio license and its opponents
grew fierce and voluminous in late 1989 and 1990. Eventually, both sides grew
weary of the debate, and those who had not been involved even more so. A
proposal for a newsgroup dedicated to licensing issues failed. A later
proposal was made for a group that would cover the many recurring legal issues
discussions. During discussion of the latter proposal, it became clear that it
would be desirable to fit the ham radio groups under the rec.radio.*
hierarchy. A full-blown reorganization was passed by Usenet voters in January
1991, leading to the overall structure we now use.
After the reorganization, more and more regular information postings began to
appear, and were spread out across the various groups in rec.radio.*. Taking
the successful example of the news.answers group, where informational postings
from across the net are sent, the group rec.radio.info was created in
December, 1992, with Mark Salyzyn, VE6MGS, initially serving as moderator.
In January, 1993, many users started complaining about the volume in
rec.radio.amateur.misc. This led to a discussion about a second
reorganization, which sparked the creation of a mailing list by Ian Kluft,
KD6EUI. This list, which was eventually joined by many of the most prolific
posters to the ham radio groups, came up with a proposal to add 11 groups to
the rec.radio.amateur hierarchy in April 1993. The subsequent vote, held in
May and early June, approved the creation of five groups:
rec.radio.amateur.digital.misc (to replace .packet), .equipment, .homebrew,
.antenna, and .space.
The Current Groups
==================
I can hear you asking, "OK, so this is all neat history, but what does it
have to do with me now?" The answer is that the history of each group has
a direct bearing on what the group is used for, and what's considered
appropriate where.
The easy one is rec.radio.amateur.misc. It is what rec.ham-radio was renamed
to during the reorganization. Any message that's not more appropriate in one
of the other groups belongs here, from contesting to DX to ragchewing on VHF
to information on becoming a ham.
The group rec.radio.amateur.digital.misc is for discussions related to
(surprise!) digital amateur radio. This doesn't have to be the common
two-meter AX.25 variety of packet radio, either; some of the most
knowledgeable folks in radio digital communications can be found here, and
anything in the general area is welcome. The name was changed to emphasize
this, and to encourage discussion not only of other text-based digital modes,
such as AMTOR, RTTY, and Clover, but things like digital voice and video as
well. The former group, rec.radio.amateur.packet, should be removed by
September 21st, 1993. It is obsolete, and you should use .digital.misc
instead (or the appropriate new mailing list, mentioned below). The group
has .misc as part of the name to allow further specialization if the users
wish it, such as .digital.tcp-ip.
The swap group is now rec.radio.swap. This recognizes a fact that became
evident shortly after the original group was formed: Hams don't just swap ham
radio gear, and other folks besides hams swap ham equipment. If you have radio
equipment, or test gear, or computer stuff that hams would be interested in,
here's the place. Equipment wanted postings belong here too. Discussions about
the equipment generally don't; if you wish to discuss a particular posting
with the buyer, email is a much better way to do it, and the other groups,
especially .equipment and .homebrew, are the place for public discussions.
There is now a regular posting with information on how to go about buying and
selling items in rec.radio.swap; please refer to it before you post there.
The first reorganization added two groups to the list, one of which is
rec.radio.amateur.policy. This group was created as a place for all the
discussions that seem to drag on interminably about the many rules,
regulations, legalities, and policies that surround amateur radio, both
existing and proposed. Recent changes to the Amateur Radio Rules (FCC
Part 97) have finally laid to rest the Great Usenet Pizza Autopatch Debate
as well as complaints about now-preempted local scanner laws hostile to
amateurs, but plenty of discussion about what a bunch of rotten no-goodniks
the local frequency coordinating body is, as well as the neverending no-code
debate, may still be found here.
The other added group is rec.radio.cb. This is the place for all discussion
about the Citizens' Band radio service. Such discussions have been very
inflammatory in rec.ham-radio in the past; please do not cross-post to both
rec.radio.cb and rec.radio.amateur.* unless the topic is genuinely of interest
to both hams and CBers - and very few topics are.
The rec.radio.info group is just what its name implies: it's the place where
informational messages from across rec.radio.* may be found, regardless of
where else they're posted. As of this writing, information posted to the group
includes Cary Oler's daily solar progagation bulletins, ARRL bulletins, the
Frequently Asked Questions files for the various groups, and radio
modification instructions. This group is moderated, so you cannot post to it
directly; if you try, even if your message is crossposted to one of the other
groups, your message will be mailed to the moderator, who is currently Mark
Salyzyn, VE6MGS. The email address for submissions to the group is
rec-radio-info@ve6mgs.ampr.ab.ca. Inquires and other administrivia should be
directed to rec-radio-request@ve6mgs.ampr.ab.ca. For more information about
rec.radio.info, consult the introduction and posting guidelines that are
regularly posted to that newsgroup.
The groups rec.radio.amateur.antenna, .equipment, .homebrew, and .space are
for more specialized areas of ham radio: discussions about antennas,
commercially-made equipment, homebrewing, and amateur radio space operations.
The .equipment group is not the place for buying or selling equipment; that's
what rec.radio.swap is for. Similarly, the .space group is specifically about
amateur radio in space, such as the OSCAR program and SAREX, the Shuttle
Amateur Radio EXperiment; other groups cover other aspects of satellites and
space. Homebrewing isn't about making your own alcoholic beverages at home
(that's rec.crafts.brewing), but rather construction of radio and electronic
equipment by the amateur experimenter.
Except for rec.radio.swap and rec.radio.cb, all of these newsgroups are
available by Internet electronic mail in digest format; send a mail message
containing "help" on a line by itself to listserv@ucsd.edu for instructions
on how to use the mail server.
All of the groups can be posted to by electronic mail, though, by using a
gateway at the University of Texas at Austin. To post a message this way,
change the name of the group you wish to post to by replacing all of the '.'s
with '-'s - for example, rec.radio.swap becomes rec-radio-swap - and send to
that name@cs.utexas.edu (rec-radio-swap@cs.utexas.edu, for example). You may
crosspost by including multiple addresses as Cc: entries (but see below). This
gateway's continued availability is at the pleasure of the admins at
UT-Austin, and is subject to going away at any time - and especially if
forgeries and other net.abuses become a problem. You have been warned.
A Few Words on Crossposting
===========================
Please do not crosspost messages to two or more groups unless there is genuine
interest in both groups in the topic being discussed, and when you do, please
include a header line of the form "Followup-To: group.name" in your article's
headers (before the first blank line). This will cause followups to your
article to go to the group listed in the Followup-To: line. If you wish
to have replies to go to you by email, rather than be posted, use the word
"poster" instead of the name of a group. Such a line appears in the headers
of this article.
One of the few examples of productive cross-posting is with the rec.radio.info
newsgroup. To provide a filtered presentation of information articles, while
still maintaining visibility in their home newsgroups, the moderator strongly
encourages cross-posting. All information articles should be submitted to the
rec.radio.info moderator so that he may simultaneously cross-post your
information to the appropriate newsgroups. Most newsreaders will only present
the article once, and network bandwidth is conserved since only one article is
propagated. If you make regular informational postings, and have made
arrangements with the moderator to post directly to the group, please
cross-post as appropriate.
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
"If my car ran OS/2, it'd be there by now" -- bumper sticker
GCS d++ p+ c++ l+ m+/- s/++ g++ w++ t+ r
--
73, Paul W. Schleck, KD3FU
pschleck@unomaha.edu
Celebrating 60 years of the Univ. of Maryland ARA - W3EAX (1933-1993)
------------------------------
Date: 15 Nov 93 18:43:00 GMT
From: news-mail-gateway@ucsd.edu
Subject: ORBS$316.2L.AMSAT
To: info-hams@ucsd.edu
SB KEPS @ AMSAT $ORBS-316.N
2Line Orbital Elements 316.AMSAT
HR AMSAT ORBITAL ELEMENTS FOR AMATEUR SATELLITES IN NASA FORMAT
FROM WA5QGD FORT WORTH,TX November 12, 1993
BID: $ORBS-316.N
DECODE 2-LINE ELSETS WITH THE FOLLOWING KEY:
1 AAAAAU 00 0 0 BBBBB.BBBBBBBB .CCCCCCCC 00000-0 00000-0 0 DDDZ
2 AAAAA EEE.EEEE FFF.FFFF GGGGGGG HHH.HHHH III.IIII JJ.JJJJJJJJKKKKKZ
KEY: A-CATALOGNUM B-EPOCHTIME C-DECAY D-ELSETNUM E-INCLINATION F-RAAN
G-ECCENTRICITY H-ARGPERIGEE I-MNANOM J-MNMOTION K-ORBITNUM Z-CHECKSUM
TO ALL RADIO AMATEURS BT
AO-10
1 14129U 83058B 93304.58449144 -.00000081 00000-0 10000-3 0 2086
2 14129 27.1748 358.4423 6020940 126.4893 305.1053 2.05881853 78069
UO-11
1 14781U 84021B 93313.58249069 .00000229 00000-0 42927-4 0 6110
2 14781 97.7981 333.4777 0010810 254.3694 105.6328 14.69080500518069
RS-10/11
1 18129U 87054A 93314.04939054 .00000017 00000-0 11670-4 0 8119
2 18129 82.9214 130.8225 0010360 275.4234 84.5738 13.72325356319844
AO-13
1 19216U 88051B 93313.91272759 -.00000211 00000-0 10000-4 0 8126
2 19216 57.8912 284.9332 7213964 328.0558 3.5561 2.09724845 41418
FO-20
1 20480U 90013C 93310.07362541 -.00000005 00000-0 14874-4 0 6071
2 20480 99.0217 139.2984 0541030 125.0547 240.2545 12.83221816175512
AO-21
1 21087U 91006A 93314.29055835 .00000084 00000-0 82657-4 0 3674
2 21087 82.9398 304.7020 0035176 337.0887 22.8703 13.74528243139502
RS-12/13
1 21089U 91007A 93313.61484132 .00000056 00000-0 53208-4 0 6119
2 21089 82.9251 174.2800 0030580 1.6907 358.4344 13.74029689138495
ARSENE
1 22654U 93031B 93312.79592387 -.00000046 00000-0 10000-3 0 2081
2 22654 1.4077 114.0599 2932748 160.6003 214.5238 1.42203069 2633
UO-14
1 20437U 90005B 93314.26240544 .00000128 00000-0 57654-4 0 9113
2 20437 98.6068 36.8706 0011455 111.4215 248.8190 14.29802927198303
AO-16
1 20439U 90005D 93314.25650448 .00000093 00000-0 43829-4 0 7110
2 20439 98.6135 37.8762 0011873 112.5374 247.7066 14.29859897198314
DO-17
1 20440U 90005E 93314.72182474 .00000108 00000-0 49637-4 0 7113
2 20440 98.6156 38.5937 0011919 110.1078 250.1390 14.29997154198392
WO-18
1 20441U 90005F 93314.27363549 .00000092 00000-0 43527-4 0 7123
2 20441 98.6152 38.1661 0012426 111.7995 248.4510 14.29974899198337
LO-19
1 20442U 90005G 93314.26623889 .00000107 00000-0 48991-4 0 7115
2 20442 98.6160 38.3657 0012902 111.6029 248.6529 14.30067157198345
UO-22
1 21575U 91050B 93313.78644466 .00000117 00000-0 46604-4 0 4111
2 21575 98.4598 27.4629 0006935 224.2634 135.7989 14.36863544121573
KO-23
1 22077U 92052B 93314.21490842 .00000000 00000-0 10000-3 0 3084
2 22077 66.0804 18.4482 0004639 338.0608 22.0210 12.86281812 58628
AO-27
1 22825U 93061C 93305.38322237 .00000057 00000-0 31218-4 0 2082
2 22825 98.6783 18.2116 0008754 149.2634 210.9045 14.27587035 5170
IO-26
1 22826U 93061D 93305.66096033 .00000076 00000-0 39017-4 0 2093
2 22826 98.6791 18.4934 0009019 149.5441 210.6266 14.27689613 5227
KO-25
1 22830U 93061H 93314.69145093 .00000111 00000-0 52532-4 0 2112
2 22830 98.5800 27.0255 0012337 94.9544 265.3046 14.28015541 6518
NOAA-9
1 15427U 84123A 93300.72651427 .00000099 00000-0 62608-4 0 6087
2 15427 99.0865 343.0970 0014906 151.8994 208.2999 14.13555759457494
NOAA-10
1 16969U 86073A 93308.02577200 .00000107 00000-0 53892-4 0 5086
2 16969 98.5151 318.8770 0012448 270.5362 89.4395 14.24841200370532
MET-2/17
1 18820U 88005A 93313.86326152 .00000060 00000-0 48384-4 0 2105
2 18820 82.5401 83.0499 0017920 77.7053 282.6113 13.84696783292003
MET-3/2
1 19336U 88064A 93313.98312645 .00000043 00000-0 10000-3 0 2102
2 19336 82.5385 118.8020 0017396 88.4059 271.9055 13.16962219254409
NOAA-11
1 19531U 88089A 93307.95823027 .00000139 00000-0 84844-4 0 4080
2 19531 99.1482 286.6377 0012789 46.5585 313.6658 14.12928630263406
MET-2/18
1 19851U 89018A 93314.44174536 .00000042 00000-0 31952-4 0 2111
2 19851 82.5186 318.3186 0015511 116.9458 243.3286 13.84348503237428
MET-3/3
1 20305U 89086A 93313.78275180 .00000043 00000-0 10000-3 0 9124
2 20305 82.5475 62.1477 0016698 110.3082 249.9836 13.16023732194255
MET-2/19
1 20670U 90057A 93314.71352062 .00000015 00000-0 79036-5 0 7110
2 20670 82.5501 22.0091 0017060 42.7604 317.4880 13.84180249170390
FY-1/2
1 20788U 90081A 93314.27490495 .00000352 00000-0 25587-3 0 8161
2 20788 98.8528 336.2622 0014224 264.8255 95.1288 14.01329924163048
MET-2/20
1 20826U 90086A 93314.40511387 .00000040 00000-0 31266-4 0 7107
2 20826 82.5262 320.0564 0012856 307.6374 52.3617 13.83563412157505
MET-3/4
1 21232U 91030A 93311.55017164 .00000043 00000-0 10000-3 0 6133
2 21232 82.5434 326.2919 0013431 27.8915 332.2926 13.16456437122196
NOAA-12
1 21263U 91032A 93308.09045315 .00000189 00000-0 93717-4 0 8155
2 21263 98.6458 335.5750 0012543 165.4607 194.6943 14.22328054128523
MET-3/5
1 21655U 91056A 93313.85451209 .00000043 00000-0 10000-3 0 6115
2 21655 82.5506 271.6301 0014550 26.1377 334.0477 13.16825241107591
MET-2/21
1 22782U 93055A 93314.66191362 .00000093 00000-0 79632-4 0 2106
2 22782 82.5507 19.6100 0023265 115.4347 244.9226 13.82991020 9889
MIR
1 16609U 86017A 93314.97077396 .00004226 00000-0 55300-4 0 5720
2 16609 51.6183 202.0455 0005693 23.2148 336.9078 15.59529397 30542
HUBBLE
1 20580U 90037B 93307.41913862 .00000906 00000-0 78090-4 0 3593
2 20580 28.4692 246.8298 0004679 70.9135 289.1966 14.92902547192330
GRO
1 21225U 91027B 93314.39830284 .00016953 00000-0 18182-3 0 2202
2 21225 28.4634 313.5049 0075239 9.9355 350.2723 15.58504747 23130
UARS
1 21701U 91063B 93309.31219655 -.00002650 00000-0 -22264-3 0 4119
2 21701 56.9841 336.0504 0005602 88.9850 271.1633 14.96217444117417
POSAT
1 22829U 93 61 G 93289.11726978 .00000072 00000-0 37231-4 0 2042
2 22829 98.6763 2.0610 0010043 184.4594 175.6498 14.27975951 2862
/EX
------------------------------
Date: 15 Nov 93 19:15:32 GMT
From: yuma!galen@purdue.edu
Subject: RS FREQ COUNTER HOLD MOD!!!!!!!!!
To: info-hams@ucsd.edu
How to add a hold function to the Radio Shack RF Frequency Counter:
Ground TP 17. In the schematic, TP17 is pin one of U3, connected to
+5V thru a 47k resistor. On the circuit board, TP17 is on the display
side, just right of the lower-right corner of the IC. Grounds are about
1/4 inch below and to the right, the three non-tinned points in the large
area of metal. TP17 is the tinned pad next to a SM resistor marked '473'
for 47k.
I rigged a momentary switch to ground TP17 thru a 1k resistor (you never
can tell) and it works just fine! I drilled a small hole to mount the switch
just above the plastic depression so I could push the button with my right
thumb. A small toggle switch would fit.
I'll be trying the other TP's to see what wonderful things RS didn't put
on the front.
Galen, KF0YJ
------------------------------
Date: 15 Nov 93 17:56:23 GMT
From: news-mail-gateway@ucsd.edu
Subject: SAREX Keps & Update 10/28
To: info-hams@ucsd.edu
My sincerest congratulations to NASA and the STS-58 flight crew for their
outstanding performance in setting a new flight duration record.
Unfortunatly I have not been able to hear the shuttle on the advertised
frequencies for many weeks now.
If we can't fix this, can someone at least post instructions telling those
of us who want off this ride, how we can unsubscribe for now then
subscribe back in a few months? I can always delete messages, but this is
nonsense.
********************************************************************
Tim Baggett, AA5DF Electrical Engineering Student
New Mexico State University
Internet: WBAGGETT@DANTE.NMSU.EDU
AMPR: AA5DF@NMSUGW.AMPR.ORG US Snail: 1970 Buchanan Avenue
Twisted Pair: (505) 523-6829 Las Cruces, NM 88001
********************************************************************
------------------------------
Date: 15 Nov 93 15:02:34 GMT
From: news-mail-gateway@ucsd.edu
Subject: STUCK KEY -- turn it off?
To: info-hams@ucsd.edu
I've received this message 45 times today
and most every day since Oct 28.
-- isn't 10/28 over yet?
> Subject: SAREX Keps & Update 10/28
> Date: Wed, 03 Nov 93 01:09:40 UTC
> Date: Tue, 02 Nov 93 21:42:59 UTC
> Date: Tue, 02 Nov 93 20:47:48 UTC
> Date: Tue, 02 Nov 93 19:58:49 UTC
> Date: Tue, 02 Nov 93 18:44:09 UTC
> Date: Tue, 02 Nov 93 17:44:47 UTC
> Date: Tue, 02 Nov 93 15:44:50 UTC
> Date: Tue, 02 Nov 93 14:44:51 UTC
> Date: Tue, 02 Nov 93 13:44:50 UTC
> Date: Tue, 02 Nov 93 12:43:53 UTC
> Date: Wed, 03 Nov 93 02:01:50 UTC
> Date: Wed, 03 Nov 93 01:09:40 UTC
> Date: Tue, 02 Nov 93 21:42:59 UTC
> Date: Tue, 02 Nov 93 20:47:48 UTC
> Date: Tue, 02 Nov 93 19:58:49 UTC
> Date: Tue, 02 Nov 93 18:44:09 UTC
> Date: Tue, 02 Nov 93 17:44:47 UTC
> Date: Tue, 02 Nov 93 15:44:50 UTC
> Date: Tue, 02 Nov 93 14:44:51 UTC
> Date: Tue, 02 Nov 93 13:44:50 UTC
> Date: Tue, 02 Nov 93 12:43:53 UTC
> Date: Thu, 04 Nov 93 05:01:32 UTC
> Date: Thu, 04 Nov 93 03:44:57 UTC
> Date: Thu, 04 Nov 93 02:44:45 UTC
> Date: Thu, 04 Nov 93 01:44:47 UTC
> Date: Thu, 04 Nov 93 00:45:06 UTC
> Date: Thu, 04 Nov 93 00:15:11 UTC
> Date: Wed, 03 Nov 93 22:46:25 UTC
> Date: Wed, 03 Nov 93 21:44:35 UTC
> Subject: SAREX Keps & Update 10/28
... and ON and ON ...... :-(
Can the sender please unstick his sending key?
Paul Marsh N0ZAU Omaha
------------------------------
Date: 15 Nov 93 15:41:24 GMT
From: ogicse!emory!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!convex!horak@network.ucsd.edu
Subject: Telescoping antenna on HT
To: info-hams@ucsd.edu
In <1993Nov13.145441.7093@ke4zv.atl.ga.us> gary@ke4zv.atl.ga.us (Gary Coffman) writes:
>In article <2bu1v5$cf1@news.bu.edu> david@med-buspheb.bu.edu writes:
>>
>>Can I expect better results with a collapsed antenna vs a rubber duck?
Probably not.
>HTs are designed to work into horrible SWRs because they don't have
>a groundplane, your hand is it, and the ducky is a poor antenna as
>well. Still, a collapsed rod antenna isn't going to be very efficient.
>It won't hurt the radio to use the rod antenna collapsed, but it won't
>help your signal.
Gary speaks the truth. The collapsed telescoping antenna won't be any
worse than a duck. By the way, I'm extremely happy with my AEA Hotrod
antenna on my HT.
David
------------------------------
Date: 15 Nov 93 20:47:00 GMT
From: news-mail-gateway@ucsd.edu
Subject: The firestorm
To: info-hams@ucsd.edu
Well, the last pair of messages on the unstoppable STS-58 flight
messages forced me to laugh aloud. Not so much their content, but
the fact that we seem to have built a structure here (Internet/
mail-lists/Packet/Gateways) that has taken on a life of its own.
First of all, let's not take this TOO seriously. Yes, it is a problem,
but I am "forced" to waste about 1 minute of time each day, looking at
the subject lines and deleting those messages right away.
Secondly, it seems to me that some sort of original message ID
should be available that could be archived at a mail list site. This
list of previously-posted messages could be used to prevent multiple
broadcasts (e.g., the STS-58 Keps 10/28) without restricting
posting access to a few individuals. If we are going to modify the
software, why not in this way rather than locking up the gate?
All in all, this sort of behavior is VERY instructive and should be
discussed in the meeting forums of the Packet BBS, list-server and
Gateway folks. Let's not waste the opportunity to make the overall
system better in the future through analysis of what has happened
(and is happening!) here.
--Paul Beckmann
AMSAT member
WA0RSE
P.S. What is a 'bogon', Tom?
------------------------------
Date: 15 Nov 93 19:57:21 GMT
From: organpipe.uug.arizona.edu!helium!hlester@uunet.uu.net
To: info-hams@ucsd.edu
References <2bp64b$kuq@organpipe.uug.arizona.edu>, <1993Nov10.053243.23523@osuunx.ucc.okstate.edu>, <CGAArI.Ct8@cbnewsm.cb.att.com>
Subject : Re: 80m on 20m dipole
In article <CGAArI.Ct8@cbnewsm.cb.att.com>,
jeffrey.n.jones <jeffj@cbnewsm.cb.att.com> wrote:
>In article <1993Nov10.053243.23523@osuunx.ucc.okstate.edu> gcouger@olesun.okstate.edu (Gordon Couger) writes:
>>>>loss it is likely to put RF in the shack. The only way to fix this is
>>>This has not been my experience. I say the benefits of open wire/ladder line
>>>far outweighs its disadvantages. There seems to be a lot of fear about this
>>>stuff.
>
>Or what you could do is use coax from your rig to the outside of your shack
>and then use a 1:1 current balun to interface the coax to the ladder line.
>
Jeff, I tried one of these current baluns from Radio Works - they call it the Remote Balun - and it got quite hot from my 100 watts (the balun is rated 1.5 KW). The idea was to replace the puny voltage balun in my MFJ-948 tuner, as it
couldn't handle severe mismatches. The result was a steadily climbing SWR. The
Radio Works balun did no better. The solution? I replaced the MFJ balun with
one I made myself with two glued-together Amidon ferrite cores: FT-140-61, and wound #18 thermaleze wire in the same configuration as that on the MFJ core.
Howard hlester@as.arizona.edu
------------------------------
Date: 15 Nov 93 14:41:08 GMT
From: das.wang.com!wang!jcole@uunet.uu.net
To: info-hams@ucsd.edu
References <1993Nov5.231254.15145@es.dupont.com>, <2bqons$4t7@ds9.sim.es.com>, <2c0c4v$gbc@wrdis02.robins.af.mil>
Subject : Re: Fun with Radio Shack
sberman@robins.af.mil (CONTRACTOR Steven G. Berman;WR-ALC/LKS) writes:
>... What I did was wait
>until I had a purchase over $3.00 (almost every time I walk in the
>store), and then get the catalog FREE with the coupon. That's the
>intent. They're just trying to save a few bucks by not giving out the
>catalog to people who don't buy ANYTHING.
I picked up my catalog yesterday -- while there to buy something I saw on
sale (never pay list at the 'Shack -- it almost always ends up on sale if
you are patient!) and used the coupon, too. Also got the 'free' flashlite
(yeah, they nicked me for the batteries -- but quantity discount of 10%
applied, since there were five cells!) and a part for a project I am working
on. They didn't charge me for the catalog.
>Now, I guess, for those hams out there who just like to have the shack
>catalog to compare against or to say "yeah, there's a neat little
>toy," you now have to BUY SOMETHING to get it. If you're not
>interested in "shopping" at R/S, then why do you need the catalog?
>-- Steve , KD4YLB ... - . ...- .
Agree with you, Steve. But those who complain about the charge for the
catalog are the same types that look offended when you offer a resonable
price for something they are hoping to sell at a major killing at the
next hamfest! It takes all kinds...
73, John WA8ZPF
------------------------------
End of Info-Hams Digest V93 #1352
******************************
******************************