Date   

Re: Flaky behavior since last Windows update

Matt Foster
 

Here's the beginning of the debug log when starting Launcher immediately after a reboot. Note the roughly 1.5 minute pause from 18:49:31 to 18:50:59

2020-11-08 18:49:31     > DXLabLauncher version 2.1.4
2020-11-08 18:49:31     > App.Path          : C:\DXLab\Launcher
2020-11-08 18:49:31     > App.exe           : DXLabLauncher
2020-11-08 18:49:31     > Module            : C:\DXLab\Launcher\DXLabLauncher.exe
2020-11-08 18:49:31     > Operating System  : Windows 10 Enterprise (64-bit) build 19041
2020-11-08 18:49:31     > Locale ID         : 1033 (0x409)
2020-11-08 18:49:31     > ANSI CodePage     : 1252
2020-11-08 18:49:31     > OEM CodePage      : 437
2020-11-08 18:49:31     > Country           : United States
2020-11-08 18:49:31     > Language          : English
2020-11-08 18:49:31     > DecimalSeparator  : .
2020-11-08 18:49:31     > ThousandSeparator : ,
2020-11-08 18:49:31     > DXLab Apps        : 
2020-11-08 18:50:59     > Monitors          : 1
2020-11-08 18:50:59     > Monitor 1
2020-11-08 18:50:59     >    width          : 2560
2020-11-08 18:50:59     >    height         : 1440
2020-11-08 18:50:59     >    dimensions     : (0, 0)-(2560, 1440)
2020-11-08 18:50:59.512 > GetLongSetting,    Section = Windows, Key = frmConfigureLeft, Result = 1185
2020-11-08 18:50:59.528 > GetLongSetting,    Section = Windows, Key = frmConfigureTop, Result = 1215
2020-11-08 18:50:59.528 > GetLongSetting,    Section = Windows, Key = frmConfigureWidth, Result = 12045
2020-11-08 18:50:59.528 > GetLongSetting,    Section = Windows, Key = frmConfigureHeight, Result = 7920
2020-11-08 18:50:59.528 > GetIntegerSetting, Section = Windows, Key = frmConfigureWindowstate, Result = 0

I then exited Launcher (didn't start any other applications), made sure it had indeed exited by checking the Task Manager, and launched it again. This time Launcher starts and shows its GUI almost instantly and the log looks normal (i.e. no pause).

2020-11-08 18:53:27     > DXLabLauncher version 2.1.4
2020-11-08 18:53:27     > App.Path          : C:\DXLab\Launcher
2020-11-08 18:53:27     > App.exe           : DXLabLauncher
2020-11-08 18:53:27     > Module            : C:\DXLab\Launcher\DXLabLauncher.exe
2020-11-08 18:53:27     > Operating System  : Windows 10 Enterprise (64-bit) build 19041
2020-11-08 18:53:27     > Locale ID         : 1033 (0x409)
2020-11-08 18:53:27     > ANSI CodePage     : 1252
2020-11-08 18:53:27     > OEM CodePage      : 437
2020-11-08 18:53:27     > Country           : United States
2020-11-08 18:53:27     > Language          : English
2020-11-08 18:53:27     > DecimalSeparator  : .
2020-11-08 18:53:27     > ThousandSeparator : ,
2020-11-08 18:53:27     > DXLab Apps        : 
2020-11-08 18:53:27     > Monitors          : 1
2020-11-08 18:53:27     > Monitor 1
2020-11-08 18:53:27     >    width          : 2560
2020-11-08 18:53:27     >    height         : 1440
2020-11-08 18:53:27     >    dimensions     : (0, 0)-(2560, 1440)
2020-11-08 18:53:27.386 > GetLongSetting,    Section = Windows, Key = frmConfigureLeft, Result = 1185
2020-11-08 18:53:27.386 > GetLongSetting,    Section = Windows, Key = frmConfigureTop, Result = 1215
2020-11-08 18:53:27.401 > GetLongSetting,    Section = Windows, Key = frmConfigureWidth, Result = 12045
2020-11-08 18:53:27.401 > GetLongSetting,    Section = Windows, Key = frmConfigureHeight, Result = 7920
2020-11-08 18:53:27.401 > GetIntegerSetting, Section = Windows, Key = frmConfigureWindowstate, Result = 0

Any suggestions would be appreciated!

--
73, Matt, N0EYE


Re: GrayLine

Dave AA6YQ
 

+ AA6YQ comments below
I found it, it's in the docs:

+ Writing this article led me to  ask the question "what would the plot of all locations with which there's never a grayline opening from my QTH look like?" 

+ I know one way to answer this question: plot the solar terminator from my QTH every minute over the course of 365 days, and see what's left uncolored, but I haven't gotten around to doing so.

+ Anyone know a more direct way to answer this question?

         73,

               Dave, AA6YQ


Re: AJA and JCC Award tracking

Joe Subich, W4TV
 

(hopefully Dayton will go ahead next year).
Not if the incoming administration has its way.

OTOH, Trudeu is not about to open the boarders anyway. We have not
been able to see our son who lives in Montreal for almost a year
now it looks like it will be another year.

73,

... Joe, W4TV


On 2020-11-08 12:29 PM, Ellam, Timothy St. J. wrote:
Rob
I agree the certificates are nice. Yes, I will have to dig up the cards at some point (or request a paper card) but having the info in DXkeeper will make it easier. JARL is usually at Dayton so that is a good time to apply (hopefully Dayton will go ahead next year).
73
Tim VE6SH


Re: AJA and JCC Award tracking

Ellam, Timothy St. J.
 

Rob

I agree the certificates are nice. Yes, I will have to dig up the cards at some point (or request a paper card) but having the info in DXkeeper will make it easier. JARL is usually at Dayton so that is a good time to apply (hopefully Dayton will go ahead next year).

73

Tim VE6SH


Re: AJA and JCC Award tracking

Ellam, Timothy St. J.
 

Thanks Dave

I missed the Callbook lookup section in the Wiki. Yes, it is not always possible to determine the information from the QRZ entries.

73

Tim VE6SH


Flaky behavior since last Windows update

Matt Foster
 

My system recently installed a batch of Windows updates. I have Win 10 Pro 2004. It seems since this latest batch of updates that my DX Labs Suite is behaving "oddly". For example, after a reboot the DX Labs Launcher takes dozens of seconds (perhaps a minute or so) to show its GUI on the screen. I can exit and restart the Launcher, and it posts immediately. Then this morning, I found that Commander was not talking to my IC-7300.

It seems to me that the issues started with these latest Windows updates, but maybe that's a false impression. I'm wondering if anyone else has noticed issues that started recently.

--
73, Matt, N0EYE


IOTA handling

Salvatore Besso
 

hello,

what is the situation with IOTA handling in DXLab suite? I'm referring in particular to the feature (is it the correct term?) introduced by IOTA-World which considers a QSO not confirmed by any means (card or LotW) to be valid for the IOTA award if there is a ClubLog match.

I ask this because I have encountered a couple of difficulties:

1. I have found a certain number of pending QSOs in IOTA-World that have never been confirmed by any means, card or LotW, but have a ClubLog match. These QSOs, of course, will never appear into a submission prepared with DXKeeper.

2. Some QSOs that are confirmed by card and/or LotW, are not added to the pending QSOs because the operation has not been accepted yet, and I think that it would be less than useful to add them manually. In this case instead, it would be useful that a mean exists that allows to know if an operation has not been accepted yet so it would be possible to work that reference again. Actually, a confirmed QSO is no longer considered needed, but it is possible that the operation is invalid, making that reference needed again.

I know that it's probably a matter of communication with IOTA-World to get these data and I don't even know if these data are fully available, but I'd like to know if there are alternatives until there will be full interoperation between DXLab and IOTA-World, or if some tricks already exist that I don't know of.

Thank you.

73 de
Salvatore (I4FYV)


Re: GrayLine

Hasan Schiers N0AN
 

On Sun, Nov 8, 2020 at 7:34 AM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:
Certainly, but while playing around with the feature, how do I test it. I can't sit around entering 300 different countries hoping one will show Grayline. 

I was looking for something more efficient to examine potential grayline passes, as it were.

There must be a better way .   :-)

73,
Hasan


On Sun, Nov 8, 2020 at 6:40 AM Julio Peralta via groups.io <jperalta4=verizon.net@groups.io> wrote:

Could it be that the country you have selected doesn’t have grey line propagation useful for your location?

 

Julio, W4HY

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Sunday, November 08, 2020 6:07 AM
To: DXLab@groups.io
Subject: [DXLab] GrayLine

 

I've been playing with DXView's Sunrise/Sunset table which is wonderful for looking at potential 160m openings (and 80/40) and I saw the choice available for Grayline...but every time I choose it, after having input a callsign that shows Sunrise/Sunset, the list of SR/SS goes away (as it should) but the Grayline is blank.

 

How do I make use of the Grayline feature in non-realtime? 

(or even real time for that matter)

73, N0AN

Hasan


Re: GrayLine

Hasan Schiers N0AN
 

Certainly, but while playing around with the feature, how do I test it. I can't sit around entering 300 different countries hoping one will show Grayline. 

I was looking for something more efficient to examine potential grayline passes, as it were.

There must be a better way .   :-)

73,
Hasan


On Sun, Nov 8, 2020 at 6:40 AM Julio Peralta via groups.io <jperalta4=verizon.net@groups.io> wrote:

Could it be that the country you have selected doesn’t have grey line propagation useful for your location?

 

Julio, W4HY

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Sunday, November 08, 2020 6:07 AM
To: DXLab@groups.io
Subject: [DXLab] GrayLine

 

I've been playing with DXView's Sunrise/Sunset table which is wonderful for looking at potential 160m openings (and 80/40) and I saw the choice available for Grayline...but every time I choose it, after having input a callsign that shows Sunrise/Sunset, the list of SR/SS goes away (as it should) but the Grayline is blank.

 

How do I make use of the Grayline feature in non-realtime? 

(or even real time for that matter)

73, N0AN

Hasan


Re: GrayLine

Julio Peralta
 

Could it be that the country you have selected doesn’t have grey line propagation useful for your location?

 

Julio, W4HY

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Sunday, November 08, 2020 6:07 AM
To: DXLab@groups.io
Subject: [DXLab] GrayLine

 

I've been playing with DXView's Sunrise/Sunset table which is wonderful for looking at potential 160m openings (and 80/40) and I saw the choice available for Grayline...but every time I choose it, after having input a callsign that shows Sunrise/Sunset, the list of SR/SS goes away (as it should) but the Grayline is blank.

 

How do I make use of the Grayline feature in non-realtime? 

(or even real time for that matter)

73, N0AN

Hasan


GrayLine

Hasan Schiers N0AN
 

I've been playing with DXView's Sunrise/Sunset table which is wonderful for looking at potential 160m openings (and 80/40) and I saw the choice available for Grayline...but every time I choose it, after having input a callsign that shows Sunrise/Sunset, the list of SR/SS goes away (as it should) but the Grayline is blank.

How do I make use of the Grayline feature in non-realtime? 
(or even real time for that matter)
73, N0AN
Hasan


Re: Displaying Special Callsign Tags in Capture Window

Dave AA6YQ
 

+ AA6YQ comments below

You also need to ensure the Capture window is large enough to show the "comments" field.

+ Good point, Don! I forgot that Special Callsign Tags are recorded in the QSO's Comments item if the "Log Special Callsign Tags" option is enabled at the top of DXKeeper's Configuration window's General tab. WinWarbler provides a similar option on its Configuration window's Log tab.

73,

Dave, AA6YQ


Re: AJA and JCC Award tracking

AE7AP
 

Tim:
Note that the JARL does not accept LOTW confirmations for their awards.  They require that you possess a QSL card or an EQSL card.  I have applied for a few of their awards - they are fun to chase & the certificates are nice also.  I went through my cards & revised DXKeeper to match.  It took a while, but it was also interesting.  Good luck!

73,
Rob - AE7AP


Re: AJA and JCC Award tracking

Dave AA6YQ
 

+ AA6YQ comments below
I have thousands of JA contacts in DXkeeper. Many date back to the 80s/90s and were confirmed by paper cards. 

After reviewing the documentation I understand that JA prefectures and Cities/Guns have to be added manually to DXkeeper unless the QSO is confirmed on LOTW and the JA operator has added his/her prefecture and city to their details when they register with LOTW. In the latter case the prefecture and city are filled in at the time the QSO is confirmed on LOTW and the DXkeeper is synced to your LOTW account. DXkeeper can then scan your log and provided a current list of confirmed and unconfirmed AJA and JCC totals. 

I think I have that right. The only way to update the non-LOTW confirmations is to review each entry and add the details manually? 
+ You can update your JA QSOs with a callbook lookup - if the callbook contains the desired information. I checked a few JA callsigns in QRZ.com, but did not see prefectures.
Many of the JA Qs in my log do not have address information. I can update each JA entry by doing a CBA lookup (appreciating the amateur may have moved since the Q took place) or checking the paper cards (if they can be located) and then adding the prefecture/city information manually. 

Is there any way to do a batch update of all JA Qs to add the current CBA information? It appears not, but I thought I would ask.

+ In the Filter panel at the bottom of the Main window's "Log QSOs", type JA in the textbox and then click the DXCC button to filter your Log Page Display to contain your QSOs with Japanese stations. Then depress the ALT key while clicking the CBA button. See

<https://www.dxlabsuite.com/dxlabwiki/CallbookLookup>

      73,

              Dave, AA6YQ

 


Re: Slow Start!

Dave AA6YQ
 

+ AA6YQ comments below
Maybe more people are experiencing this problem?
+ Yes, something like this is reported here an average of once each week. It's usually the result of a misconfigured or incompetent anti-malware application. See

<https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference>
 
Since this week it takes more than 2 minutes for the launcher to start all applications
This is only the first time after that it just works fast.
But it strikes me.

 
and since a few days I have when I make a qso that I log in the capture when I click on log that I get a pop up window with the following text.
Upload QSO to Club Log:
of course I know that if I turn off clublog this is no longer there but I like it if the qso is logged directly in Clublog but I don't have to see this window every time
can I turn this off and where can I do this?
+ No, you can't prevent the display of that window.

      73,

             Dave, AA6YQ


AJA and JCC Award tracking

Ellam, Timothy St. J.
 

Hello

I have thousands of JA contacts in DXkeeper. Many date back to the 80s/90s and were confirmed by paper cards. 

After reviewing the documentation I understand that JA prefectures and Cities/Guns have to be added manually to DXkeeper unless the QSO is confirmed on LOTW and the JA operator has added his/her prefecture and city to their details when they register with LOTW. In the latter case the prefecture and city are filled in at the time the QSO is confirmed on LOTW and the DXkeeper is synced to your LOTW account. DXkeeper can then scan your log and provided a current list of confirmed and unconfirmed AJA and JCC totals. 

I think I have that right. The only way to update the non-LOTW confirmations is to review each entry and add the details manually? 

Many of the JA Qs in my log do not have address information. I can update each JA entry by doing a CBA lookup (appreciating the amateur may have moved since the Q took place) or checking the paper cards (if they can be located) and then adding the prefecture/city information manually. 

Is there any way to do a batch update of all JA Qs to add the current CBA information? It appears not, but I thought I would ask.

Thanks and 73

Tim VE6SH


Re: DXKeeper's scripts

Salvatore Besso
 

Dave,

There is no function that aborts script execution.
ok, maybe in a future version...

73 de
Salvatore (I4FYV)


Re: Slow Start!

Norm_W4QN
 

Have you "Pruned" you SC database?

Check Config, and Size Control 

See attached image of my setting

Norm W4QN




--
Norm_W4QN


Re: Displaying Special Callsign Tags in Capture Window

wb6bee
 

You also need to ensure the Capture window is large enough to show the "comments" field.    

Don
WB6BEE


Re: Slow Start!

John, G4DRS <g4drs@...>
 

Rien, I have seen this, too.
--
John
G4DRS

4041 - 4060 of 201231