[Dx4win] LOTWREPORT - NOT FOUND
OK. I downloaded my confirmed report from LOTW and imported into DX4WIN. I got a message that this -notfound file had been written. I'm afraid I don't know what to do with it. I looked at a couple of the QSOs on the report and looked them up in LOTW and DX4WIN. They appear to be confirmed in both places (showing LOTW CNFM) so I don't understand why they are showing on this report and what, if anything, I need to do with this information. I did not find this addressed on Jim's DX4WIN uber-wonder page of info. Running v8.04 on Vista OS. 73 from the desert and thanks in advance, Fred/NA2U Wretched excess is just barely enough. __ 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
Re: [Dx4win] LOTWREPORT - NOT FOUND
Fred, My experience is that the ones with X's on the NOTFOUND Report are in LOTW but not matching up totally right in your Log. I click on them and change as necessary. Or, I merely ADD them to my Log in the Add Off-line mode if they aren't there. Strangely, I always wonder how they are in LOTW and not in my Log in the first place. But, I assume the LOTW is correct since everything is always entered in a secure mode by both parties. GL/73, Bob K8BL From: Fred - NA2U cw...@juno.com Subject: [Dx4win] LOTWREPORT - NOT FOUND To: dx4win@mailman.qth.net Date: Wednesday, December 14, 2011, 7:43 PM OK. I downloaded my confirmed report from LOTW and imported into DX4WIN. I got a message that this -notfound file had been written. I'm afraid I don't know what to do with it. I looked at a couple of the QSOs on the report and looked them up in LOTW and DX4WIN. They appear to be confirmed in both places (showing LOTW CNFM) so I don't understand why they are showing on this report and what, if anything, I need to do with this information. I did not find this addressed on Jim's DX4WIN uber-wonder page of info. Running v8.04 on Vista OS. 73 from the desert and thanks in advance, Fred/NA2U Wretched excess is just barely enough. __ 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 __ 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
Re: [Dx4win] LOTWREPORT - NOT FOUND
I see this all the time and it's mostly because of a mismatch in something like a county between what's in your log and what's in the LoTW confirmation record. I get a lot of these after I do a state QSO party and work some mobile/portable stations not in their home county. When they upload to LoTW they just use their regular certificate that populates their home county. DX4WIN sees this as a mismatch and doesn't set the LoTW confirm flag for the QSO. It's up to you to correct the log or just manually set the LoTW Cnfm flag. What makes things confusing is that the NOTFOUND file actually contains all the QSL data from a particular download, not just the ones with mismatches. With the NOTFOUND file open (on the logging window menu bar select LoTW, then select Review QSOs not found), look for the X in the leftmost column. For each of these double click the QSL line and it will bring up a list of possible matches in the log, with the fields that are different highlighted in red. When you find the one that corresponds to the QSL, double click on it and it will open it in the logging window for correction. You will also probably encounter some QSLs with less critical mismatches from the LoTW report file import. These differences will show up with IMPORT: xxx appended to the QSO in the log window's Notes for this QSO field. To see all of these, do a search for IMPORT and look through the resulting records. DX4WIN will do this for fairly trivial errors such as a difference in the last two characters in a 6 character Grid designation. The biggest source of such errors is always zone mismatches. It's amazing how many people have the wrong zone in their LoTW certificates, usually putting the IARU zone in instead of the CQ zone. You can correct the zone in each record if you wish, or just live with the log clutter. Just remember that some 4th call area states are in zone 4 instead of zone 5 and some 7th call area states are in zone 4 instead of zone 3. I think DX4WIN gets the zone right if you have the state field filled in (thank, Jim). 73... Randy, W8FN On 12/14/2011 19:43, R.T.Liddy wrote: Fred, My experience is that the ones with X's on the NOTFOUND Report are in LOTW but not matching up totally right in your Log. I click on them and change as necessary. Or, I merely ADD them to my Log in the Add Off-line mode if they aren't there. Strangely, I always wonder how they are in LOTW and not in my Log in the first place. But, I assume the LOTW is correct since everything is always entered in a secure mode by both parties. GL/73, Bob K8BL __ 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
Re: [Dx4win] LOTWREPORT - NOT FOUND
Hi Randy yes it's a mine field, which is the most correct information, sometimes they realise their mistake and upload again. I have also found people sometimes do the QTH change when they operated from a different location then upload their whole log and screw up everything previously loaded. To save my sanity I accept that there will be errors at this level and move on. :-) I think the Cnfm flag gets set differences or not. 73 John ZL1BYZ. -Original Message- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Randy Farmer Sent: Thursday, 15 December 2011 15:36 To: dx4win@mailman.qth.net Subject: Re: [Dx4win] LOTWREPORT - NOT FOUND I see this all the time and it's mostly because of a mismatch in something like a county between what's in your log and what's in the LoTW confirmation record. I get a lot of these after I do a state QSO party and work some mobile/portable stations not in their home county. When they upload to LoTW they just use their regular certificate that populates their home county. DX4WIN sees this as a mismatch and doesn't set the LoTW confirm flag for the QSO. It's up to you to correct the log or just manually set the LoTW Cnfm flag. __ 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
