开云体育

+ AA6YQ comments below + Please delete the errorlog.txt file from your DXKeeper folder, as it capture no useful evidence. I'd appreciate it if

John's definition of an intermittent problem: One that will never be there when you are looking for it! I operated for 20+ hours in the ARRL January VHF contest this weekend running 3 instances of

+ AA6YQ comments below + Yes, we've discussed it many times here over the years. 73, Dave, AA6YQ

I thought I remembered this coming up in the past. ?I found a 2020 post describing the same issue. ?It's a defect in th commercial control use to implement the display. -- Tom-KQ5S

+ AA6YQ comments below + LoTW has been inaccessible or down a lot since May. 73, Dave, AA6YQ

That fixed it.? Still wonder why it happened. Thanks Joe. Dale AA1QD

https://spectrum.ieee.org/open-source-crisis When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team

# AA6YQ comments below

Click the LotW button at the bottom of the Log QSOs tab to filter the log page for any QSOs with LotW Sent = U. Switch to the QSL tab and select LotW Click the Update from LotW button at the bottom

I have 5 QSO's in my DXK log from back in May that still show LotW Sent as "U" even though I have run the Sync LotW QSO's many times since uploading them. All of the later QSO's have updated Sent to

+ AA6YQ comments below + None of the errorlog.txt files that Paula sent me contained program errors. The next diagnostic step is to see if she can log a test QSO from DXKeeper's Capture window; if

The 2 most common reasons for QSOs not being logged are ... 1. DXKeeper is running with elevated privileges. That is set to "run as administrator". Outside of testing there is no legitimate need to

+ AA6YQ comments below + Is there an errorlog.txt file in any of your DXKeeper, DXView, or SpotCollector folders? If so, please attach it to an email message, and send the message to me via aa6yq (at)

I am getting an error message that JTAlert cannot confirm that a QSO was logged to DXKeeper. The QSOs in fact are NOT being logged to DXKeeper via JTAlert. This started when I installed the latest

I have 2 monitors. I did notice if I hover the mouse over, say, the call cell in DXKeeper, the popup menu is displayed on the other monitor. The same is true for SpotCollector. If I hover over one of

Works great in DXkeeper and SpotCollector. :-) Tom - KQ5S

Use // to begin a comment, and // to end a comment. For example, // US State // (State='<filtertextbox>') and (DXCCID in ('291', '6', '110')) To optimize visibility in a popup explanation, the comment

On Sat, Jan 18, 2025 at 08:08 PM, Joe Subich, W4TV wrote: # more AA6YQ comments below > > In principle, yes. However, I have no objection to having the SQL > popups being controlled by an *or* of

In principle, yes. However, I have no objection to having the SQL popups being controlled by an *or* of "Show control explanations" and "show SQL explanations". My goal is to be able to see the SQL

+ AA6YQ comments below + The proposal is to make popup explanations for the user-defined SQL buttons in the Filter panel at the bottom of the Main window's "Log QSOs" tab display "SQL comments" - the