开云体育

Thanks Joe, I did enable, un-enable and re-enable and see if things changed. But no joy. vy 73, Dave, w0rx

Did you, perhaps, uncheck the "QSL" box as you printed labels, or addresses, etc.? If so, click "enable all" before clicking "Update Log" ... 73, ... Joe, W4TV

+ AA6YQ comments below I finished processing a batch of QSL cards from the bureau. After printing the labels, 3 col stick-ons, I pressed the "update log" button whose tooltip says: for each printed

I finished processing a batch of QSL cards from the bureau.? After printing the labels, 3 col stick-ons, I pressed the "update log" button whose tooltip says: for each printed QSL label, update the

Tnx Dave for the details. My problem was I was clicking for ssb/cw and it would work but not for ft8/4 which now makes sense. It is a very useful tool to stay away from dupes and of course, jt alert

+ AA6YQ comments below I read this in the documentation: "Unless you've checked an application's Log Debugging Info box, it should never produce an errorlog.txt file. If it does,..." I was doing some

Dave, I read this in the documentation: "Unless you've checked an application's Log Debugging Info box, it should never produce an errorlog.txt file. If it does,..." I was doing some housekeeping and

# More AA6YQ comments below Or they could use their satellite connection to work the rare island from their home station a few times while cooling their heels on the boat offshore, like several

I only activated US islands in FL, AL, and GA this year, so the DXCC confirmation wouldn’t be an issue in this case. So, I’ll take your suggestion, and worry about the rare one when/if I activate

+ AA6YQ comments below Instructions would be more consistent if the "log debugging info" check boxes were retitled "error log". You instructions and commentary refer often to "error log", but one has

It's clear that the root cause of the reported problems is erroneous DXCC information in QRZ callbook entries. Since you can't modify another station's QRZ callbook entry, the corrective action is to

+ AA6YQ comments below The IOTA report came back with the 'not found in log' indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus

+ AA6YQ comments below If the data is user-supplied and the QRZ webpage shows the correct data such as the case with R2FC and PJ4JA I don’t understand where else they are getting the user-supplied

+ AA6YQ comments below I have one (out of three) spot sources that regularly times out, but the indicator remains green in the spot source status tab......when I open that source window, it says

Thanks, Joe, for setting me straight and teaching me something new. I did not know the flag was used to determine the country, nor did I know you could click on the flag and change it. Tom-KQ5S

The IOTA report came back with the “not found in log” indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus call/6. VS6BG I

QRZ *DOES NOT SHOW THE CORRECT DATA* Look up PJ4JA and look closely at the flag and country beside the callsign ... it shows Curacao! JA3AVO who "manages" that entry has entered the wrong country in

+ AA6YQ comments below Thanks Dave, I was on 17.9.7, but updated to the latest and that fixed it. I have nine “not found in log(s)” I have to figure out, but five of those are my call from IOTAs I

If the data is user-supplied and the QRZ webpage shows the correct data such as the case with R2FC and PJ4JA I don’t understand where else they are getting the user-supplied data? Tom - KQ5S

I have one (out of three) spot sources that regularly times out, but the indicator remains green in the spot source status tab......when I open that source window, it says connections timed