[WT-support] Has the $QSOB4 SO2R bug been fixed in V4?

[Tom W8JI]

Our station policy  (that some operators won't follow 
because they have the habit of saying "dupe" and not 
logging) is to encourage all ops to work and log all dupes. 
It actually winds up being faster, plus we do not risk a 
bigger penalty for a log error in some contests. Some 
contests now actually ask people to work and log all dupes.

----- Original Message ----- 
From: "Ed Muns" <w0yk at msn.com>
To: <support at win-test.com>
Sent: Wednesday, August 05, 2009 12:59 PM
Subject: Re: [WT-support] Has the $QSOB4 SO2R bug been fixed 
in V4?


TV-Bob and I have argued this point (working dupes or not) 
for years.  Even
in ARRL Sweepstakes with its long exchange, I strongly 
prefer to just work
dupes and not break my rhythm.  I also don't want to risk 
getting a NIL (and
penalty) because the other person doesn't have me in the log 
for the alleged
first QSO.  And, I certainly don't want to instigate a 
discussion about if
and when we worked earlier.  Bob and I will continue to 
disagree on this and
it is not a "truth" that long exchanges make the QSO B4 
message effective.

So, contesters will continue to take different sides on this 
topic.  But,
the QSOB4 macro bug in Win-Test should be fixed.

Ed - W0YK


  _____

From: support-bounces at win-test.com 
[mailto:support-bounces at win-test.com] On
Behalf Of Bob Wilson, N6TV
Sent: Wednesday, 05 August, 2009 09:30
To: support at win-test.com
Subject: Re: [WT-support] Has the $QSOB4 SO2R bug been fixed 
in V4?


2009/8/5 José Nunes CT1BOH <ct1boh at gmail.com>


Just work the dupe.
There should be a penalty for people who don't work 
dupes...


Obviously you have never entered the ARRL Sweepstakes 
contest, where you can
work a station only once the entire weekend, and the 
exchange is
extraordinarily long.  In this contest, it is much faster 
NOT to work the
dupe, especially when others are calling at the same time.

This bug makes the SO2R scenarios completely unusable in 
such contests, and
I am really hoping that it will be fixed soon.

73,
Bob, N6TV





--------------------------------------------------------------------------------


> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>