I am a new DXLab user. A friend who uses the software helped meget set up. At the moment my QSOs are not getting uploaded to LOTW,although the first few QSOs I made with the software did get

Many thanks Dave...looks like I'm in business! 73, Don K9NR

Hi Joe, I'm not interested in cards at all, only LoTW confirmations. But, when I tried your expression, it returns "Invalid filter expression...." I'm puzzled by the APP_DXKeeper_LotWConfimration

Phil, I use: BAND='6m' and ((APP_DXKeeper_LotW_QSL_RCVD in ('Y','V') and APP_DXKeeper_LotWConfimration like '*G*') or QSL_RCVD in ('Y','V') or VUCCVerified in 'S','V') That gives Grids confirmed by

Hi all, Now that I am finally retired, and have some time on my hands (probably not a good thing!), and the fact that I have been playing on 6m (mostly FT8), I have been chasing grids on the band,

I've been working toward the JARL Worked All JA Award for a while. I'm at the point where I need just a few more prefectures. A couple of months ago, with Dave's help, I created an SC filter that

Dan Thanks that was what I was afraid night be the problem with the M1 chip. Can only hope someone is already using DXLab on an Apple with M1 chio Regards Ivor MM0IEL

I have, in the past, run DXLab (etc) on windows, on VMware Fusion, on an Intel based Mac. It ran pretty well, actually: https://www.qrz.com/db/c6asz%20 That said, what virtualization and OS

I am about to replace my present W10 laptop and thinking about going over to Apple. Will DXLab suite run on a Mac Air with the M1 chip? I would be interested to know if anyone is doing this and if so

+ AA6YQ comments below Slugging away at fixing my WAS status in DXK. Over 4700 Q's deep in the report and have been setting any contact check marked to 'V' in my log when it suddenly dawned on me

+ AA6YQ comments below You are right, Dave. However, it was the shortcut that was the issue. Upgrading did not change it but maybe it was not supposed to. + The shortcut doesn't need to change from

Think I found the explanation of the black check mark - marked for inclusion in a future application. Why ?? Again my fault for not checking first but AAARRRGGGHH !!! Makes less than no

Slugging away at fixing my WAS status in DXK. Over 4700 Q's deep in the report and have been setting any contact check marked to 'V' in my log when it suddenly dawned on me that I might

You are right, Dave. However, it was the shortcut that was the issue. Upgrading did not change it but maybe it was not supposed to. David NM5Z

Set it to C:\DXLab\Launcher\DXLabLauncher.exe or you will have the same problem the next time you upgrade. 73, ... Joe, W4TV

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

Joe, tt was set wrong C:\DXLab\Launcher\DXLabLauncher212.exe so I changed it to C:\DXLab\Launcher\DXLabLauncher214.exe and now it works fine. THANKS! NM5Z David

+ AA6YQ comments below Setting up DXLab applications has been quite a learning experience. I have achieved success receiving texts on my phone with cluster spots. Unfortunately, I receive

+ AA6YQ comments below When I open the launcher, it reads"new app upgrades". The current version is V2.1.2 and the upgrade is V2.1,4. When I click the upgrade button, it reads that it will terminate

+ AA6YQ comments below WAE is the only contest that does this. + Unless there's a reliable way to distinguish actual QSOs from QTC QSOs, the answer may be "don't use the N1MM-DXKeeper Bridge in