Okay, I'm hooked. My first Sweepstakes.
-----------------------------------------------
ARRL SWEEPSTAKES -- 1995
Call: NZ6N Section: LAX
Mode: SSB Category: Single Unlimited
Exchange: NR A NZ6N 66 LAX
BAND QSO QSO PTS SECTIONS
160 0 0 -
80 1 2 -
40 117 234 -
20 95 190 -
15 57 114 -
10 0 0 -
-----------------------------------
Totals 270 540 77
Score: 41,580
Power Out: 120 watts Hours of operation: 12.3
Equipment: TS-930s, KT34A, 40m inverted-Vee, CT V9.23
This is to certify that in this contest I have operated my transmitter
within the limitations of my license and have observed fully the rules
and regulations of the contest.
Randy Powell NZ6N
---------------------------------------------
Soapbox:
Thank you, WA6GDS, for raving about this contest -- y'all put on a
very satisfying event. Was able to get on for 3 hours in SS CW &
12+ hours in SS SSB and my enjoyment increased with each ten
sections worked. This is a major amount of time on the air for
me considering my shack is basically in my living room next to my
5- and 10-yr old's computer & next door to our bedroom. Talk
about getting along with the YF! Since my ant farm at this point
consists of a tribander at 50' and I learned from SS CW that you
can't do it without 40m, and working 40m by loading up a KT34A is
rather inelegant to say nothing of the miniscule ERP, I pointed
the yagi at 30 degrees and sling-shot a line over the boom and
pulled up a 40m inverted-Vee so my neighbor could discover new RFI
in her bullet-proof alarm system since the Vee was so close to her
house. Wait 'til I work up the gumption to switch on the 1.5KW.
It did get me on 40m where I made the most contacts. Next year
the shack & garage will be built (we have been "waived" ahead by
the state Coastal Commission, building "code" is not even remotely
fun to learn) and I'll put a trapped half-sloper back up or an
HFV-2 up on top of it for some better results. If anyone out
there has a manual for the HFV-2 who wouldn't mind faxing it to
me, please let me know by email to ad274@lafn.org (LAFN not 1AFN).
I'm collecting radial schemes.
SS is pure fun. After my portable Mendocino County CQWW CW effort
this past weekend, SS sounded friendlier (and more copiable) to
this rookie contester. And getting a sweep in my first attempt
goes down like a piece of homemade pecan pie. I had great fun
running and S&P-ing, and learning which sections I need to nail
down on 40m by Saturday night so they won't be impossible on
Sunday. Made several successful calls for needed sections (WVA,
BC??) just a few kcs up from where they had S&P-ed last. I
started getting excited Sunday afternoon when I nailed ID & DE to
attain 70 sections and realized I had a shot at a rookie sweep.
High point was when the 75th(MS) & 76th(SC) sections needed called
me on my run freq. saying they'd "heard" I needed 'em. I tell ya,
kvetching works! 77th section needed was SDG just south of here
180 miles so down I went to 75m, loaded up my 40m inverted-Vee and
broke in on a rag-chewer in SDG section for the sweep. My son,
KE6MAF, while playing Sim-Tower -next to me!- kept asking, "How
many left? Are they tough ones?" It was fun to share the
excitement with him.
73,
Randy NZ6N
ad274@lafn.org
>From Trey Garlough <GARLOUGH@TGV.COM> Fri Dec 1 16:07:39 1995
From: Trey Garlough <GARLOUGH@TGV.COM> (Trey Garlough)
Subject: UNconfirmed calls
Message-ID: <817834059.891672.GARLOUGH@TGV.COM>
> > XX1XXX: XX1XXX TEST
> > DL2HBX: DL2HBX
> > XX1XXX: DL2? 5NN00
> > DL2HBX: DL2HBX HBX 5NNA4
> > XX1XXX: TU XX1XXX TEST
> >
> Simple - in line four above, send only your call, no exchange. If he
> wants to complete the contact, he will send your call and await your
> exchange.
Yep, this is what the JA's seem to mostly do and it works well.
And regarding the "DX not signing their call" thread, I think the
person who said "dupe them if they don't send their call after a few
QSOs" is right. But here is an important hint: when you ask for the
DX's call, please say "CALL? 5nn05" or "5nn05CALL?". Do _not_ say
"5nn05 CALL?" because the instant the DX hears "5nn05 <pause>" he
is going to transmit his call (or TU) and you will be "doubling" with
him, and you can't copy his call if you are transmitting. And if the
DX was tranmitting his call while you were doubling with him, he will
be particularly unsympathetic when you come back and send "CALL?" on
top of his next three QSOs.
And as a person who is fairly proficient at CW, I am always astounded
by this type of thing which happens four or five times on Sunday:
me the pack a lid
-- -------- -----
HC8N HC8N TEST
G4BUO
G4BUO 5nn10
5nn14
HC8N
SM3EVR CALL?
SM3EVR 5nn10
5nn14
HC8N
F6BEE CALL?
F6BEE 5nn10
5nn14
HC8N
CALL?
Who is this guy sending "CALL?" What does he want from me? I'm
sending my call after every QSO.
Hint #2: on Sunday afternoon when you hear someone with few or no
takers at 36 WPM and you are having trouble getting the call, one
thing you can do is send "PSE QRS". If I have no takers, I will slow
down to about 28 WPM for a minute or so, or until I get you into my
log.
I don't mean to sound harsh, but long term soultion for folks having
trouble copying callsigns is for them to improve their CW and
contesting skills, rather than to ask everyone else to slow down all
weekend. Our group would not have managed to get 7750 QSOs into the
log (before dupes) if we had to tranmit at "least common denominator"
speeds.
My vote for best attitude goes to Martin Luther, VK5GN, who after
being the SSB contesting beacon of Australia for the last 20 years
has decided to take up CW contesting. His regular updates on this
mailing list as to his progress should be an inspiration to us all
(they are to me) to improve our own skills.
--Trey, WN4KKN/6 (aka HC8N)
>From snace@wsc.nasa.gov (Steve Nace) Fri Dec 1 17:06:30 1995
From: snace@wsc.nasa.gov (Steve Nace) (Steve Nace)
Subject: OO reports, who else??
Message-ID: <v01510105ace4e62253a4@[192.77.86.129]>
My station owner got an OO report due to my supposed lidness.
My Icom 765 readout said 14.000.8. My new wallpaper said I was
at 13.998.8.
Did anyone else get a report?
Please reply direct, NOT on the reflector. Summary if interest exists.
73 de Hose KN5H
>From Pete Smith <n4zr@ix.netcom.com> Fri Dec 1 17:07:02 1995
From: Pete Smith <n4zr@ix.netcom.com> (Pete Smith)
Subject: Vanity 610V now available
Message-ID: <199512011707.JAA04844@ix2.ix.netcom.com>
At 09:27 AM 12/1/95 CST, Kris I. Mraz wrote:
>Form 610V (for vanity callsigns) is now available. Our corporate atty
>in Washington has been watching for it for several of us back home.
>He faxed us one yesterday (Thursday).
>
>Now we just have to wait to be able to use it :-(
>
>
>73
>Kris AA5UO
>mraz@aud.alcatel.com
>
Our ARRL Director informed the local PacketCluster last night that ARRL has
received a master from which they can reproduce forms to satisfy the
requests they have. According to his message, they did not receive another
form, the instructions for use of the 610-V. Wonder if that's because the
latter form will have the dates for the various gates.
73,
Pete N4ZR (n4zr@ix.netcom.com)
>From mraz@rdxsunhost.aud.alcatel.com (Kris I. Mraz) Fri Dec 1 17:19:52 1995
From: mraz@rdxsunhost.aud.alcatel.com (Kris I. Mraz) (Kris I. Mraz)
Subject: Vanity 610V now available
Message-ID: <9512011719.AA00814@maverick.aud.alcatel.com>
Pete N4ZR said:
According to his message, they did not receive another
> form, the instructions for use of the 610-V. Wonder if that's because the
> latter form will have the dates for the various gates.
The form 610-V refers you to form 1070-V for fees and where to file. If
you don't have this form they say to call the FCC's Consumer Assistance
Branch at 800-322-1117 (or 717-337-1212).
Note. 610-V instructions don't give any instructions referring to the
fact that an applicant for a deceased relative's callsign must hold a
license level commensurate with the requested callsign.
73
Kris AA5UO
mraz@aud.alcatel.com
>From Jan & Del Seay <seay@alaska.net> Fri Dec 1 17:45:39 1995
From: Jan & Del Seay <seay@alaska.net> (Jan & Del Seay)
Subject: Rules and Regs
Message-ID: <9512011745.AA24281@alaska.net>
Having only been on the reflector a short time, I would like
to make a unrequested observation. We have several different
worlds that we may live in at our own discretion.
There is the strictly legal world, the interpreted legal world
and the world of good common courtesy and horse sense.
True, the R&Rs state that every communication must be identified
at the end. Then there are those who interpret a communication as
not including every new call. (Don't know how they interpret it
that way, but okay)
The last world is where you send your call and the call of the
other station for every qso. So it takes 50 milliseconds longer,
it won't slow your Q-Rate signifigantly as the "ur cl" guys
adding to the pile will certainly slow you down.
The procedure of not IDing each call is a fairly new phenomenon,
I believe started by the "Non-Rare" guy who figured out that they
could garnish a pile when no one knew who they were. (WFWL) This
seemed to gain popularity among the contesters for a different
reason, ie Q-Rate. Take a look at the high scorers in this years
CQWW and you'll note that two of the highest Multi-Multis (TY5A and
VP5FOC) are of the ID every call gang, and the conclusion must be
drawn that this is a successful procedure.
So much for my two-cents worth. Have fun.
-Del, KL7HF-
>From jreid@aloha.net (Jim Reid) Fri Dec 1 17:48:59 1995
From: jreid@aloha.net (Jim Reid) (Jim Reid)
Subject: KL7 in New Jersey
Message-ID: <199512011748.HAA12424@hookomo.aloha.net>
>X-Sender: seay@alaska.net (Unverified)
>To: jreid@aloha.net (Jim Reid)
>From: Jan & Del Seay <seay@alaska.net>
>Subject: Re: Vanity calls and my Error!
The subject is dear to my heart! Lots of these guys get their "DX"
call, then pull up stakes. I wish the Commission would go back to
requiring call sign to reflect the call area.
One of the ones that really frosts us up here is in the Honor Roll
list. This guy came to Alaska several years ago, got a license, moved
to W2 land, and proceedes to work dx. And he even has the gall to
use the KL7 Bureau! So poor John has to send his mail to NJ.
It really delutes the calls for us, and sure it is the same with
KH6.
73 and see ya' -Del, KL7HF-
73 and Aloha,
Jim Reid, AH6NB (Happily retired on the Island of Kauai)
Hawaii, USA Email: jreid@aloha.net
>From patd@eskimo.com (Patrick Dayshaw) Fri Dec 1 17:59:41 1995
From: patd@eskimo.com (Patrick Dayshaw) (Patrick Dayshaw)
Subject: UNconfirmed calls
Message-ID: <199512011759.JAA14325@mail.eskimo.com>
>Miscopying calls should not be taken lightly. YOU WILL LOSE CREDIT FOR
>THE CONTACT IF THE *OTHER* GUY MISCOPIES YOUR CALL.
Snip..........
>One question arises - is this policy fair? Let's suppose the following
>occurs:
>W2UP: CQ CQ TEST DE W2UP W2UP K
>DX: DL2XXX
>W2UP: DL2XXX 59905
>DX: TU 59914
>W2UP: TU TEST DE W2UP
>In this exchange DL2XXX never sent my call, so I don't know if he got it
>right or not. If he didn't, the contact's removed from the log. Sound
>fair? Not to me. Suggestions?
>73 Barry - W2UP
Well, although I'm sure this doesn't make many of the "high rate" types
happy, and yes, recognizing that it's NOT required under U.S.
law/regulations, if I have ANY DOUBT about your call I use my "Insert" key
to send your call and my exchange. I'm sometimes rewarded (yes, I'm sure it
could only be a reflection of my low skill), with a call correction from the
station I'm working. Since I'm almost always in the S&P mode this works for
me. Slows your rate I suppose, but then you don't lose a Q if I blew it.
I'm in the score category where chances are nobody bothers checking my log
anyway, or at least I've never seen a score reduction so I expect it may
benefit you more than me. I guess the question for you then is - Does your
statistical analysis reveal that the total points you lose to bad calls vs
the extra time it takes for me to confirm your call with my exchange make it
worth it? In the 4U1VIC example that may have been the case, as two mults
is indeed a heavy penalty for you or me.
As to the fairness, yes I think it is fair. A valid QSO requires a valid
exchange in BOTH directions. BOTH operators have responsibilities to ensure
that a valid exchange takes place. Sometimes that requires a high speed op
to QRS or ask for a confirmation, thus slowing the rate. After all a high
rate of busted calls only gets you in the Disqualified Box.
Yes, I see all the skill based insults that fly around here, but the bottom
line is the "big kids" need the "little kids" for points, so they just have
to adjust to the fact that the game includes some of us "low-skilled types"
rather than just the "always faultless pro's". It's not like a foot race
where it's just the runner and the track. Each QSO is in fact, a team
effort that includes two contestants who may be competing against one
another on one level, but for that single QSO they are both on the same team
and have the same goal, a VALID exchange.
Confirming your call is what I do. Probably irritates a few, but based on
the opinions expressed here, I suspect there is just no way to avoid that
anyway.
73
Patrick, WA7VNI........ patd@eskimo.com
>From Larry Tyree <tree@cmicro.com> Fri Dec 1 18:03:34 1995
From: Larry Tyree <tree@cmicro.com> (Larry Tyree)
Subject: SprINT contest
Message-ID: <199512011803.KAA25100@cascade.cmicro.com>
NINTH INTERNET CW SPRINT CONTEST
Contest period: 02:00:00Z to 04:00:00Z on Thursday December 28th UTC. This
is Wednesday evening in the USA.
Bands: 80 and 40 meters only (this is a real radio contest, no internet).
Suggested frequencies are 3530-3550 and 7030-7050.
Max power output: 150 watts at transmitter output connector.
Exchange: Consecutive QSO number (starting with one), name and state
or province or DXCC country (if outside W/VE). The name for
the first QSO is your name. For every QSO afterwards, the name
you send is the name you received in the previous QSO.
Call: CQ INT
The standard sprint QSY rule must be followed. This means that if you
solict a QSO (ie: with CQ or QRZ), after completing the QSO, you must
QSY at least 1 kHz before calling another station, or 5 kHz before
solicting another QSO.
Both callsigns must be sent during the exchange. Only one signal at a
time please and all QSOs are to take place on CW. All information
submitted must have been decoded during the contest. The use of post
contest detection or verification techniques or systems is not allowed.
Also, do not make round robin type QSOs. It will be very easy to spot
these with the names floating around. A round robin QSO is one where
you should QSY, but instead hang around to work the station who is
QSOing the station you gave the frequency to.
You may work the same station multiple times provided they are separated
by at least 3 other QSOs in both logs (regardless of band). For example,
if WN4KKN works N6TR, KKN must work at least 3 other stations before he
can work TR again. TR must also work 3 stations before working KKN
again. Changing bands does not eliminate the three QSO requirement.
The three QSOs must not be dupes themselves.
You must not work the same station or stations using any kind of schedule
or system. It is the intent of the dupe rule to make sure we don't run out
of stations to work. It is NOT the intent of this rule for you to change how
you would operate the contest if dupes were not allowed. If, in the log
checkers opinion, you have not lived up to the intent of this rule, your
log will be disqualified!!
Total score is the number of contacts you make. Any QSO found to be
defective in anyway will be removed from both logs (yes, if someone
miscopies your exchange, you won't get credit for the QSO, so QRS a
bit!!).
Please refrain from using vulgar or inappropriate names. If you receive
one of these names, feel free to either edit it or replace it with your
starting name. Make sure to make a note in your log so we know what you did.
Injecting the contest with an inappropriate name (in the log checker's
opinion) will result in a 1000 point penalty per occurrence. Examples of
inappropriate names may be found on MTV and generally start with the
letter "B".
Additional penalties will be assessed to people who work a significant number
of QSOs, but don't turn a log in. They will be given minus one point
for each QSO that we can verify actually occurred.
Logs must be sent in ASCII format via internet to n6tr@cmicro.com within
72 hours of the end of the contest. Figuring out how to send in your
log on the internet is PART OF THE CONTEST. If you need help, we will
try to assist the best we can.
Logs must show the band, time, station worked, number sent, number received,
name received and QTH received for each QSO. Also, please tell me the
name you start the contest with. We will assume the name you send is the
name received on your previous QSO, so you don't have to show that.
Results will be publised on CQ-CONTEST within 2 weeks of the contest. Logs
are checked using the K2MM LogZap software system. All checked logs will
be made available by FTP except for those requested by the submitter to
be kept private. Decisions of the judging committe are final and arbitrary.
Good luck, tell a friend and HAVE FUN!!
Tree N6TR
tree@cmicro.com
>From floydjr@nr.infi.net (jim floyd) Fri Dec 1 17:56:21 1995
From: floydjr@nr.infi.net (jim floyd) (jim floyd)
Subject: ARRL SS SSB Scores 95 V
Message-ID: <199512011805.NAA02546@moe.infi.net>
ARRL SWEEPSTAKES SSB 95
RAW SCORES
Compiled by
WA4ZXA
CALL OP/SECT SCORE QS0'S SECTS HRS
_______________________________________________________________
Single/OP/QRP/Q
WB0GAZ CO 104,636 707 74 24
KF9PL 76,350 509 75
KB2R (AT K1VR) EMA 70,984 467 76 24
AA0OB MN 66,900 446 75 19
N5NMY 52,052 338 77
W1AW CT 47,880 342 70
VE6SH 25,060 179 70 8
WA1GUV VT 16,032 67 48 12
KH6CP/1 CT 9,216 128 36 11
Single/OP/Low Power/A
NA5S 252,560 1640 77
VE4GV MB 248,864 1616 77 22
KP2/KE2VB VI 243,504 1602 76 23
W2CRS CO 224,378 1457 77 24
NM5M 222,530 1445 77
K7FR EWA 210,056 1364 77 23
N0AT MN 205,898 1337 77 24
WX0B NTX 202,972 1318 77 17
W7ZRC 202,202 1313 77 23
NA5Q NTX 178,948 1162 77
KB5WWA 176,176 1144 77
N5NM 171,248 1112 77 17
WA1S 169,400 1100 77 22
AA4RX 169,400 1100 77
W9UP (OP N0BSH) WI 168,784 1096 77 24
KC6X LAX 163,086 1059 77 24
WA4ZXA NC 159,544 1036 77 21.5
KJ6HO LAX 159,544 1036 77 24
K8BL OH 155,848 1012 77 22
KB3AFT 146,520 990 74 24
KN6DV LAX 146,300 950 77 22
K7MM EWA 142,604 926 77 22
N7LOX 140,910 915 77
AC1O/4 SFL 140,140 910 77 20
K3MQH 128,436 834 77
N3ADL 119,000 777 77 17
KM9P (OP AA4LR) GA 117,344 772 76 24
KE5FI 116,732 758 77 20
KG4W 108,262 703 77 17.7
WA6KUI TN 107,646 699 77 24
WA7BNM LAX 106,400 700 76 17
N3IXR WPA 101,332 658 77 23
N1PBT VT 87,750 585 75 23.1
AE2T WNY 87,150 581 75
NN5T 83,006 539 77 16
KI4DC 79,310 515 77 12
KG8PE MI 77,616 504 77 20
W6RGG EB 77,000 500 77 16
WA7LNW AZ 74,536 484 77 17
AE6Y 71,148 463 77 10
K0FRP 63,910 415 77
K8JLF EMA 61,256 403 76 12
K9JF WWA 61,000 396 77 8
NJ1V STX 50,050 325 77 13.8
WA8LLY/6 SF 42,966 279 77
KJ4VH KY 42,966 279 77 5
AD4VH 40,404 273 74
N3BDA EMA 40,032 278 72 16
AA7TF ID 38,624 284 68 13
KD4HXT/7 AZ 34,408 253 68 17
K8AKS 33,004 223 74 12.7
VE8EV NWT 31,098 219 71 16
KF4BTS (OP KM9P) 30,150 225 67
KK7A ID 28,670 235 61 3
AC5CT 25,728 192 67
NT2V SNJ 21,522 211 51 7
N5MTS NTX 19,154 157 61 17
VE6DBH AB 16,758 147 57 8
WB4VIM NC 17,346 147 59 12
KD0AV IL 17,818 151 59 5
W3EDU (OP N3KKM) 15,860 130 61 8
KC4URW 12,432 111 56 7
K7FD 11,858 77 77
NF6H ORG 11,858 77 77
K8NZ OH 11,660 110 53 4
KE4ZYV (OP KR4YL) SFL 11,430 127 45 3
KS4XG NC 10,000 100 50 5
K6XO/M UT 162 9 9 .5
WB4HFL NC 36 6 3 10
Single/OP/High Power/B
N5RZ WWT 364,826 2371 77 24
N2IC CO 346,654 2251 77 24
K6LL 330,946 2149 77
AA5BL 328,944 2136 77
KI3V NV 326,942 2123 77 23
KA5W 318,934 2071 77
W0SD (OP WD0T) SD 314,776 2044 77 24
AB5KD (OP WB5VZL) 305,228 1982 77
N3BB (OP AA5RB) 304,920 1980 77
W5CCP (OP AH9B) 303,226 1969 77
WC6H 300,608 1952 77
KF3P 292,138 1897 77
KE3Q 291,368 1892 77
WE9V WI 285,670 1855 77 24
W5WMU (OP ?) 285,516 1854 77
WB1GQR VT 284,130 1845 77 24
W4MYA VA 275,814 1791 77 24
K8AZ (OP NI8L) 254,562 1653 77
K8CC (OP WD8IJP) 252,406 1639 77
N9ITX/7 MT 250,404 1626 77 23
K2ZJ (OP WA2LCC) 240,394 1561 77
AA4NC (OP KI4HN) NC 236,082 1533 77
AB6FO LAX 235,928 1532 77 24
KI7WX 235,928 1532 77
WB2K 234,388 1522 77
KI7WX UT 234,234 1521 77 23.5
N4ZC (OP WB5M) NC 234,080 1520 77
W0AIH (OP N0AXL) 228,844 1486 77
WB0O 224,686 1459 77 16
WA7FOE WWA 216,524 1406 77
K0EJ TN 210,210 1365 77 19
K1RQ 209,802 1363 77 16
K0BH 208,670 1355 77
W6UE (OP N6DLU) LAX 201,278 1307 77 23
N4BP SFL 200,640 1320 76
K8FC 196,966 1279 77
K0IJL 194,348 1262 77
AA6MC SCV 188,958 1227 77 18.5
KF0DJ CO 178,640 1160 77
K0DI LAX 177,384 1167 76
NI6T SCV 174,020 1130 77 24
AB6WM SCV 167,860 1090 77
KL7Y AK 154,000 1000 77 13
AL7CQ 154,000 1000 77 14
WG9L 135,058 877 77
K8MR OH 124,586 809 77 11.1
W5ASP STX 116,800 800 73
AA3JU 114,114 741 77
K1DG 111,034 721 77 8
WO9Z 107,800 700 77 9.5
W5NN (OP KB5WBT) 101,024 656 77 7
AB7BS NV 100,640 680 74 14.2
N6TV 100,200 668 75 7.4
N1CC ENY 99,022 643 77 15
K0LUZ NFL 94,094 611 77 12
W6QHS 86,006 539 77 7
KB4CG 71,700 478 75 22
N7IXG 64,800 432 75
N2CFD 48,664 316 77 21
VE7UBC BC 45,124 386 58 6
W1IHN NC 35,112 228 77 6.5
K3SA 35,000 250 70 4
WD4MUR VA 11,858 77 77 10
KC7BNH NV 11,692 158 37 2.8
KI8W MI 4,242 101 21 1
Multioperator
K9RS 354,354 2301 77
KW8N 336,182 2183 77
K5MR 308,924 2003 77
NX0I 308,000 2000 77 24
AB4RU GA 303,688 1972 77
K1NG RI 287,210 1865 77 24
N4ZZ TN 263,648 1712 77 24
K0DD 249,942 1623 77
WV7Y EWA 243,320 1591 77
AB6LJ 240,856 1564 77
KC4DY VA 239,624 1556 77 24
KO4EW TN 229,768 1492 77
N6KI SDG 225,610 1465 77 23.8
VG6JY AB 214,214 1391 77 24
AB6LJ 209,286 1359 77
K1KP 209,132 1358 77
VE3RM 206,052 1338 77
KV6H 204,820 1330 77
N6ZS 203,280 1320 77
K6SG 203,280 1320 77
KF6A 201,740 1310 77
N2KJM NNJ 200,662 1303 77
VY1JA NWT 197,428 1282 77 22.5
VE2CUA PQ 196,812 1278 77 22
VE5RI SK 148,456 964 77 22.7
KP4VA PR 143,792 946 77 24
KC7KFF AZ 140,904 937 76 24
KF8UM WV 137,984 896 77 23
N3RR MDC 129,668 842 77 16
AA0WO IA 127,204 826 77
AA3JU EPA 114,114 741 77
W6OAT SCV 110,264 716 77
ND3F 107,800 700 77
KB2UGM WNY 108,262 703 77
AA7BG 102,102 663 77 13
KZ8E STX 87,626 569 77 22.5
N8JP 79,772 518 77 9
AE0M SCV 75,088 494 76 19.2
WB1HBB NH 48,510 315 77 13
K3WW EPA 46,200 300 77
KB1GW CT 44,992 304 74
AB7CZ ID 24,420 185 66 9
KC8FS WV 20,020 130 77 8
K5TM STX 17,640 140 63 7
W8PZS OH 7,332 78 47 5
Operator List for Multi-Op
Call Ops
VY1JA VY1JA,AA6KX
VE2CUA VE2DUB,VE2JNK,VE2ARW,VE2KWA,VE2TRN
K5TM K5TM,ALEXANDRA (AGE 11), JACOB (AGE 9)
VG6JY VE6JY,VE6LDX,VE6FR
N2KJM K2WK,N2BIM,N2MZH,N2KJM
AB7CZ AB7CZ,N0ZQM
NX0I NX0I,K0RWL,K0VBU,KM0L,WB0OIZ
KO4EW KO4EW,KQ4HC,KD4HIK
AB4RU AB4RU,AA4GA,N9HZQ
AA5B AA5B,K9RS
KW8N NZ4K,KF8TY,KU8E,KW8N
N4ZZ N4ZZ,W9WI
AA0WO AA0WO,KD9KX,KA0IES,WE0F,KA7QEN,NN0H
W8PZS NS8O,N3TLD,KB8JEE
K1KP K1KP,N1OEK,WX1Z
WV7Y WA7EGA,WB7AVD,WS7I
KB2UGM K2DB,KA2IYB,N2TUK,N2PEB,N2TWI,KB2KLP,KB2UVT
AE0M AE0M,N0BBS
KC7KFF KC7EFP,KC7CER,KC7FVT,KC7MOD,KC7MOC,N7UUJ
KC4DY KC4DY,KB4NT,WA4RDI
K9RS AA5B,K5TA
ND3F ND3F,N2SLN (son age 10)
K1NG KI1G,WF1B,KD1NG
N6KI N6KI,N6AZE,WB6NBU,N6UZH,N6XJM,KB6NMK
KV6H KV6H,N6IYS
N6ZS N6ZS,N6SNO,KM6AS,AA6WJ
K6SG K6SG,K3EST
KF6A KF6A,KJ6JC,AA6WJ
AB6LJ AB6LJ,AA6WJ,NV6O
*********************************************************************
Sorry about not posting this sooner but have been REAL busy with CQWW
CW scores. I will wait one more week before I make the final posting
for this contest. So if you got scores get them in now. I will not
modify the final posting period.
A note to everyone about any scores sent to me. Please put in the subject
line which contest it is. After this weekend I could be getting scores
from three different contests. Simple SS, CQWW, or 160 will be enough.
One request please and that is send me your section also. Being a small
pistol I only compete against the guys in my area. I know a lot of them
but with people moving in, you never know. You can take the list and
break it down anyway you want that way. Of course you cannot go by the
call. Feel free to email it to me if you have already sent your score.
Please remember when sending me email about correcting anything that
you include your call. I have no way of knowing who you are. Also if
you send in your score and do not see it within a short time, just wait.
I am waiting till I have quiet a few scores before I send out a posting.
This should help to cut down on bandwidth.
Anyone who sends me a score with no class on it will be put into the B
class. Feel free to email me and I will correct it.
73's Jim
Amateur Call: WA4ZXA
Email: floydjr@nr.infi.net
Packet Node: N4ZC
>From C Sim James, KK5EA" <jamescs@mail.auburn.edu Fri Dec 1 18:49:04 1995
From: C Sim James, KK5EA" <jamescs@mail.auburn.edu (C Sim James, KK5EA)
Subject: No Code stuff (was Re: 160 Magic)
Message-ID: <Pine.SOL.3.91.951201123506.14417F-100000@mallard.duc.auburn.edu>
On Fri, 1 Dec 1995, Tony Brock-Fisher wrote:
> overnight is such a good idea. If we contemplate eliminating the code
> requirement, we need to add another requirement which keeps up the
> standards for people entering the hobby. If we just keep eliminating
> standards, we WILL be CB sooner or later.
Tony et al.,
I agree that if we eliminate CW then there deffinately
needs to be a raise somewhere else along the testing pipeline. I am not
sure what it would be but I do think the testing process would have to be
beefed up. If it becomes too easy nobody will appreciate the licenses
they have and if you don't appreciate something it does not bother you to
treat it without respect. No respect = not caring what you do. After
all, the FCC seems to have lost its teeth so what is to stop folks from
trashing stuff up? It is already bad enough (i.e. good ole boys on 75M)
I started in this stuff about 2 years before the no code was
approved and at the time I really thought it would be the death of us.
It is not as bad as I thought, but we really do have some folks running
around out there on 2M without a clue. Trick is to educate them not slam
them. Althourgh I do slam them on occation I am only human and I am
doing my best.
73 es CUL,
Sim, KK5EA/4
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Over the modem.
|C. Sim James, KK5EA 03PO | Through the University.
|Email: jamescs@mail.auburn.edu |
|Packet: kk5ea@k4ry.#cenal.al.usa.na | Nothing but 'Net
///////////////////////////////////////
>From westnet@iol.ie (Tony Stack EI2GX) Fri Dec 1 19:09:04 1995
From: westnet@iol.ie (Tony Stack EI2GX) (Tony Stack EI2GX)
Subject: ??? Single op. assisted ??? CQWW
Message-ID: <199512011905.TAA17664@GPO.iol.ie>
Hello All,
perhaps somebody can clarify this matter.
ON4UN indicated in a message (or seemed to) that the Singl Op Assisted
Category in CQWW was ALL Band only,
however reading the rules as published in CQ Mag Sept. issue this would
not seem to be the case.
Single Operator Assisted is defined as same as rule III. A 1
well A says that Single Op cats are SINGLE BAND or ALL BAND
This would seem therefore to indicate that you can be assisted on a
single band.
What say you all ....
73's de Declan ei6fr
westnet@iol.ie
>>>>> Tony Stack EI2GX, Declan Craig EI6FR and Alan Dean EI9IF <<<<<
sysops DUBDX ,Dublin DX Cluster.
WESTNET DX GROUP
DX Cluster......................ei2gx > ei6fr
BBS .............ei2gx@ei7gm.#81.irl.eu
e-mail..........................westnet@iol.ie
>From Doug Brandon <dab@kaiwan.com> Fri Dec 1 18:37:57 1995
From: Doug Brandon <dab@kaiwan.com> (Doug Brandon)
Subject: Gettings 610V forms
Message-ID: <199512011837.AA271133077@corelis.com>
You can call the FCCs document retrieval system at 202-418-0177. Make
sure you are calling from your FAX machine! To get the 610V, order
document number 006108. It is six pages long. You can also order
other forms by ordering the index.
73 de Doug NF6H
/*--------------------------------------------------------------------*/
Doug Brandon http://www.kaiwan.com/~dab dab@kaiwan.com
>From w7ni@teleport.com (Stan Griffiths) Fri Dec 1 16:07:02 1995
From: w7ni@teleport.com (Stan Griffiths) (Stan Griffiths)
Subject: UNconfirmed calls
Message-ID: <199512011607.IAA16851@desiree.teleport.com>
W2UP writes:
>One question arises - is this policy fair? Let's suppose the following
>occurs:
>W2UP: CQ CQ TEST DE W2UP W2UP K
>DX: DL2XXX
>W2UP: DL2XXX 59905
>DX: TU 59914
>W2UP: TU TEST DE W2UP
>
>In this exchange DL2XXX never sent my call, so I don't know if he got it
>right or not. If he didn't, the contact's removed from the log. SOund
>fair? Not to me. Suggestions?
Well, in this scenerio, the log checkers are only given two choices: 1)
Remove the contact, or 2) Don't remove the contact. Of the two choices, I
favor #1. To do anything else assumes the log checker has more information
than is presented in the log. All he knows is that it is a busted QSO. He
does not know why. The problem is in the operating technique of the guy you
worked. If it is going to be fixed, he has to fix it.
Stan W7NI@teleport.com
>From w7ni@teleport.com (Stan Griffiths) Fri Dec 1 16:06:56 1995
From: w7ni@teleport.com (Stan Griffiths) (Stan Griffiths)
Subject: UNconfirmed calls
Message-ID: <199512011606.IAA16818@desiree.teleport.com>
DL2HBX said:
>there is another topic that really strikes me besides not signing every
>one to three contacts. It's the way that some stations confirm or better
>don't confirm the caller's callsign. This year it was extremely bad as I
>operated QRP and several times it was like this:
>
> XX1XXX: XX1XXX TEST
> DL2HBX: DL2HBX
> XX1XXX: DL2? 5NN00
> DL2HBX: DL2HBX HBX 5NNA4
> XX1XXX: TU XX1XXX TEST
>
>I could just guess from the timing that the contact had been ok but
>often there were some other stations in the background that might also
>have been DL2's or just DL's or whatever...
>
>So please...
>===========================================================================
>CONFIRM THE CALLER'S CALLSIGN, AT LEAST THE PARTS MISSED ON THE FIRST OVER!
>===========================================================================
>
>And by the way: There were neither DL2SBX, nor DL2HDX, nor DL2SDX, nor
>DL2HBN, nor DL2VBX, nor DL2HBQ, nor DL2IBX, nor DL2HB, nor DL2HTX, nor
>DL1HBX, nor DL2HBA QRV this weekend! As my computer did most keying
>this weekend I am sure that this is not what I had sent...
This last part looks like an attempt to get you to check your log and fix it
if you didn't get DL2HBX's call right. I question the ethics of this. If
they didn't get your call during the QSO, it is a busted contact and you
should not try to fix it after the contest.
>In my .NOT file there are 15 stations that *definately* miscopied my
>callsign (see above) and several attempts to correct it failed due to
>stronger stations answering the next CQs. I am sure there are many of
>the non-confirming stations that miscopied my call as well.
To me this is what operating QRP is all about. It is very difficult and
frustrating. If you can clean up your act this way, it takes away a great
deal from your accomplishment. I NEVER operate QRP because I don't have the
patience to work that hard for each QSO. This "cleaning the log afterwards"
has the same flavor as "making schedules in advance". In a radio contest, I
don't think much of either technique for enhancing your score.
Stan W7NI@teleport.com
>From k8mr@barf80.nshore.org (Jim Stahl) Fri Dec 1 15:39:57 1995
From: k8mr@barf80.nshore.org (Jim Stahl) (Jim Stahl)
Subject: 160 meter Special Event
Message-ID: <aDTFFD2w165w@barf80.nshore.org>
I don't have a simple way to move stuff from packet to the
internet, but here's a candidate for the great planning award:
ARRL bulletin ARLX072 reports that the Antique Wireless
Association will be operating a special event station (W2AN) from
7pm to midnight Saturday Dec. 2 and again Dec. 9, using a
restored transmitter that was originally used for trans Atlantic
contacts in 1921. "Listen for its bell-like tone on or near 1815
kHz" says the bulletin.
Yeah. Right in among all the 160 meter contest activity. Just
what contesters need, and with all the normal contest QRM just
what those who want to hear this transmitter need. Does anyone
know these AWA guys, and could they be persuaded that perhaps
Sunday evening (Dec. 3) would make for a much better experience
for all?
The ARRL bulletin lists their QSL route as AWA, 59 Main Street,
Bloomfield, NY 14469.
Jim K8MR k8mr@barf80.nshore.org
----------------------------
Jim Stahl
InterNet: k8mr@barf80.nshore.org
Basic Amateur Radio Frequency, BARF-80 +1 216/237-8208
"Totally devoted to Amateur Radio" - 24 Hrs a day 8/N/1 14.4k-300 baud
>From k8mr@barf80.nshore.org (Jim Stahl) Fri Dec 1 15:38:14 1995
From: k8mr@barf80.nshore.org (Jim Stahl) (Jim Stahl)
Subject: Contest Announcement Screwup?
Message-ID: <FaTFFD1w165w@barf80.nshore.org>
After the recent discussions about the ARRL's new policy of user
friendly, though incomplete, contest announcements in QST, and
after finding that at least a few guys took time off periods of
less than 30 minutes because of these announcements, get ready
for a potentially much bigger screw up.
I just got around to reading the announcement for the January VHF
Sweepstakes. In the various appeals to those who "have only an FM
transceiver", there is no mention of three significant rules
concerning FM: (1) No use of 146.52 or repeater frequencies;
(2) No solicitation of QSOs on repeaters; and the big one, (3) No
repeater QSOs!
The writeup claims that "if you own a hand-held or two, you can
make dozens of contacts while experiencing the fun and excitement
of VHF contesting..." . How this could be done without repeater
use is beyond me.
It's too late for a correction in QST, but the word needs top be
passed that it's not quite so simple as QST would seem to say.
Use of the ARRL official bulletin system, a few weeks before the
contest, would seem to be the best place to start. Otherwise we
face a the possiblity abuse by a few loophole seeking big guns
and/or of a lot of violations by little guys who never had a
reason to know otherwise.
Jim K8MR k8mr@barf80.nshore.org
----------------------------
Jim Stahl
InterNet: k8mr@barf80.nshore.org
Basic Amateur Radio Frequency, BARF-80 +1 216/237-8208
"Totally devoted to Amateur Radio" - 24 Hrs a day 8/N/1 14.4k-300 baud
>From Hans Brakob <71111.260@compuserve.com> Fri Dec 1 20:16:33 1995
From: Hans Brakob <71111.260@compuserve.com> (Hans Brakob)
Subject: (R)160M Magic
Message-ID: <951201201632_71111.260_EHM51-1@CompuServe.COM>
Oh nooooooo, Mr. Bill!
That %@@*&+-**&^% "code is good/code is bad" virus finally
migrated from "rec.radio.stupid.arguments" to the contest
reflector.
QRT! QSY! KNOCK IT OFF!
|