[TRLog] QSO Party county line contacts

Ronald D Rossi rrossi@btv.ibm.com
Tue, 23 Sep 1997 09:36:09 -0400

>>>Tree N6TR said:
> rrossi@btv.ibm.com writes:
>> Did we ever come up with a good way of handling county line contacts for QSO 
>> parties? I know how to deal with rovers using a /M1, /M2, etc on the end of
>> the call. The problem is the multiple mults, zero Q point contact county line 
>> stradlers. If I just dupe a new county the serial number gets hosed. Do we 
>> need a 'NO QSO INCREMENT ON DUPE' logcfg.dat item(!!!! yikes not another !!!!) 
>> or did I miss the fix?
> This is a messy thing - the only way I know to do it is to log
> the two QTHs with a / between them.  Put the one you need as a 
> mult first.  

I just gave it a try with 6.11. the "/" causes TR to think it is a callsign 
update when CALLSIGN UPDATE ENABLE is TRUE. I turned it FALSE and it takes the 
first county fine, but ignores anything following the first "/". Only the 
first county shows up in the log (DOM file artifact??).

73 de KK1L ex N1PBT...ron (rrossi@btv.ibm.com) <><
Ron Rossi H/P SRAM Engineering -- IBM Microelectronics
QTH: Swanton, Vermont

FAQ on WWW:               http://www.contesting.com/trlogfaq.html
Submissions:              trlog@contesting.com
Administrative requests:  trlog-REQUEST@contesting.com
Problems:                 owner-trlog@contesting.com
Feature Wishlist:	  http://web.jzap.com/n6tr/trwish.html