>
>As with any Internet mail list, send your subscription request to
>" dx-request@unbc.edu ".
>
>Lyndon handles the list manually on a time available basis, so don't expect
>an immediate response like automated list handlers give. When I rehomed
>this list from my work machine to my home machine, it took around a week for
>him to get around to doing it.
>
> Regards / JBL KD1ON
>
>
>
Hi,
As a CONTESTER and a DXer I would like to be on both lists! I
haven't been able to get onto the DX forum yet...I have seen some people
say that the message text should simply say:
subscribe
and others say it should read:
subscribe dx
Does it matter? Perhaps since Lyndon does it manually, it doesn't?
73, Zack W9SZ
>From becker@shell.portal.com (Celia and Tony Becker) Sun Apr 9 07:57:29 1995
From: becker@shell.portal.com (Celia and Tony Becker) (Celia and Tony Becker)
Subject: DX Sprint thoughts
Message-ID: <199504090657.XAA05286@nova.unix.portal.com>
You wrote:
>Hmm... I don't know Sprint rules... :-(
The Sprint has a special QSY rule: 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.
This means that you _cannot_ just sit on one frequency and call CQ, waiting
for other stations to answer. You _must_ search and pounce every other
QSO.
>I always supposed it's a US only competition. But now I see I was wrong...
Several groups are starting local Sprint contests. One in Europe and one
int Asia. What we are discusssing in this thread is how a world-wide or DX
Sprint might be organized.
>And another hand, can you describe the meaning "hand-off QSO" for me?
>After this I would be able to answer your question.
What Dave meant by "hand-off QSO" is that, like a Relay-Team in a track
meet, the runner who is ending his sprint must QSO his team member to
"hand-off" the "baton" before the new runner may begin his sprint, making
more QSOs for the team.
AE0M, Tony Becker - becker@shell.portal.com - Silicon Valley, U.S.A.
>From Bill Turner <wrt@eskimo.com> Sun Apr 9 08:14:52 1995
From: Bill Turner <wrt@eskimo.com> (Bill Turner)
Subject: Followup on RTTY software
Message-ID: <Pine.SUN.3.91.950409000018.8129B-100000@eskimo.com>
Had several responses to the question about RTTY contest programs.
Several operators had used the Scotchlog program and all agreed it was
user-unfriendly and a poor second to WF1B. W5VSZ uses the Aries
program but pointed out that it is a DX/ragchew program, not really a
contest program. It does work well (bulletproof was the word) and does
CW, AMTOR, ASCII and packet, but not PACTOR or G-TOR. He commented it's
kind of old by today's standards.
Looks like WF1B is still king of the hill.
Thanks to those who responded. See you in the pileups!
73, Bill W7LZP
>From Bill Turner <wrt@eskimo.com> Sun Apr 9 09:02:19 1995
From: Bill Turner <wrt@eskimo.com> (Bill Turner)
Subject: Unshifted figures problem
Message-ID: <Pine.SUN.3.91.950409003855.17692B-100000@eskimo.com>
In working RTTY contests, I often get signal reports and exchanges like
this: 599 TOOQWE TOOQWE. Took me a while but I finally figured out what
is happening is the sending station is sending a figures shift immediately
before the 599 and then unshifting after the last TOOQWE. My TNC, a KAM,
has a command I can set to Unshift On Space (USOS on or off). What this
does if it is on, is to unshift figures case as soon as it sees a space.
If the sending station does not transmit another figures shift then I get
TOOQWE instead of 599123 or whatever. On the other hand if I set USOS
off, then it gets the figures right but doesn't return to character mode
when it should.
It would appear that the thing to do is always send a figures shift
command immediately before sending figures, but apparently not all
programs do this. Or is this a carryover from the old days of mechanical
senders/printers?
It seems like it is mostly the JAs that I get this on, but occasionally
US stations, too.
Anybody else having this problem? Anybody found a solution?
73, Bill W7LZP
|