I have tried to update my IOTA status several times using the .csv file downloaded from the IOTA website’s MY IOTA/DOWNLOAD QSOS, using the Update button in DXKeeper’s Check Progress/IOTA panel without success. The report shows “Updates: 0” and don’t contain any QSOs. Generated Progress reports show none of the new contacts contained in the .csv file are “Verified.”
I’m sure I must be doing something wrong, but can’t figure out what it is. I followed the steps in the online instructions faithfully. I checked the .csv file to be sure it contained my recently submitted and approved IOTA QSOs (it did) and I noticed the approved QSOs were “Accepted” rather than “Verified,” but I don’t know if that’s relevant. What am I missing? I’m pretty sure this worked for me last year…

Thanks, Steve K4WA

+ AA6YQ comments below

When I double click on a spot, sometimes an popup info box appears that shows me not just my progress on that DXCC entity but my progress with that specific call. I say "sometimes" since it works and then it doesn't. I know from following this group for years that it is usually a simple op error in a box checked/unchecked. I have reset from Launcher in that I use multiple monitors on occasion so I know it's all on my primary. For instance, if I click on 8E3R, an info box on DXView will show my the progress with YB but not that call specifically. I would like to see that call, the bands and modes.

+ If in the Options panel on the General tab of DXKeeper's Configuration window you have the "Display callsign progress on Lookup" box checked, then when you double-click a Spot Database Entry whose mode results in DXKeeper's Capture window being populated, the "Callsign Progress" window containing the information you seek will be displayed. This won't happen when you double-click a Spot Database Entry for a K1JT mode like FT8, as the QSO will be logged from WSJT-X, not the Capture window.

+ You can also cause this window to be displayed by right-clicking an Entry in DXKeeper's "Log Page Display" and clicking on the "Display progress for ..." command in the pop-up menu.

73,

Dave, AA6YQ

On 2025-01-21 10:37 AM, Gabor Morocz via groups.io wrote:

However, the ever rising Windows issues drive me crazy.

There should be no "Windows issues" if you follow the instructions
as written. In particular, DXLab Suite should *NOT* be installed
in C:\Program Files(x86) ... rather it should be installed in its
own directory tree, typically C:\DXLab Suite. In addition, none
of the DXLab Suite components should ever be configured to "Run
as Administrator" by default as that will cause problems with the
Windows User Account Control *and* problems with communication
between the various DXLab Suite applications and cooperating
applications.

73,

... Joe, W4TV


On 2025-01-21 10:37 AM, Gabor Morocz via groups.io wrote:

Larry,
Thanks for the kind words. I intend to start using the software in stages, using only the essentials at first.
Moving up in complexity will follow.
However, the ever rising Windows issues drive me crazy.
73,
Gabor, K7TES
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Larry, K4KGG via groups.io
Sent: Tuesday, January 21, 2025 08:28
To: [email protected]
Subject: Re: [DXLab] DXLab Worth; Installation Issues
Hello Gabor and Group,
I'm a long time user of DXLab software. Everything you need for DXing is here. Documentation is outstanding. If you can follow written instructions the software can improve your DXing in countless ways. No software I've used comes close to the quality of support Dave provides.
Understanding and employing some features may take some effort. The rewards are worth the effort.
Larry, K4KGG

Larry,
Thanks for the kind words. I intend to start using the software in stages, using only the essentials at first.
Moving up in complexity will follow.
However, the ever rising Windows issues drive me crazy.
73,
Gabor, K7TES

开云体育

I have multiple PJ4JA QSOs from the current operation both FT8 and CW
in my DXKeeper log and all are properly identified Bonaire.? There is
no override - either Jim's BigCTY or Clublog that references PJ4JA.

The problem is the QRZ xml record is FUBAR.

de Laurie VK3AMA
(JTAlert author)

Hello Gabor and Group,

I'm a long time user of DXLab software. Everything you need for DXing is here. Documentation is outstanding. If you can follow written instructions the software can improve your DXing in countless ways. No software I've used comes close to the quality of support Dave provides. Understanding and employing some features may take some effort. The rewards are worth the effort.

Larry, K4KGG

Any idea where the discrepancy could be coming from?

Do you have an old QSO from PJ4JA prior to 2010-10-10?

I have multiple PJ4JA QSOs from the current operation both FT8 and CW
in my DXKeeper log and all are properly identified Bonaire. There is
no override - either Jim's BigCTY or Clublog that references PJ4JA.

73,

... Joe, W4TV

On 2025-01-21 7:42 AM, Anthony - N2KI via groups.io wrote:

Question regarding these countries.
On occasion, I will get a message from Clublog saying that I am logging a PJ4 as Curacao but they are changing it to the correct country, Bonaire.? I have also seen the same message on occasion for European Russia <-> Kalingrad.
The sequence
JT Alert displays correctly as Bonaire
When DXKeeper receives the contact, it logs it as Curacao
Upon uploading (automatically) to Club Log > message indicating the country is incorrect
Club Log changes it to the correct country
DXKeeper logs it locally incorrect
I have to edit the contact manually and change the country.
My current DXCC database is 2.6.2
Any idea where the discrepancy could be coming from?
--
Anthony - N2KI

+ AA6YQ comments below

Thanks, it worked but every time I start it asks me if I would allow program to make changes to my device? Is that normal?

+ That's normal given your settings. Here's Perplexity's direction for stopping that:

--------------
To stop Windows 11 from asking if you would allow a program to make changes to your device, you can adjust the User Account Control (UAC) settings:

1. Open the Start menu and type "User Account Control" in the search bar.

2. Click on "Change User Account Control settings" in the search results.

3. In the User Account Control Settings window, move the slider to the bottom position labeled "Never notify"

4. Click "OK" to save the changes.

5. You'll be prompted to confirm the action. Click "Yes" to proceed

6. Restart your computer for the changes to take effect

By following these steps, Windows will no longer prompt you with the "Do you want to allow this app to make changes to your device?" message. However, it's important to note that disabling UAC completely can pose security risks, as it removes a layer of protection against unauthorized changes to your system.

-----------------

I made all exe files run as Administrator. Is that an overkill?

+ Yes: it's unnecessary. I suggest that you reverse those changes, as it could prevent your DXLab applications from interoperating with other applications you might want to utilize..

I also added the CI-V Commander.exe as an exclusion under the firewall.

But there are two other exe files (Commander587 and Commander1603). Should they be also added to the exclusion list?

+ No. The only executable you're running is

CI-V Commander.exe

73,

Dave, AA6YQ

Dave,
Thanks, it worked but every time I start it asks me if I would allow program to make changes to my device? Is that normal?
I made all exe files run as Administrator. Is that an overkill?
I also added the CI-V Commander.exe as an exclusion under the firewall.
But there are two other exe files (Commander587 and Commander1603). Should they be also added to the exclusion list?
73,
Gabor K7TES

+ AA6YQ comments below

Can anyone point me to the proceduire to add /P and /M to my call in DXKeeper? I can set up the myQTH for any location that I may work from, and have submitted to LoTW for the TQSL certificates for the new call (KE5WCT/P AND KE5WCT/M). And I know that I will have estabilish a certificate for new locations for TQL. I have added the appropriate new log for QRZ ClubLog, and am working on ones for eQSL.

In the meantime, I would like to how to create and use the new call's for making contacts and logging same.

+ When logging new QSOs, all you need do is make sure that the correct "Station Callsign" and "myQTH ID" are being recorded.

+ You can specify a default "Station callsign" in the upper-left corner of the Configuration window's Default tab; just remember to update it when you switch callsigns you're using over the air.

+ You can specify a default "MyQTH ID" in the "Log Settings" panel on the Configuration window's Log tab; just remember to update it when you switch the location from which you're making QSOs.

+ I suggest that you review



+ Before uploading/syncing with Club Log, specify the correct callsign on the "QSL Configuration" window's "Club Log" tab.

+ Before uploading/syncing with QRZ, select the correct "QRZ Logbook" on the "QSL Configuration" window's QRZ tab.


73,

Dave, AA6YQ

+ AA6YQ comments below

After a while the computer said:

CI-V Commander Window: Commander will terminate.

+ Commander only displays that message if it's being prevented by your Windows security settings from installing a component that it uses.

+ To work around this,

1. after Commander terminates, start Windows Explorer and navigate to your Commander folder, which by default is

c:\DXLab\Commander


2. in your Commander folder, right-click the entry for

CI-V Commander.exe

and select Run as Administrator from the popup menu


3. after Commander starts, terminate it

You should now be able to start Commander normally (without Administrator privileges)

73,

Dave, AA6YQ

+ AA6YQ comments below

Thanks, looks like LOTW is pretty erratic in responding, it even timed out by updating a single QSO from the log display panel, my internet is fine. Maybe I'll just wait a few days.

+ I just checked: LoTW is not responding here either.

Dave