+ AA6YQ comments below

I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA

That error indicates that the html page that is to be delivered by https contains links to content (eg. images, style sheets, etc) that are plain http.

+ Thanks Jim, and Laurie!

+ QRZ exerts no control over what a QRZ user includes in his or her "QRZ page". Pathfinder is web browser; it will attempt to render the web pages at which you point it when you specify a callsign and invoke one if its Search buttons. If the contents of a web page include security violations, then whatever mechanisms on your system detect and report such violations will do so.

+ Best as I can tell, every QRZ page includes this "plain http" reference:

http://www.arrl.org/lotw/

73,

Dave, AA6YQ

And that page contains at least one http link. Are there any Windows configuration changes that I could make that would prevent this warning from occurring?

And that is one relaxed looking kangaroo on your qrz.com page!
--
Jim McPhee
Placitas, NM
W5ABA

I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA

That error indicates that the html page that is to be delivered by https contains links to content (eg. images, style sheets, etc) that are plain http.


de Laurie VK3AMA

I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA

+ AA6YQ comments below

I have Spot Collector filtered for just FT8, but when I click on any of those FT8 spots, my Flex 6600 changes to the correct band and freq but changes the radio mode to SSB.

+ Are you using the direct interoperation between DXLab and WSJT-X (SpotCollector considers the latter a spot source), or are you using JT-Alert?

73,

Dave, AA6YQ

+ AA6YQ comments below

With regards to "everything you've reported above is correct behavior" I assume DXKeeper believing virtually all QSOs have been uploaded to Clublog is a result of something I have set in DXKeeper.

+ That's false, as I've already explained in

https://groups.io/g/DXLab/message/211020

"Either the ADIF files you imported into DXKeeper included <APP_DXKEEPER_ClubLog:1> fields in each QSO, or you set the APP_DXKEEPER_ClubLog in your logged QSOs after importing them."

+ Are you going to respond to the questions I asked you in

https://groups.io/g/DXLab/message/211042

+ ?

+ Have you contacted Club Log Support to determine why DXKeeper is unable to authenticate and submit QSOs?

73

Dave, AA6YQ

Hi Paul,
I don’t have a FLEX.

FROM Dave’s help files:

Flex Signature (6000) Transceivers

When controlling a Flex Signature transceiver, Commander's Main window's Filters panel provides Width , High-cut, and Low-cut controls. The Main window's Filters panel also provides Group selector that lets you quickly choose pre-set Wide, Normal, or Narrow width and shift settings that you've defined for the SSB, CW, DIGL, DIGU, RTTY, and AM modes on the Configuration window's Filter Groups tab. Enabling the show each mode's Filter Group setting on this tab causes Commander to parenthetically display each mode's last Filter Group in the Main window's Mode panel.

Have you checked your settings as above?

ED WA6WGS

I have Spot Collector filtered for just FT8, but when I click on any of those FT8 spots, my Flex 6600 changes to the correct band and  freq but changes the radio mode to SSB. Any ideas on how to correct?
tnx
paul w2eck

With regards to "everything you've reported above is correct behavior" I assume DXKeeper believing virtually all QSOs have been uploaded to Clublog is a result of something I have set in DXKeeper.

What might that be?

Tnx and vy 73, Dave. w0rx

--
vy 73, Dave, w0rx

+ AA6YQ comments below

finally" meant that I had trouble getting my FTDX3000 connected to my computer. Issue solved.

+ Thanks. I wanted to be sure that I didn't miss something in

https://www.dxlabsuite.com/dxlabwiki/ConnectingYaesu

 

I checked in Configuration to make sure the enable box was checked, it is. Then I noticed the work length was still set to 6. When I changed it to 8 the problem went away. When I now bring up Commander all is well.

+ So you had Commander configured to support multiple primary transceivers, in which case the "Word Length" setting on the Configuration window's "MultiRadio" tab must be set to 8. I'm glad that Commander is controlling your FTDX3000 now.

     73,

            Dave, AA6YQ

+ AA6YQ comments below

I finally got commander setup to work with my FTDX3000 Yaesu.

+ Why do you say "finally"? Was there a problem?

But, when I shut commander down and brought it back up the "word" length changed from 8 to 6. Change it back to 8 works but I have to do it each time I bring commander up. I have tried several thing to fix the problem. Any suggestions?

+ On the MultiRadio tab of Commander's Configuration window, there is a vertical row of four Enable boxes along the right side of the Control panel; are any of these boxes checked?

         73,

                  Dave, AA6YQ

In the message below, I meant to say "contact eQSL support".

73,

Dave, AA6YQ

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Tuesday, November 15, 2022 5:13 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXkeeper login fail to eQSL.cc

+ AA6YQ comments below


I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login. It logged in to eqsl.cc but I still got the login error message in DXkeeper. I renistalled DXkeeper and got the same result.

What else should I check

+ As I have already suggested, you should contact Club Log Support. Only they can tell you why the username and password you've selected are not enabling your instance of DXKeeper to authenticate with Club Log.

+ Uninstalling and re-installing DXKeeper could not possible solve this problem -- but could have created a much bigger problem. Never attempt to correct a problem with a DXLab application by uninstalling and then re-installing it unless there is hard evidence of a corrupted installation -- like error messages from Windows reporting missing components or libraries.

73,

Dave, AA6YQ

Email

+ AA6YQ comments below

I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login.  It logged in to eqsl.cc but I still got the login error message in DXkeeper.  I renistalled DXkeeper and got the same result.

What else should I check

+ As I have already suggested, you should contact Club Log Support. Only they can tell you why the username and password you've selected are not enabling your instance of DXKeeper to authenticate with Club Log.

+ Uninstalling and re-installing DXKeeper could not possible solve this problem -- but could have created a much bigger problem. Never attempt to correct a problem with a DXLab application by uninstalling and then re-installing it unless there is hard evidence of a corrupted installation -- like error messages from Windows reporting missing components or libraries.

        73,

              Dave, AA6YQ

I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login.  It logged in to eqsl.cc but I still got the login error message in DXkeeper.  I renistalled DXkeeper and got the same result.

What else should I check?

+ AA6YQ comments below

Thank you Dave. Apparently, I had not previously used the scripts to update and correct my log which contains records of contacts back to 1973.

 

So I ordered the scripts by date oldest to latest and then ran them one at a time. 

 

There were obviously a number of corrections.

 

Thanks again for the great toolbox that is DXLab Suite.

+ See

https://www.dxlabsuite.com/dxlabwiki/CorrectDXCCEntity

       73,

             Dave, AA6YQ

+ AA6YQ comments below

I noticed that there are DXCC databases in DXKeeper/Databases, SpotCollector/Databases, and of course DXView/Databases.  These have differing dates with the most recent being the upgraded one in DXView.  Did I miss a step upgrading that or is this expected?  The one in SC has a date of 3/28/2016.

+ When DXKeeper and SpotCollector start up, they check to see if DXView is installed. If so, they reference DXView's DXCC Database. Thus with DXView installed, one need only keep DXView's DXCC Database up-to-date.

      73,

             Dave, AA6YQ