On Sun, Jan 15, 2012 at 8:57 PM, Rick Arzadon <n8x...@yahoo.com> wrote:
> Initially joined the DX4WIN Yahoo group.
> That one is utterly messed up with nasty ads, etc.
>
> The reason for joining the mail group here is that I use DXLab's DXKeeper
> to upload to LoTW.
>
> I did a search of the DX4WIN mail group and there are quite a few threads
> about missing states, etc.
>
> I have Emailed 17 hams that come back with a "WAS candidate doesn't
> specify US state" error.
>
> Of the 17 I have received 6 replies so far and most are DX4WIN users.
> Missing are also their county, zone(s), etc.
>
> There are a few that don't know how or have no way of setting up default
> parameters to meet the above critea.
>
> I am at a loss, as I have never seen DX4WIN in operation, nor have I read
> a user manual for the program.
>
> TNX es 73,
> Rick -N8XI
Rick,
Assuming that you're seeing problems with confirmations on Logbook of the
World not giving you confirmations for US states, this has nothing to do
with the logging program in use. When a user sets up a station location
using TQSL, they select the appropriate DXCC entity, subdivision, and zones
for that location. They're allowed to leave these selections blank or put
whatever they want into zone numbers, etc. No enforcement is done by TQSL
to ensure that the information they provide is either complete or
consistent.
I spent a lot of time fixing this issue, adding ways to allow TQSL to
ensure that zone numbers are correct for the selected entity as well as
requiring subdivisions to be correct (for the US, that's the State). For
example, you couldn't mix up your CQ and ITU zone numbers. That ability is
there in the current (1.13) version of TQSL.
Unfortunately, ARRL HQ rejected this change. The enhancements are in the
TQSL program but not enabled in the current TQSL configuration file, which
is where the verification data is configured. Without that, you can choose
whatever you wish.
If you have a QSL via LoTW with someone where the location data is
incorrect, the only thing you can do is to ask that ham to fix it. This has
NOTHING to do with what logger they use. Luckily, you can change the
location data in TQSL, re-sign a log and re-upload it and it'll correct the
confirmation.
Whomever told you that this was somehow related to DX4WIN was wrong. While
it's entirely possible for a logging program to detect and notify a user
when they mess up while defining their station location, I don't know of
any logger that does that. DXKeeper certainly doesn't keep users from
making these mistakes and I'm sure there's lots of DXKeeper-based QSOs on
LoTW with missing states, bad zones, etc.
73,
-Rick
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
