[WT-support] Re: Additional Items

[Simon M0CLW]

>>You can get WT sending "QSOB4" in case of dupe: edit the "INSERT" CW 
>>message and add the variable $QSOB4 after the $LOGGEDCALL one. In example, 
>>this is default "INSERT" message:
>>
>>$LOGGEDCALL $QSOB4 $F2
>>
>>That way, pressing the INSERT key will first transmit the logged callsign, 
>>followed by either the report or "QSOB4" if it's a dupe.
> 
> 
> I think that this illustrates one of the areas that are difficult to deal 
> with in a program that doesn't treat S&P and running differently.  

(snip)

Pete, I am interested by your comments, but would you mind 
clarifying one or two things for me please?

Firstly, why is it better to have a logging program that 
differentiates between running and S&P? OK, so you can use <INS> to 
send the exchange or whatever whilst in S&P mode, but you only need 
hit F2 in Win-Test to do exactly the same thing.

Having the functionality to switch between running and S&P is just 
making the software more complex - it's just another box to tick, or 
another key combination to keep in mind. Win-Test is 100% compatible 
with the KISS principle ;)

In Win-Test, if I'm running, I hit <INS> to send his call and 
exchange, and then the + [plus] key to send TU etc. If I'm S&Ping, I 
simply hit F4 to send my call once, and if he comes back to me, I 
hit F2 to send the exchange. Not exactly brain surgery :) But, I 
have only ever used N1MM a couple of times, so perhaps I'm missing 
the point!

I understand WriteLog sends QSO B4 if you're running and a dupe 
calls you. Basically, it is preventing you from making a [duplicate] 
QSO. Win-Test also does this, as explained by Olivier, with this 
$QSOB4 variable. I think just about all logging software gives you 
the option of sending QSO B4. I believe N1MM has a checkbox in one 
of its configuration dialog boxes that gives you the option of 
working dupes or not (i.e. defining whether the program will send 
QSO B4 or not). When you think about it, the Win-Test method is 
probably better (by utilising a variable) because you can decide 
whether to work dupes 'on the fly' (edit the message, and add/remove 
the $QSOB4 variable) - you may want to do this at a multi-op station 
where it may be the decision of the individual operator. Adding or 
removing the variable involves only a few key strokes - whereas in 
N1MM, you'd have to access the appropriate dialog box, uncheck/check 
the box that sets the option etc... Long winded because I don't use 
a mouse much during a contest.

Just as a side note: Personally, I never send QSO B4. IMO, sending 
QSO B4 to a station in a contest I now consider poor operating 
practice. And you're more than likely gonna lose QSOs because the 
number of people that come back and say "you're not in my log" is 
very high - of course you're not in their log because otherwise they 
wouldn't be calling :) And if the dupe calling is a 'casual' op who 
could well be using just paper for logging (or perhaps is using 
software that doesn't track dupes etc), I'd still work him because 
I've obviously made him happy - so he'll call me in contests again 
in the future (hopefully). Also, the language barrier can be a 
problem - although this is unique to SSB of course.

Sometimes 'dupes' are just calling to check out propagation and the 
like. For example, a dupe may call you (he sends his call), and your 
logging software would automatically send QSO B4 to him - but he may 
have wanted to ask a question, for example (maybe QSL route)! Now 
he's gonna be peeved :)

Besides, who said it's embarrassing if you've worked someone before? 
Just work 'em, log 'em, and you said yourself: nobody loses out. Of 
course none of this applies if you are assisted/multi-op and are 
using the cluster because the calls/spots which are dupes are greyed 
out on the bandmap.

I don't think anything of it if a dupe calls me. Besides, it just 
adds to the hourly QSO rate! ;-))

73, Simon M0CLW

-- 
Simon A. Pearson [ M0CLW ]
Worldwide Young Contesters