Dave,
I have seen this same situation between DXKeeper and Spot Collector. Ever since I changed the TQSL file to exef as you recommended previously, the issue has not reappeared.
Bruce - K5WBM
toggle quoted message
Show quoted text
On Jun 15, 2024, at 8:40?PM, Dave AA6YQ via groups.io <aa6yq@...> wrote:
?# More AA6YQ comments below
clearing the "TQSL.exe pathname" in the TQSL panel at the bottom of the "QSL Configuration" window's LoTW tab eliminate the "on startup, DXKeeper isn't connected to Pathfinder" misbehavior?
+ DXKeeper does not use DDE to interoperate with TQSL - it directs Windows to start TQSL with a particular set of command line arguments, and then waits for TQSL to create a file containing the requested results ("news" about a new version or approaching Callsign Certificate expirations). With LoTW not available, TQSL never creates that file; DXKeeper eventually gives up.
+ It's possible that DXKeeper waiting for that file to be created is responsible for the "on startup, DXKeeper isn't connected to Pathfinder" misbehavior on some systems. What happened after you cleared the "TQSL.exe pathname"?
Thanks for such a quick response, Dave.
My DXLab Suite and PF is currently without any hiccup, but I'm going to attempt to recreate the PF hiccup thusly:
1) I reinserted what I had removed weeks ago, the "TQSL.exe pathname" in the TQSL panel at the bottom of the "QSL Configuration" window's LoTW tab and then proceeded to terminate DXLab Launcher and all enabled programs.
2) Restarted the PC.
3) DXLauncher opens all enabled programs.
4) DXKeeper opens and displays only a [CC] in it's titlebar and not what I would expect to see, [CC,PF].
5) A popup window, "DXKeeper: Updates from LoTW" reports, "TQSL is unable to connect LoTW". I acknowledge with an "OK" click and the popup closes.
6) I click on a previously logged entry in the DXKeeper log and focusing on the PF window I see no response there. What I expect to see is the selected callsign's QRZ page.
7) The hiccup has returned. PF will not respond to queries.
7) I close PF, relaunch PF, and now [CC,PF] is displayed on the DXKeeper titlebar.
8) PF works as it should for this session of DXLab Suite. With a reboot, the PF hiccup returns.
--------- Now, to return my system to not having the PF hiccup I follow these steps:
1) I remove the "TQSL.exe pathname" in the TQSL panel at the bottom of the "QSL Configuration" window's LoTW tab and proceed to terminate DXLab Launcher and all enabled programs.
2) Restart the PC.
3) DXLauncher opens all enable programs.
4) DXKeeper opens and displays a [CC,PF] in the titlebar as it should for me.
5) There is no popup window warning of LoTW being offline or TQSL difficulties nor of any other potential problem
6) PF responds as it should and has for several weeks now, but only after eliminating the TQSL.exe pathname as cited above. My reasoning for erasing the TQSL.exe pathname? Why launch an executable that cannot work until the LoTW server is restored.
All I know is that this detail has worked for me and once LoTW is restored I'll reinsert the TQSL.exe pathname.
# Many thanks, Joe! Your methodical approach demonstrates that when DXKeeper is not "connected" to Pathfinder at startup, the root cause is likely DXKeeper waiting for TQSL to respond to its "report the LoTW news" query.
# Rather than temporarily clear the TQSL pathname as you report above, I suggest instead making this change in the pathname:
TQSL.exe => TQSL.exef
# This will prevent DXKeeper from directing TQSL to "report the LotW news", but make it easy to restore the correct TQSL pathname after LoTW is again accessible.
Dave, I have not seen the "on startup, DXKeeper isn't connected to Pathfinder" popup. I've been spared that one <whew!>
# There is no such popup; that's just my concise description of the misbehavior.
Oh, and thanks for the clarification about DDE calls and such. You're the program guru. I most certainly am not.
# Nor should you need to be.
73,
Dave, AA6YQ
