开云体育

+ AA6YQ comments below + To avoid encountering the impacts of you callsign change one-by-one, take a look at https://www.dxlabsuite.com/dxlabwiki/NewCallsign 73, Dave, AA6YQ

QRZ Log requires a separate log for each callsign. Have you created and configured a QRZ log for YU0X? 73, ... Joe, W4TV

Thanks Dave, now I have a problem that when I log a QSO I get the following notification: "Upload of QSO to QRZ Log did not succeed:wrong station_callsign for this logbook YU0X doesnt match book

+ AA6YQ comments below + I don't understand your question. + Have you reviewed the step-by-step instructions in https://www.dxlabsuite.com/dxlabwiki/MovingBetweenPCs + ? 73, Dave, AA6YQ

GM Group, I'm planning on moving DXLabs over to my new Win11Pro PC. Is loading the previous registry settings onto the new PC, directory-specific? In other words, do I have to follow the

When posting a spot by right-clicking on the call in DXKeeper the spot is posted with the transmit frequency. ?I think it would be more beneficial to post the receive frequency. ?Tuning to the

+ AA6YQ comments below + The free *Process Lasso* tool enables your to specify persistent core affinities: https://bitsum.com/processlasso-docs/#default_affinities 73, Dave, AA6YQ

+ AA6YQ comments below Hello, I changed my callsign and would like the QSOs I made with the old callsign to be counted. What do I need to do to do that? + None of the award tracking mechanisms in

Hello, I changed my callsign and would like the QSOs I made with the old callsign to be counted. What do I need to do to do that? Tom YU3TA/YU0X

That’s not unusual. I’ve run across quite a few erroneous IOTA tags in the QRZ database call details tab. Some are probably where an activator visited an island and intended to remove it after the

The IOTA tag displayed in QRZ's entry for FK8HM's is "EU-148 Languedoc-Roussillon Region group", but the LoTW confirmation I received for a QSO made earlier today specifies OC-032. Neither the BigCTY

... via the Databases tab of DXView's Configuration window. Terminate DXKeeper, WinWarbler, and SpotCollector before directing DXView to update these databases. Because the GridDXCC database has been

Thanks Joe. I set my dates as MM-DD-YYYY way back in 2007 and have always had it that way. It was an optional way to do the dates then and that is what I was used to. I don't know why that is not an

1) Your dates are incorrectly formatted ... should be YYYY-MM-DD 2) I'm not sure <> works for not equal ... Try the following: (mode='CW') AND (NOT DXCCPrefix = 'K') AND (QSO_Begin BETWEEN

+AA6YQ comments below + For whatever reason, Windows considers that file to be open. I suggest that you terminate all of your applications and reboot Windows. 73, Dave, AA6YQ

Joe, It is a back-up file which was made automatically on shut-down and saved to a flash drive. Jim

It appears that I have worked a few DX stations in CW that I don't have confirmed or verified. I am attempting to write a SQL expression that searches for mode of CW and NOT a US QSO and it the QSO

E:\ZF2LC_2025-03-21_14-57-00.mdb failed" You are attempting to open a backup file created on 2025-03-21 14:57:00z That file is locked because it is open for writing by another instance of DXKeeper or

I get the message "attempt to open the log in E:\ZF2LC_2025-03-21_14-57-00.mdb failed The Microsoft Jet database stopped the process because you and another user are attempting to change the same data

About the application's affinity being transient. There is at least one way to set the affinity with DXLab Launcher. Here is the command line that I use to start WSJT-X in the Apps Started Before