For me, there was not a single instance all weekend of a callsign showing up
as a multiplier along with its "/BUST" counterpart. In every case, it was a
"common" country. Besides, you could always double check the bandmap. Ah,
this isn't such a big deal - just a nuisance to see all those /BUST spots as
multipliers and having to click and delete each one.
Jim, I think I just figured out how to steal your run frequency ;-)
73,
Barry N1EU
>From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
>To: "Barry N1EU" <n1eu@hotmail.com>,writelog@contesting.com
>Subject: Re: [WriteLog] WL 10.30B Comments - stuttering, Enter key, packet
To: <writelog@contesting.com>
>Date: Tue, 19 Feb 2002 07:47:17 -0500
>
>At 08:39 AM 2/18/2002 -0500, Barry N1EU wrote:
>
>>6. "/BUST" should not show up as a multiplier. Seems like we visited this
>>a year or two ago.
>
>I disagree. It should be in there. What if 1S0DX was spotted? Then
>shortly afterwards 1S0DX/BUST is spotted. If the /BUST spot doesn't show
>up, then you'll never know that 1S0DX was a busted call. An extreme
>example, but it can happen when more subtle calls, i.e. YA5T spotted on
>wrong band, you go there and hear W3LPL CQing. If the /BUST call was there
>too, you may not have bothered to QSY and lose your run frequency.
>
>- Jim
>
>
>--
>Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
>USA +978-251-9933, <jjreisert@alum.mit.edu>, http://www.ad1c.com
>
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
|