This thread was three weeks ago but I thought this might be helpful.
I recently downloaded my LoTW report and received the dreaded not found
message and it turned out
that I had created the ADIF in N1MM and uploaded it to LoTW but forgot to
import it into DX4WIN.
73 de Terry KK6T
All,
-
From: Randy Farmer w...@tx.rr.com
To: Larry Gauthier (K8UT) k...@arrl.net; DX4Win Reflector
dx4win@mailman.qth.net
Sent: Friday, January 30, 2009 21:48
Subject: Re: [Dx4win] Measuring the LoTW import process
Today I downloaded an LoTW report from the ARRL web site and imported the
files
: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net]
On Behalf Of Larry Gauthier (K8UT)
Sent: Sunday, 1 February 2009 4:41 a.m.
To: DX4Win Reflector; Randy Farmer
Subject: Re: [Dx4win] Measuring the LoTW import process
Randy,
Thank you for this explanation, which makes perfect
Today I downloaded an LoTW report from the ARRL web site and imported the
files into my DX4Win log. When the process was completed, I somehow had 20
unaccounted for LoTW QSOs. Here's the details:
Before the download and import, I set a filter to get a count of the
existing LoTW confirmed QSOs.
Larry,
You should have a file with a .notfound file extension. This file
contains a report explaining why certain QSOs were not confirmed but
appeared as confirmed in the ADIF file. If you 'disagree' with the
explanation, zip up your log and adif file and mail it to me and I will
have a look.
Today I downloaded an LoTW report from the ARRL web site and imported the
files into my DX4Win log. When the process was completed, I somehow had 20
unaccounted for LoTW QSOs.
This is perfectly normal. After the first time I did a file download
from the site I've NEVER had 100% new QSLs in any
6 matches
Mail list logo
