开云体育

+ AA6YQ comments below Disabled QSL Queue entry for 6Y7EI on 2025-03-14 at 21:02:17 - station location "Williston, Florida" specified in QSO's QTHID item "williston" doesn't match station location

Dave, following your instructions got my DXK running properly again.? ?But when I logged some new QSOs and attempted upload to LoTW a similar problem came up: In DXK QSL tab... <Add Requested>

Thanks, Dave. Old logs gone, KG6JOT and AE6JW logs imported no errors. Next to import the big pile for NU6T. Rich, NU6T [email protected]> wrote: -- Richard Hill

# More AA6YQ comments below + My previous instructions were incorrect: I did say CTRL-CBA. No harm done. Do the CTRL-Delete to remove all QSOs from the current log. 73, Dave, AA6YQ

+ AA6YQ comments below + The CBA button performs a callbook lookup. + I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page

I'm losing track in the long series. I've cut and pasted here. My comments after the "*". This is where I think I am in the process: _____________ + AA6YQ comments below Repeated steps, Clicked on

Got it. Thanks, Dave. -- Bruce - W4NDX

+ AA6YQ comments below + Reviewing the Reference Documentation of each DXLab application you've been using may reveal useful functionality that you didn't investigate during your initial

+ AA6YQ comments below + That's described in the 3rd paragraph of the "Generating DX Spots" sub-section of Logging section of WinWarbler's Reference

what I like about it.. the outgoing spot window stays open....I been doing the hard way for years. Hope it helped somebody besides me.? will be chasing POTA cw most the day today.. if wife lets

i found it... jezz Depressing the Ctrl key while clicking the Spot ( https://www.dxlabsuite.com/winwarbler/Help/Logging.htm#Spot ) button will display WinWarbler's *Outgoing Spot* window, which

Can I spot with notes from WinWarbler? say working a POTA station... I log him from WW then go to dxkeeper right click on his call to get the spot with notes to come up and inform that he is pota.? I

That does appear to be a better way to simplify getting QSOs into QRZ log for non-subscribers. I tried it and at least for callsigns that have been reassigned one needs to "prove" ownership for the

There is one interoperation... GT will send QSO to DXKeeper setup is under config/logging I do not use GT under Windows. I prefer JT Albert. I have used it under Linux, no JT Alert linux

+ AA6YQ comments below When uploading QSOs to LoTW, previously logged QSOs recovered to DXKeeper from OneDrive log backup are uploading to LoTW without any errors. However, New QSOs, logged since

When uploading QSOs to LoTW, previously logged QSOs recovered to DXKeeper from OneDrive log backup are uploading to LoTW without any errors. However, New QSOs, logged since the recovery are being

Running W10 22H2 ... I have not seen anything here and know that this IS NOT A WINDOWS SUPPORT LIST but, for better or worse, Windows is the dongle that makes the DXLab suite work (N1MM+ Logger, too,

+ AA6YQ comments below + DXKeeper's interoperation with DXView and the latter's interoperation with DX Atlas and Google Earth provide more functionality than does Grid Tracker. For example,

One can submit? QSOs to QRZ for free via multiple methods, I have used them all: - manual entry at QRZ.com - import ADIF files - import from LoTW.? LoTW confirmations are imported and count toward

DXKeeper does not interoperate with Grid tracker. DXKeeper already offers two other interfaces for interoperating with WSJTX - direct (using SpotCollector) or with JT Alert. See: