Hi all-
Had the very same problem here. I assumed it had to do with the "QTH must
match for dup" switch which I used for the first time.
I did notice that even if the dup alert did not flash, the previous contact
was still shown in the "Check Call" box in a different color. That kept me
alerted and saved a number of dups.
73 de K0OU Steve in KC
----- Original Message -----
From: <Jimk8mr@aol.com>
To: <na-user@contesting.com>
Sent: Sunday, October 08, 2000 9:53 PM
Subject: [na-user] CQP (?) Dupe Checking Glitch
|
| Running the CQP this weekend, I found that the dupe checking worked
sometimes
| and not at others.
|
| I did start the contest with "QTH must match for dupe" not enabled, and
| switched it on somewhere fairly early on. I don't recall seeing the
problem
| before it was enabled, but there was no correlation I could detect between
| dupes where the original qsos made before or after it was enabled.
|
| The problem was that entering a call and hitting a space would not alert
that
| is was a dupe, although the check station window did show the previous
qso.
| If the non-alerted dupe was entered, it would be recorded as a dupe.
Perhaps
| half of the (dupe) qsos would be properly alerted, and half not.
|
| Comments?
|
| Jim K8MR
|
| --
| Submissions: na-user@contesting.com
| Administrative requests: na-user-REQUEST@contesting.com
| WWW: http://datom.contesting.com/
| Questions: owner-na-user@contesting.com
|
|
--
Submissions: na-user@contesting.com
Administrative requests: na-user-REQUEST@contesting.com
WWW: http://datom.contesting.com/
Questions: owner-na-user@contesting.com
|