+ AA6YQ comments below I am trying to resolve a QSO that was reported in a "No matching QSO in log" message. Following the instructions at

+ AA6YQ comments below Tried the Safe Boot process a couple of times, and had problems with that. 1. Commander running under Safe Boot would not recognize my COM port 8 as installed by my IC-7600.

As I’m going through the optimization checklist, the webpage “Addictive Tips” on how to set the “affinity to an application” doesn’t cover Windows 10. In Windows 10, to check or change

I was referring to the email I sent to AA6YQ(at)ambersoft.com Am 01.11.2021 um 18:06 schrieb Dave AA6YQ:

+ AA6YQ commentsb elow + I read your message here: https://groups.io/g/DXLab/message/204177 + As you can see, your other email destinations are not shown. 73, Dave, AA6YQ

Dave, I have followed your recommendation by sending the more detailed test description and results to both yourself and Dick, W3OA. You could see that you were both addressees of

Dave, sorry it took me a few days to run your experiment. I did not need to disable automatic uploading, as I don't use it. I always upload to LOTW manually. Using the Capture window, I logged a QSO

I am trying to resolve a QSO that was reported in a "No matching QSO in log" message. Following the instructions at "https://www.dxlabsuite.com/dxlabwiki/LoTWNoMatchingQSOInLog", I get to the "Finding

If you go into the Bitlocker console, there is an option to back up the key. -Kurt, KR2C

FYI, Tried the Safe Boot process a couple of times, and had problems with that. 1. Commander running under Safe Boot would not recognize my COM port 8 as installed by my IC-7600. Device manager said

Dave & Mike Thanks much for replies and instruction. Got the sort an update done successfully. 73 Paul w2eck

+ AA6YQ comments below + So that I can see what's going on, please do the following: 1. on the Configuration window's General tab, check the "Log debugging info" box 2. wait until 5 new spots from

<plaws0@...> wrote: Actually, it's apparently branded "FileVault". ¯\_(ツ)_/¯ -- Peter Laws | N5UWY | plaws plaws net | Travel by Train!

Hello Dave, thank you for your immediate reply. Your configuration comments are not applicable here (nothing is checked in the special callsign tab and the spots are not older than the standard 15

An over-reaction? That *never* happens! :-D My company required disk encryption on my company-supplied MacBook Pro several years ago. Turned it on, OS X did it's thing, and that was that. Never

Yes, that is correct. It will only update the QSOs displayed on the filtered log. It is highly recommended that you make a backup of your log database before doing en masse updates. 73, Mike ND9G

+ AA6YQ comments below + On the lower section of its Main window's "Log QSOs" tab, DXKeeper provides the "Log Page Display", which can display all of your logged QSOs, or a subset of your logged QSOs.

+ AA6YQ comments below + Wolf, I investigated this issue when you first raised it two years ago. My recommendation then was "It's clear from your description above that incorrect commands are being

+ AA6YQ comments below + Juergen, I don't know anything about SparkSDR2DXC or WinTelnet-X.If a source of spots conforms to the telnet DXCluster protocol, then SpotCollector will interact with it. Note

Read some older postings on subject, but want to be sure. If I do a UTC filter of my log and generate a log page of QSO's in the desired time range, then use the Modify QSOs in Log Page Display- to