locked Re: Logging from WSJT-X into DXKeeper

Joe Subich, W4TV


Are you using Windows 10? If so are you using insider preview
versions of Windows 10?


... Joe, W4TV

On 3/8/2016 9:41 AM, Nick Maslon - K1MAZ k1maz@... [HamApps] wrote:
Hi Laurie,

I've tried running everything normally and as administrator and the DDE
test fails both ways. Do you have any other suggestions on what to try?

Nick K1MAZ

On Tue, Mar 8, 2016 at 2:38 AM, 'Laurie, VK3AMA' groups08@...
[HamApps] <HamApps@...> wrote:


Sounds like DDE communications between JTAlert and DXKeeper is not
working. You can check that by opening the Settings window, "Applications
-> DXLab Suite -> Test" section.

The usual cause is running DXKeeper with elevated privileges (set to Run
As Administrator) or Launcher is elevated and it starting DXKeeper will
automatically elevate DXKeeper. The Windows security model prevents
processes running different privilege levels from communicating. There is
no reason to run DXKeeper elevated provided it is installed outside the Windows
protected "Program Files.." directory trees as recommended by the DXLab

de Laurie VK3AMA

On 8/03/2016 1:14 PM, k1maz@... [HamApps] wrote:


I'm trying to log from WSJT-X into DXKeeper through JTAlert, but I keep
getting this error message: http://imgur.com/XXBxulf . JTAlert appears
to be decoding from WSJT-X and reading DXKeeper's log (it shows QSO B4 in
the bar) but it can't write to the log. DXKeeper is open. Any help would
be greatly appreciated.

Thank you,
Nick K1MAZ

Join Support@HamApps.groups.io to automatically receive all group messages.