Bill G4WJS, what's your reaction to the MSK144 time logging situation being discussed in this thread? 73, Dave, AA6YQ 73 David A92GE

It makes ZERO sense that LoTW wants to work on "Start" time... the ONLY time that is significant is the END time - when the QSO is logged. Until the QSO is completed it is not a QSO... so of what

As I mentioned in a previous thread this situation is made worse by the fact that WSJT/JTDX both will log the start time of an incompleted QSO when a subsequent QSO is completed. I believe this is a

+ AA6YQ comments below Is this possibly a problem with K7TP placing his DXLab files in the protected X86 program directory instead of the recommended C:DXLab folder? And/or what user permissions he

+ AA6YQ comments below I am trying to set up WinWarbler on a Yaesu FTDX101MP. MMTY is working well as a stand alone and I am making RTTY contacts. Commander is working fine with both TX and RX Mode

I don't get into the BARTG contests for the same reason. Jim N7US

LotW does not recognize "end time". There is only one time involved in the QSO entry and by the LotW specification that is the start time. *ANY ONE OR ANY LOGGING PROGRAM* that uses "end time" is

Is this possibly a problem with K7TP placing his DXLab files in the protected X86 program directory instead of the recommended C:DXLab folder? And/or what user permissions he is logged in with?

Hi all I am trying to set up WinWarbler on a Yaesu FTDX101MP. MMTY is working well as a stand alone and I am making RTTY contacts. Commander is working fine with both TX and RX Mode and freq all

If that's the case, make all stations provide their state in the exchange. Don't make *some* stations use a call sign other than the one assigned by the regulator. It would be like CQWW saying all

+ AA6YQ comments below + The Launcher starts SpotCollector.exe + You results from booting Windows into "safe mode with networking" indicate that one of the applications being automatically started by

Thanks, Dave. I checked my anti-malware app (Malwarebytes) and found that I'd previously added C:\DXLab and C\DXLab\Commander to the "Allow List.": Malwarebytes says it will skip everything in the

Look, I've *watched* the news - this IS the end times!!! *rimshot* -- Peter Laws | N5UWY | plaws plaws net | Travel by Train!

+ AA6YQ comments below + If that's the case, your PC or Windows or both are not working correctly. With "log debugging enabled" when starting up, DXKeeper always adds entries to its errorlog.txt

+ AA6YQ comments below + Since MSK144 QSOs are made with WSJT-X, I would think that user community - perhaps with orchestration by the WSJX-X team - would articulate (and possibly automate) a policy

Following the above the Errorlog.txt is empty

yes, no easy answer for this. MSK144 qso can potentially take super long times.... I think the QSO end time might still have certain flexing as well based on when I get messages vs when the partner

When, exactly, does a QSO start? This may seem like a stupid question to those who have not tried meteor scatter. I may double-click on your CQ to start calling you at 11:00. You may hear me calling

+ AA6YQ comments below + I recommend against putting incorrect information in your log. Contact your QSO partner, point out the error, and ask them to resubmit the QSO with the correct start time.

+ AA6YQ comments below + That would explain the lack of a confirmation. I suggest that you contact your QSO partner and ask him or her to resubmit the QSO with the correct start time; that will