Re: [Dx4win] LOTW report question

2016-11-21 Thread OZ0J Joe
On lotw.arrl.org go to Your QSO then Query and search one of the calls that is "busted". Click on details to the left after the QSO has been shown. I am not online now, but I guess that you can see upload date for the QSO. 73 Joe OZ0J -Oprindelig meddelelse- Fra: DX4WIN

Re: [Dx4win] LOTW report question

2016-11-21 Thread Rick Murphy
"I wasn't even on the air that day". Um, no. YOU uploaded a QSO for that day. Who you QSOd with ALSO uploaded a QSO for that contact. It matched, and generated a QSL. Someone else saying that they worked you never shows up in your LoTW downloads. Please check again. (It's quite possible for

Re: [Dx4win] LOTW report question

2016-11-21 Thread Barry
No other log files in use. On 11/21/2016 19:04, David Kozinn, K2DBK wrote: This is probably more something for the LoTW group, but unless something has changed you can't download a QSO that isn't a QSL. In other words, it has to match for you to get it. That's one of the security features in

Re: [Dx4win] LOTW report question

2016-11-21 Thread David Kozinn, K2DBK
This is probably more something for the LoTW group, but unless something has changed you can't download a QSO that isn't a QSL. In other words, it has to match for you to get it. That's one of the security features in LoTW. Is it possible that you had a different log file open on that day, or

[Dx4win] LOTW report question

2016-11-21 Thread Barry
I just did a LOTW upload and download. After uploading the interim QSLs rcvd file into DX4WIN, it told me that 12 QSLs were found with no QSOs. So I looked that the lotw.notfound report amd cjecked a few of the QSOs marked with an X. For some of them, I wasn't even on the air that day. Does

[Dx4win] DX4WIN.CTY country file Release #16.13 - 21 November 2016

2016-11-21 Thread Jim Reisert AD1C
The DX4WIN country file, DX4WIN.CTY Release #16.13 is now available from: http://www.country-files.com/dx4win-info/ You can read the release notes at: http://www.country-files.com/dx4win-cty-16.13-21-November-2016/ You can (and should) use the DX4WIN Data Updater to update the file: