Date   

Re: force Windows focus

Andy - K0AF
 

On Tue, May 11, 2021 at 11:33 PM, Greg wrote:

Hi Andy

I have attached a autohotkey script that should do what you want, it did on my system!  Once you have downloaded and installed Autohotkeys run the script and hold the "Windows" key and the "z' key and winwarbler should jump into focus. You can change the key combination by changing the line that is #z::  the # indicates the windows key and the z is obvious.

Cheers

Greg VK3VT

Hello Greg, thank you very much for the AutoHotKey script. It works as advertised and is exactly what I was looking for. I see AutoHotKey has a very long list of features and capabilities I need to explore. Your script was a big help getting me started.

Thanks!

Andy - K0AF


Re: TQSL Hangs

Dave / NR1DX
 

Ditto here
All DXLAB programs, TQSL  and Win10-64-pro are the latest releases

NO Problems whatsoever with uploads or updates

Dave
NR1DX

On 5/13/2021 12:30 PM, Phil Cooper via groups.io wrote:
Hi all,

Dave AA6YQ, Gary AB9M, Bernd KB7AK and Art W2NRA.....

Been seeing these emails from various folk today, and thought I would try some contacts to see what happens.
I also did the required update and reboot for Win10 updates yesterday (a feature update), and when I used DXK to sign and upload some contacts, all went as expected.

I am running Win10Pro 64bit, but I doubt that is making the difference.

Maybe it was just a passing phase, and is now fixed?

73 de Phil GU0SUP

-----Original Message-----
From: "CSM\(r\) Gary Huber - AB9M" <glhuber@...>
Sent: Thursday, 13 May, 2021 13:32
To: "DXLabs Group AA6YQ" <dxlab@groups.io>
Subject: [DXLab] TQSL Hangs

Automatic update check or manual intervention to check TQSL status hang and require the process to be "END TASK" via Task Manager, Windows 10 Pro 64 bit. No other anomolies in DXLab Suite have been noted.


73 ES DX,

Gary - AB9M










--
Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: TQSL Hangs

Phil Cooper
 

Hi all,

Dave AA6YQ, Gary AB9M, Bernd KB7AK and Art W2NRA.....

Been seeing these emails from various folk today, and thought I would try some contacts to see what happens.
I also did the required update and reboot for Win10 updates yesterday (a feature update), and when I used DXK to sign and upload some contacts, all went as expected.

I am running Win10Pro 64bit, but I doubt that is making the difference.

Maybe it was just a passing phase, and is now fixed?

73 de Phil GU0SUP

-----Original Message-----
From: "CSM\(r\) Gary Huber - AB9M" <glhuber@...>
Sent: Thursday, 13 May, 2021 13:32
To: "DXLabs Group AA6YQ" <dxlab@groups.io>
Subject: [DXLab] TQSL Hangs

Automatic update check or manual intervention to check TQSL status hang and require the process to be "END TASK" via Task Manager, Windows 10 Pro 64 bit. No other anomolies in DXLab Suite have been noted.


73 ES DX,

Gary - AB9M


Re: "TQSL is unable to contact LoTW"

ART W2NRA
 

Hi Dave,

I had this issue a couple of days ago. I figured out a copy of TQSL in a different directory. I deleted It and set TQSL’s location back to where DXLab’s settings said it should be. It’s working fine and no more pop up msg.

This is a guess but I think the culprit is Win 10 update.

73, Art W2NRA
CWOPS OPS #1955


Re: "TQSL is unable to contact LoTW"

Bernd - KB7AK
 

I saw the same issue yesterday, it happens directly after installing this week's Windows updates and the required reboot


TQSL Hangs

CSM&#92;(r&#92;) Gary Huber - AB9M
 

Automatic update check or manual intervention to check TQSL status hang and require the process to be "END TASK" via Task Manager, Windows 10 Pro 64 bit. No other anomolies in DXLab Suite have been noted.

73 ES DX,

Gary - AB9M


"DXing with DXLab"

Dave AA6YQ
 

I will be presenting “DXing with DXLab” at the (Virtual) International DX Convention this Saturday May 15 at 23Z (7 pm EDT, 6 pm CDT, 5 pm MDT, 4 pm PDT):

https://www.dxconvention.com/pages/program.html

 

To register, visit

 

https://www.dxconvention.com/pages/registration.html

 

My presentation will be publicly available afterwards.

 

       73,

 

            Dave, AA6YQ


Re: Log Transcription Features?

Dave AA6YQ
 

+ AA6YQ comments below
An Alternative Solution -
Many of us who had years of paper logs filled before adopting Computer Logging and have had to address this problem of transcription.  There are some who want to transcribe every paper QSO, and others who "cherry picked" those logs to collect Award significant QSO's.  (note - DXCC QSO's prior to ARRL adopting computer DXCC record keeping, the Call and other details were not included in their transcription, and DXCC credit is acknowledged only by the DXCCID number. However entering a Confirmed QSO in your log will then allow DXLab Progress Report for DXCC credit to  track LotW records.  I think this only applies to QSOs before 1982, and the advent of DXCC computer record keeping.) 
I found that direct entry into DXLab was tedious and not flexible, but if you can 'hire' a young student and typist to do the work it can be efficient and is an often suggested solution.

However there are other alternatives and I chose to create an EXCEL spreadsheet for entering basic QSO data and algorithms to convert those data into ADIF format which then could be easily IMPORTED into DXKeeper. 

+ DXKeeper can directly import tab-delimited files exported from a spreadsheet application, so there is no need for conversion to ADIF. See "Importing ADIF and Tab-Delimited Files" in

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm

+ The downside of this technique that a spreadsheet application won't detect and report many data entry errors as you're recording QSOs. Such errors will only be reported when you import the tab-delimited file, often requiring you to revisit the paper log in order to obtain the information required to correct the errors. 


      73,

               Dave, AA6YQ


Re: Log Transcription Features?

Norm_W4QN
 

An Alternative Solution -
Many of us who had years of paper logs filled before adopting Computer Logging and have had to address this problem of transcription.  There are some who want to transcribe every paper QSO, and others who "cherry picked" those logs to collect Award significant QSO's.  (note - DXCC QSO's prior to ARRL adopting computer DXCC record keeping, the Call and other details were not included in their transcription, and DXCC credit is acknowledged only by the DXCCID number. However entering a Confirmed QSO in your log will then allow DXLab Progress Report for DXCC credit to  track LotW records.  I think this only applies to QSOs before 1982, and the advent of DXCC computer record keeping.) 
I found that direct entry into DXLab was tedious and not flexible, but if you can 'hire' a young student and typist to do the work it can be efficient and is an often suggested solution.

However there are other alternatives and I chose to create an EXCEL spreadsheet for entering basic QSO data and algorithms to convert those data into ADIF format which then could be easily IMPORTED into DXKeeper. ,
What data to be entered is somewhat dependent on the end objective for this effort.  Mine was simple, DXCC credits, Mode and Band; and WAZ candidates,  Of course Date, Time and Call are essential as well.  (Note some awards did not exist prior to 1975, e.g. CW DXCC) 

Why create a spreadsheet?  Ease of entry, Copy and Paste, Copy Down, Create Dates and time, these tools and the many others available can make this chore much less frustrating.  BTW hiring that young typist to do the work works here even better - little to learn for them as most are familiar with spreadsheets.

The form of this tool is basic and essentially the same, however the content (data categories) can be, and usually is customized and to add categories will require some knowledge of ADIF nomenclature and architecture to conform with the rules of ADIF and EXCEL tools for Linking statements.

For anyone interested in exploring this tool contact me directly and we can evaluate your objective and the compatibility of what is available in the spreadsheet.
(note, others have created spreadsheet tools using similar techniques)

Norm W4QN


Re: "TQSL is unable to contact LoTW"

Dave AA6YQ
 

+ AA6YQ comments below
Dxview hangs with a command window open:
C:\DXLab\DXKeeper>"C:\TrustedQSL\tqsl.exe" -n 2>"C:\DXLab\DXKeeper\LotWNews.txt"
There is no response being shown.

This is after a restart for an install of KB5003173
https://support.microsoft.com/en-us/topic/may-11-2021-kb5003173-os-builds-19041-985-and-19042-985-2824ace2-eabe-4c3c-8a49-06e249f52527

Prior to the update, all worked well. I hope this might help

+ DXKeeper isn't actually "hanging" is it?

+ See my message to TQSL developer Rick K1MU in

https://groups.io/g/DXLab/message/201365?p=,,,20,0,0,0::created,0,,1,2,0,201365

       73,

             Dave, AA6YQ

 

 


Re: "TQSL is unable to contact LoTW"

James Fuller N7VR
 

I am Sorry,
I meant DXKeeper.
Jim Fuller N7VR

On 5/12/2021 9:18 PM, Dave AA6YQ wrote:
As you may recall, Rick, if the user has specified a pathname for TQSL.exe, DXKeeper on startup creates and runs a batch file that
invokes TQSL.exe with the -n command line option to be informed about

- a new version of TQSL
- a new version of TQSL's Configuration Data file
- expiring Callsign Certificates
- pending Callsign Certificates

Using the >2 command line option, the results of the operation are specified to be placed in a file named LotWNews.txt

Today, I and several other users began seeing this operation time out, causing DXKeeper to report "TQSL is unable to contact LoTW".

The Windows Task Manager shows that TQSL.exe is still running.

Running the batch file manually produces the same result: TQSL.exe starts, but doesn't terminate.

DXKeeper is still able to direct TQSL to upload QSOs to LoTW.

My guess is that LoTW is not providing the information that TQSL is requesting when invoked with the -n command line option; can you
investigate?

73,

Dave, AA6YQ





Re: "TQSL is unable to contact LoTW"

James Fuller N7VR
 

Hi Dave,
Dxview hangs with a command window open:
C:\DXLab\DXKeeper>"C:\TrustedQSL\tqsl.exe" -n 2>"C:\DXLab\DXKeeper\LotWNews.txt"
There is no response being shown.

This is after a restart for an install of KB5003173
https://support.microsoft.com/en-us/topic/may-11-2021-kb5003173-os-builds-19041-985-and-19042-985-2824ace2-eabe-4c3c-8a49-06e249f52527

Prior to the update, all worked well. I hope this might help.

Jim Fuller N7VR

On 5/12/2021 9:18 PM, Dave AA6YQ wrote:
As you may recall, Rick, if the user has specified a pathname for TQSL.exe, DXKeeper on startup creates and runs a batch file that
invokes TQSL.exe with the -n command line option to be informed about

- a new version of TQSL
- a new version of TQSL's Configuration Data file
- expiring Callsign Certificates
- pending Callsign Certificates

Using the >2 command line option, the results of the operation are specified to be placed in a file named LotWNews.txt

Today, I and several other users began seeing this operation time out, causing DXKeeper to report "TQSL is unable to contact LoTW".

The Windows Task Manager shows that TQSL.exe is still running.

Running the batch file manually produces the same result: TQSL.exe starts, but doesn't terminate.

DXKeeper is still able to direct TQSL to upload QSOs to LoTW.

My guess is that LoTW is not providing the information that TQSL is requesting when invoked with the -n command line option; can you
investigate?

73,

Dave, AA6YQ





"TQSL is unable to contact LoTW"

Dave AA6YQ
 

As you may recall, Rick, if the user has specified a pathname for TQSL.exe, DXKeeper on startup creates and runs a batch file that
invokes TQSL.exe with the -n command line option to be informed about

- a new version of TQSL
- a new version of TQSL's Configuration Data file
- expiring Callsign Certificates
- pending Callsign Certificates

Using the >2 command line option, the results of the operation are specified to be placed in a file named LotWNews.txt

Today, I and several other users began seeing this operation time out, causing DXKeeper to report "TQSL is unable to contact LoTW".

The Windows Task Manager shows that TQSL.exe is still running.

Running the batch file manually produces the same result: TQSL.exe starts, but doesn't terminate.

DXKeeper is still able to direct TQSL to upload QSOs to LoTW.

My guess is that LoTW is not providing the information that TQSL is requesting when invoked with the -n command line option; can you
investigate?

73,

Dave, AA6YQ


Re: TQSL is unable to contact LoTW

C. Michael D'Alto
 

Me three


Re: TQSL is unable to contact LoTW

Ron K5MM
 

Me too

K5MM/ron


On May 12, 2021, at 7:39 PM, dxradio33 via groups.io <k8fc@...> wrote:



Just for the record, I am experiencing the same anomaly.

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Andy - K0AF
Sent: Wednesday, May 12, 2021 18:25
To: DXLab@groups.io
Subject: [DXLab] TQSL is unable to contact LoTW

 

[Edited Message Follows]

When I open DXKeeper, after about a minute an error message pops up saying "TQSL is unable to contact LoTW". All was fine earlier this morning. I closed the Launcher for a couple work related calls and now I get this message when I start DXKeeper. I don't have any internet connectivity issues. I tried rebooting; I also tried booting and selecting "Enable Safe Mode with Networking". I opened Windows Security > Firewall & network protection > Allow an app through firewall and verified that DXKeeper is listed as allowed to communicate through Windows Defender Firewall.

When I open DXKeeper a Windows command window opens with the following command:

C:\DXLab\Launcher>"C:\Program Files (x86)\TrustedQSL\tqsl.exe" -n   2>"C:\DXLab\DXKeeper\LotWNews.txt"

That command window hangs for a minute or two and then closes. It creates a new LotWNews.txt file in the DXKeeper directory each time I open DXKeeper but the file is empty. In that directory there is also a file "LotWResult.txt". The time stamp on that file is from early this morning when everything was working.

I've opened the DXKeeper>Config>QSL Config >LoTW tab and verified my LoTW user name and password are correct. If I hit "Run" in the bottom panel in that tab (the panel labeled TQSL 2.5.7) the TQSL window opens. From there I can log in to the LoTW site. In the DXKeeper>QSL tab, the "Check LoTW Queue" button in the "LotW operations" panel shows the LoTW queue is 1m.

Thanks for the great support. I know my problem will be solved shortly (this problem anyway).

73,
Andy - K0AF


Re: TQSL is unable to contact LoTW

dxradio33
 

Just for the record, I am experiencing the same anomaly.

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Andy - K0AF
Sent: Wednesday, May 12, 2021 18:25
To: DXLab@groups.io
Subject: [DXLab] TQSL is unable to contact LoTW

 

[Edited Message Follows]

When I open DXKeeper, after about a minute an error message pops up saying "TQSL is unable to contact LoTW". All was fine earlier this morning. I closed the Launcher for a couple work related calls and now I get this message when I start DXKeeper. I don't have any internet connectivity issues. I tried rebooting; I also tried booting and selecting "Enable Safe Mode with Networking". I opened Windows Security > Firewall & network protection > Allow an app through firewall and verified that DXKeeper is listed as allowed to communicate through Windows Defender Firewall.

When I open DXKeeper a Windows command window opens with the following command:

C:\DXLab\Launcher>"C:\Program Files (x86)\TrustedQSL\tqsl.exe" -n   2>"C:\DXLab\DXKeeper\LotWNews.txt"

That command window hangs for a minute or two and then closes. It creates a new LotWNews.txt file in the DXKeeper directory each time I open DXKeeper but the file is empty. In that directory there is also a file "LotWResult.txt". The time stamp on that file is from early this morning when everything was working.

I've opened the DXKeeper>Config>QSL Config >LoTW tab and verified my LoTW user name and password are correct. If I hit "Run" in the bottom panel in that tab (the panel labeled TQSL 2.5.7) the TQSL window opens. From there I can log in to the LoTW site. In the DXKeeper>QSL tab, the "Check LoTW Queue" button in the "LotW operations" panel shows the LoTW queue is 1m.

Thanks for the great support. I know my problem will be solved shortly (this problem anyway).

73,
Andy - K0AF


TQSL is unable to contact LoTW

Andy - K0AF
 
Edited

When I open DXKeeper, after about a minute an error message pops up saying "TQSL is unable to contact LoTW". All was fine earlier this morning. I closed the Launcher for a couple work related calls and now I get this message when I start DXKeeper. I don't have any internet connectivity issues. I tried rebooting; I also tried booting and selecting "Enable Safe Mode with Networking". I opened Windows Security > Firewall & network protection > Allow an app through firewall and verified that DXKeeper is listed as allowed to communicate through Windows Defender Firewall.

When I open DXKeeper a Windows command window opens with the following command:

C:\DXLab\Launcher>"C:\Program Files (x86)\TrustedQSL\tqsl.exe" -n   2>"C:\DXLab\DXKeeper\LotWNews.txt"

That command window hangs for a minute or two and then closes. It creates a new LotWNews.txt file in the DXKeeper directory each time I open DXKeeper but the file is empty. In that directory there is also a file "LotWResult.txt". The time stamp on that file is from early this morning when everything was working.

I've opened the DXKeeper>Config>QSL Config >LoTW tab and verified my LoTW user name and password are correct. If I hit "Run" in the bottom panel in that tab (the panel labeled TQSL 2.5.7) the TQSL window opens. From there I can log in to the LoTW site. In the DXKeeper>QSL tab, the "Check LoTW Queue" button in the "LotW operations" panel shows the LoTW queue is 1m.

Thanks for the great support. I know my problem will be solved shortly (this problem anyway).

73,
Andy - K0AF


Re: Combining logs

Doug Grace
 

Thanks Dave, worked just fine but then again, you knew that. 73....
ve1dfg

On Wed, May 12, 2021 at 6:14 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I have several logs I want to combine into 1 log. How do I do that. Just leave a hint as to where I can find the answer. I looked in the online help files and did not find the answer.
+ Pick one of your logs to be the "survivor", and make a backup copy of this log file. Open each of the other log files, and export a "standard ADIF" file from each; if a log contains unique "my QTH" definitions, check the "Export QTH definitions" box on the Main window's "Export QSOs" tab before clicking the Start button. Then open the "survivor" log, and import each of the ADIF files you created.

     73,

            Dave, AA6YQ

--
Doug Grace
902-456-0506


Re: Combining logs

Dave AA6YQ
 

+ AA6YQ comments below
I have several logs I want to combine into 1 log. How do I do that. Just leave a hint as to where I can find the answer. I looked in the online help files and did not find the answer.
+ Pick one of your logs to be the "survivor", and make a backup copy of this log file. Open each of the other log files, and export a "standard ADIF" file from each; if a log contains unique "my QTH" definitions, check the "Export QTH definitions" box on the Main window's "Export QSOs" tab before clicking the Start button. Then open the "survivor" log, and import each of the ADIF files you created.

     73,

            Dave, AA6YQ


Re: Lat Lon options

Dave AA6YQ
 

+ AA6YQ comments below
Is there a way to have PropView and DXView recognize Decimal degrees as in 41.861544N as opposed to 41 51' 42.7"N?
Just faster is all, all my  mapping programs use decimal degrees.

+ No, but entering a grid square or just clicking on a location on DXView's World Map is sufficiently accurate for propagation forecasting, and faster than typing a lat/lon in either format.

       73,

              Dave, AA6YQ

9821 - 9840 of 211134