Doesn't the installer copy the new .exe to dxlablauncher.exe so the shortcut never needs to change? Check and see if you have a file called C:\DXLab\Launcher\DXLabLauncher.exe That exactly matches siz

Wow. Great troubleshooting!

Well crap. I thought i still had to "run as administrator "

Satpc32.exe is in C:Program Files (x86)/SatPC32 Data files are in C:Users/KI4US/AppData/Rosming/SatPC32 As I recall, I made no changes in the install away from defaults... I know I am an admin on the

I do not run satpc32 in elevated admin mode... Unsure why your system requires it.

Could this be the issue? Did you make this change from the dxlab setup info? https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking Continuous Tracking By default, SatPC32 only conveys information to

I use jtalert, which will log the wsjt contact directly into dxkeeper. No import required .. It's well supported and works great for me. https://hamapps.com/ Alternatively, in wsjt there is a menu to

I think the issue might be missing parens... The last "OR" will defeat the first terms .. Try this (Band = '6m') and (DXCCPrefix <> 'K') and ((QSL_RCVD in ('Y','V')) or (APP_DXKEEPER_LOTW_QSL_RCVD in

What does the device manager show? Could you be suffering the effects if the dreaded cloned prolific usb device driver impact?

There are some click buttons on dxkeeper that show more fields. I think the comments are within the "details" button but I'm not in front of logging pc right now to confirm. I tried to find in help fi

You will get the 1st error message repeatedly. I asked some hams to add a qsl image to their eqsl pages... One did, the others did not. It kinda bothered me to keep getting the error so I experimented

And your image does not get sent to the list...

Email me direct. I use n1mm wsjt and dxkeeper gateway....

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 se

Sorry. Wrong person. In the original message, it was noted: Qso was over 20 minutes long. Qso partner logged wso end time. Result us wso partner's wso time and poster wso time was greater than 30 minu

I thought you said the qso partner used qso end time....

Did you solve the mismatch by changing your qso start time in your log to be within 30 minutes of qso partner end time and resubmit to lotw? I too find msk qso's can take a VERY long time.

Did you click the option in config to use multiple monitors? Each app has it's own setting...

I understand. It was just an overview of what I did. This provided me exactly what you asked how to accomplish I generally only use dxkeeper as well, but for contexts, I add in n1mm for contest loggin

What I did for the recent vhf contest: Logged with n1mm and ran wsjt under n1mm Used n1mm to dxkeeper bridge to log contest contacts to my main log. Dxkeeper was running. Dxcommander was not. With thi