Repeat Please !
force12 at ibm.net
force12 at ibm.net
Thu Apr 6 22:34:43 EDT 1995
If you have sent me anything in the last few days, I have probably
lost it as I have had a major hard disk drive failure. I have the
system up and running again, but have lost a lot of Internet stuff.
So if you are waiting for me to respond to a post, please send it
Natan W6XR/2 -- FORCE12 at IBM.NET
>From Celia Tony Becker <becker at shell.portal.com> Fri Apr 7 04:41:00 1995
From: Celia Tony Becker <becker at shell.portal.com> (Celia Tony Becker)
Date: Thu, 6 Apr 1995 20:41:00 -0700 (PDT)
Subject: DX Sprint thoughts
Message-ID: <199504070341.UAA24837 at jobe.shell.portal.com>
> In February, when the NA Sprint is offered, we have the opportunity for a
> weekend period in which several four-hour slots could be arranged. One for
> EU, one for NA, one for Asia.
I like the idea. Lets set a 24 duration divided into 6 four hour periods.
A station in the single operator category may choose to operate
1, 2, or 3 four hour periods maximum. Choosing which periods to operate
becomes part of the strategy. This category will favor those with the
superior hardware to the extent that they are able to operate it.
Does anyone think a single operator can do more than 3 four hour periods?
How should Multi-Single, Multi-Two and Multi-Multi be treated?
> Combination schemes could apply: work any two and add the scores; cumulative
> scoring for all three; continental champs; etc.
I like the idea of a Relay-Team category too. Several single operators may
combine their scores for non-overlapping four hour periods up to a total of
the total 24 hour duration. The exchange for a Relay-Team is the team name,
but you can work the team once for each operator. This gives the spirit of
the multi-multi but the flavor of the Sprint.
Sprint format favors operator stamina and skill over hardware, so
this would make an excellent contest to use in qualifying for WRTC.
AE0M, Tony Becker - becker at shell.portal.com - Silicon Valley, U.S.A.
More information about the CQ-Contest