Date   
Re: DX Lab Launcher takes forever to launch

Dave AA6YQ
 

I added "PIP Anywhere" to

<http://www.dxlabsuite.com/dxlabwiki/ApplicationInteference>

Thanks Bruce and Mike!

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 9:24 PM
To: dxlab@...
Subject: Re: [dxlab] DX Lab Launcher takes forever to launch

Hello Mike:

It was a program called: PiP Anywher by TODO. I have no Idea what it is but as soon as I stopped it all whent back to normal. In fact Before I stopped it. I had the Blue Wait ball show up also about every 3 sec. That is also gone now.

Many thanks for the suggestions Mike.

Bruce N9BX 73



On 3/9/2018 3:52 PM, 'Mike Pagel' k9uw@... [dxlab] wrote:

Bruce, which start up program turned out to be the culprit? Others
might benefit from your discovery.

73,

Mike, K9UW

Amherst, WI

*From:* dxlab@... <dxlab@...>
*Sent:* Friday, March 9, 2018 2:51 PM
*To:* dxlab@...
*Subject:* Re: [dxlab] DX Lab Launcher takes forever to launch

thanks, it was one of the automatic start up programs that had
everything hosed up.

Bruce N9BX

Sent from my iPad


On Mar 9, 2018, at 7:33 AM, Brian Smithson n8wrl@...
<mailto:n8wrl@...> [dxlab] <dxlab@...
<mailto:dxlab@...>> wrote:

It is anti-malware or firewall issues:

http://www.dxlabsuite.com/dxlabwiki/ApplicationInteference

73

-Brian n8wrl

On Fri, Mar 9, 2018 at 8:25 AM, n9bx73@...
<mailto:n9bx73@...> [dxlab] <dxlab@...
<mailto:dxlab@...>> wrote:

No other apps are running. CPU is an I7 32 Gigs of Ram. Just
plain slow, I am hoping it is a compatability issue with win 10.

Bruce



------------------------------------
Posted by: Bruce Osterberg <n9bx73@...>
------------------------------------


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

Yahoo Groups Links




---
This email has been checked for viruses by AVG.
http://www.avg.com

Re: DXKeeper Refuses To Log Z60A

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 6:24 PM
To: dxlab@...
Subject: [dxlab] DXKeeper Refuses To Log Z60A

All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC Z6, code 522 is entered the the code field flashes red and will not complete the log.

The instructions for updating the DXCC database include invoking the Recompute function at the bottom of "Check Progress" tab of DXKeeper's Main window; have you done that?
73,

Dave, AA6YQ

Re: qso's from Feb 21st on LOTW

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 4:15 PM
To: dxlab@...
Subject: [dxlab] qso's from Feb 21st on LOTW

I made 4 q's on Feb 21st. They still show as U in DXKeeper, meaning uploaded but not confirmed as being in LOTW.

'U' means "Uploaded to LoTW, but not accepted by LoTW". The "Sync LOTW QSOs" function queries LoTW to report newly accepted QSOs, and updates logged QSOs accepted by LOTW.

If I highlight each q and right click, the menu offers an option to upload to LOTW, but each QSO says that it's duplicate info, they've already been uploaded. If I click update from LOTW on the same menu, it looks like each QSO made it to LOTW.
If I go to the LOTW website, it doesn't show anything for Feb 21st??? Any ideas on how to fix this?

Have you successfully submitted QSOs to LoTW from DXKeeper in the past, or is this your first attempt?
Do you have any LoTW "Callsign Certificates" besides the one you have for KG8DH?
73,

Dave, AA6YQ

Re: DXKeeper Refuses To Log Z60A

Robie
 

Per the Z60A QRZ.com page - 

CLARIFICATION OF THE Z60A LOTW UPLOAD TIMING

The complete Z60A log will be uploaded to LoTW approximately four weeks after the current activation. The current activation will end immediately following Kosovo's 10th independence anniversary celebrations on Sunday, February, 18 2018. The additional four-week window will allow for corrections and checking for potentially busted calls.
Robie - AJ4F







On Fri, Mar 9, 2018 at 8:37 PM, Danny Douglas n7dc@... [dxlab] <dxlab@...> wrote:
 

INTERESTING,  Have all the z6 QSOs been confirmed to lotw?  I have 5 bands worked, and not one match yet. I even worked three of them twice, and definitely got my call right, etc.  All on cw, so far. 

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On March 9, 2018 at 8:41 PM "'Bob Main' bobmain1@... [dxlab]" <dxlab@...> wrote:

 

Wish my Z6 QSOs were confirmed, but maybe they will be by July 4th.

73, Bob KB4CL

From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 8:33 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper Refuses To Log Z60A

All of my Z6 QSOs are already confirmed via LoTW and they show code 522 with no issues.

On 3/9/2018 6:23 PM, carbide_bill@... [dxlab] wrote:

All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC Z6, code 522 is entered the the code field flashes red and will not complete the log.

Is there an incorrect code in the database?

Thanks,

KD0NPT

[Non-text portions of this message have been removed]


 


Re: DXKeeper Refuses To Log Z60A

Danny Douglas
 

INTERESTING,  Have all the z6 QSOs been confirmed to lotw?  I have 5 bands worked, and not one match yet. I even worked three of them twice, and definitely got my call right, etc.  All on cw, so far. 

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On March 9, 2018 at 8:41 PM "'Bob Main' bobmain1@... [dxlab]" <dxlab@...> wrote:

 

Wish my Z6 QSOs were confirmed, but maybe they will be by July 4th.

73, Bob KB4CL

From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 8:33 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper Refuses To Log Z60A

All of my Z6 QSOs are already confirmed via LoTW and they show code 522 with no issues.

On 3/9/2018 6:23 PM, carbide_bill@... [dxlab] wrote:

All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC Z6, code 522 is entered the the code field flashes red and will not complete the log.

Is there an incorrect code in the database?

Thanks,

KD0NPT

[Non-text portions of this message have been removed]


 

Re: DX Lab Launcher takes forever to launch

Bruce N9BX
 

Hello Mike:

It was a program called: PiP Anywher by TODO.  I have no Idea what it is but as soon as I stopped it all whent back to normal. In fact Before I stopped it.  I had the Blue Wait ball show up also about every 3 sec.  That is also gone now.

Many thanks for the suggestions Mike.

Bruce N9BX 73

On 3/9/2018 3:52 PM, 'Mike Pagel' k9uw@... [dxlab] wrote:

Bruce, which start up program turned out to be the culprit?  Others might benefit from your discovery.

73,

Mike, K9UW

Amherst, WI

*From:* dxlab@... <dxlab@...>
*Sent:* Friday, March 9, 2018 2:51 PM
*To:* dxlab@...
*Subject:* Re: [dxlab] DX Lab Launcher takes forever to launch

thanks, it was one of the automatic start up programs that had everything hosed up.

Bruce N9BX

Sent from my iPad


On Mar 9, 2018, at 7:33 AM, Brian Smithson n8wrl@... <mailto:n8wrl@...> [dxlab] <dxlab@... <mailto:dxlab@...>> wrote:

It is anti-malware or firewall issues:

http://www.dxlabsuite.com/dxlabwiki/ApplicationInteference

73

-Brian n8wrl

On Fri, Mar 9, 2018 at 8:25 AM, n9bx73@...
<mailto:n9bx73@...> [dxlab] <dxlab@...
<mailto:dxlab@...>> wrote:

No other apps are running.  CPU is an I7 32 Gigs of Ram.  Just
plain slow, I am hoping it is a compatability issue with win 10.

Bruce

Re: DXKeeper Refuses To Log Z60A

Bob Main
 

Wish my Z6 QSOs were confirmed, but maybe they will be by July 4th.



73, Bob KB4CL



From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 09, 2018 8:33 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper Refuses To Log Z60A





All of my Z6 QSOs are already confirmed via LoTW and they show code 522 with no issues.



On 3/9/2018 6:23 PM, carbide_bill@... [dxlab] wrote:



All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC Z6, code 522 is entered the the code field flashes red and will not complete the log.

Is there an incorrect code in the database?

Thanks,

KD0NPT









[Non-text portions of this message have been removed]

Re: DXKeeper Refuses To Log Z60A

Sidney Shusterman
 

All of my Z6 QSOs are already confirmed via LoTW and they show code 522 with no issues.


On 3/9/2018 6:23 PM, carbide_bill@... [dxlab] wrote:
 

All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC  Z6,  code 522 is entered the the code field flashes red and will not complete the log.

Is there an incorrect code in the database?

Thanks,

KD0NPT



DXKeeper Refuses To Log Z60A

Bill Erixon
 

All databases are up to date but when I try to log Z60A in DXKeeper which is now in the entity pulldown list as Republic of Kosovo and DXCC  Z6,  code 522 is entered the the code field flashes red and will not complete the log.

Is there an incorrect code in the database?

Thanks,

KD0NPT


Re: DX Lab Launcher takes forever to launch

Mike, K9UW
 

Bruce, which start up program turned out to be the culprit?  Others might benefit from your discovery.

 

73,

 

Mike, K9UW

Amherst, WI

 

From: dxlab@...
Sent: Friday, March 9, 2018 2:51 PM
To: dxlab@...
Subject: Re: [dxlab] DX Lab Launcher takes forever to launch

 

 

thanks, it was one of the automatic start up programs that had everything hosed up.

Bruce N9BX 


On Mar 9, 2018, at 7:33 AM, Brian Smithson n8wrl@... [dxlab] <dxlab@...> wrote:

 

It is anti-malware or firewall issues:

 

 

73

 

-Brian n8wrl

 

On Fri, Mar 9, 2018 at 8:25 AM, n9bx73@... [dxlab] <dxlab@...> wrote:

 

No other apps are running.  CPU is an I7 32 Gigs of Ram.  Just plain slow, I am hoping it is a compatability issue with win 10.

Bruce

 

qso's from Feb 21st on LOTW

Kg8dh
 

I made 4 q's on Feb 21st.  They still show as U in DXKeeper, meaning uploaded but not confirmed as being in LOTW.  If I highlight each q and right click, the menu offers an option to upload to LOTW, but each QSO says that it's duplicate info, they've already been uploaded.  If I click update from LOTW on the same menu, it looks like each QSO made it to LOTW. 
If I go to the LOTW website, it doesn't show anything for Feb 21st???  Any ideas on how to fix this?

Thanks
KG8DH

Re: DX Lab Launcher takes forever to launch

Bruce N9BX
 

thanks, it was one of the automatic start up programs that had everything hosed up.
Bruce N9BX 


On Mar 9, 2018, at 7:33 AM, Brian Smithson n8wrl@... [dxlab] <dxlab@...> wrote:

 

It is anti-malware or firewall issues:


73

-Brian n8wrl

On Fri, Mar 9, 2018 at 8:25 AM, n9bx73@... [dxlab] <dxlab@...> wrote:
 

No other apps are running.  CPU is an I7 32 Gigs of Ram.  Just plain slow, I am hoping it is a compatability issue with win 10.

Bruce


Re: Spotcollector (SC) color coding question

cwf172@...
 

Thanks for the assist...I will work on this!

Love DXLabs!

Re: LoTW Confirmation = Z

ve3ki
 

The Z in LotW cfm simply means that the other station included their CQZ in the station location they used to sign the QSO for upload. Period. Nothing else.

Those are the only LotW QSOs you can use in an award application. If a station did not include their CQZ in their upload, so that there is no Z in LotW cfm for that QSO, then that QSO is no good for WAZ. It may be good for DXCC and possibly other awards, but not for WAZ.

If you had 50,000 QSOs with the same zone on the same band and mode, and all of them included their CQZ in their station location, they would all be marked with a Z, regardless of the fact that you might not need any of them for an award. Meanwhile, if you have only one QSO with another zone, but the other station did not include their CQ zone when they uploaded that QSO, you won't be able to use that LotW confirmation even though it might be one you need.

73,
Rich VE3KI



---In dxlab@..., <bobmain1@...> wrote :

I understand that LoTW doesn't know what I have credit for, but DXKeeper
does. But never mind I will continue doing what I have been doing and if I
just happen to need a zone that has been confirmed by LoTW then I will use
no matter what it set to what. Didn't mean for it to be that confusing to
understand what I am asking.



Bob



From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, March 08, 2018 4:44 PM
To: dxlab@...
Subject: RE: [dxlab] LoTW Confirmation = Z





>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, March 08, 2018 3:50 PM
To: dxlab@...
Subject: [dxlab] LoTW Confirmation = Z

I THINK that if LoTW Confirmation = Z that means that QSL can be used to
confirm that zone for that band/mode is that correct? Got
an interesting problem then because I have 11 with that set to Z but I don't
need any of them. All those zones have already been
verified by CQ and logged into DXKeeper. Seems to me that if the zone is
already verified by CQ then I don't need LoTW Confirmation
set to Z because it is of no use to me.

>>>LoTW doesn't know which zones, zone-bands, zone-modes, or zone-band-modes
you've already submitted to CQ for award credit. It
informs you as to whether your LoTW confirmation "counts" for WAZ,
independent of whether you personally "need" the confirmation.
It also informs you of whether LoTW confirmations count for WAS and VUCC,
whether or not you need them.

73,

Dave, AA6YQ





[Non-text portions of this message have been removed]

Re: DX Lab Launcher takes forever to load

Joe Subich, W4TV
 

As Dave often suggests, try booting into "Safe mode with networking"
and then starting DXLab Suite. If the behavior is not present in
safe mode, something being loaded at start-up is interfering with
DXLab Suite. You can then work through the possibilities to find out
what is interfering - generally some misconfigured anti-malware
application.

73,

... Joe, W4TV

On 3/9/2018 8:23 AM, n9bx73@... [dxlab] wrote:
When I click on the icon for dxLab launcher it takes about 1.3 minutes to load. And when it does come up, each of the components like DXkeeper, ETC will say, taking too much time to load or over 160 seconds, and then they will come up. But when they do come up, you cants use them right away, you must wait for another minute, If you try to close them, you will get the count down indicator starting at 12 and finally to 1 before the program shuts down. Running Windows 10 with all the latest updates. Bruce N9BX 73

Re: Add Needed

Scott Stembaugh
 

Thanks, Joe!  That is likely it since these are a combination of OQRS requests and QSOs that were imported from DXBase.  I don't think we have it configured to automatically set QSL RCVD to 'R'.


vy 73,
--scott

On Fri, Mar 9, 2018 at 7:59 AM, 'Joe Subich, W4TV' lists@... [dxlab] <dxlab@...> wrote:
 


> When we do an 'Add Needed' for QSLs (set to print labels), the Queue
> is populated with QSOs that have already been manually marked with
> QSL Sent = Y and a QSL Sent date.

When the QSOs were *manually set* for QSL Sent = 'Y' was QSL RCVD set
to 'R'?

If QSL RCVD is not set to 'R', add needed will request the card (again).
I ran into this with OQRS requests ... since labels were never printed
the log was never automatically updated to set QSO RCVD = 'R'.

73,

.... Joe, W4TV



On 3/9/2018 7:49 AM, Scott Stembaugh radio.n9ljx@... [dxlab] wrote:
> i am helping a friend get settled in with DXLabs. Last night we noticed an
> anomaly I can't explain.
>
> When we do an 'Add Needed' for QSLs (set to print labels), the Queue is
> populated with QSOs that have already been manually marked with QSL Sent =
> Y and a QSL Sent date. QSL Aging had not been set up. And some of these
> were recently sent (last month or so). They have not been confirmed yet,
> but being so 'young' I would not expect to seem them still being added to
> the QSL queue. I do not see this behavior in my log.
>
> where should I look for an explanation?
>
> thanks,
> --scott
> ------
> Scott Stembaugh - N9LJX
> radio.n9ljx@...
> http://sites.google.com/site/radion9ljx
>


DX Lab Launcher takes forever to load

Bruce N9BX
 

When I click on the icon for dxLab launcher it takes about 1.3 minutes to load.  And when it does come up, each of the components like DXkeeper, ETC will say, taking too much time to load or over 160 seconds, and then they will come up.  But when they do come up, you cants use them right away, you must wait for another minute,  If you try to close them, you will get the count down indicator starting at 12 and finally to 1 before the program shuts down.  Running Windows 10 with all the latest updates. Bruce N9BX 73

Re: DX Lab Launcher takes forever to launch

Brian Smithson <n8wrl@...>
 

It is anti-malware or firewall issues:


73

-Brian n8wrl

On Fri, Mar 9, 2018 at 8:25 AM, n9bx73@... [dxlab] <dxlab@...> wrote:
 

No other apps are running.  CPU is an I7 32 Gigs of Ram.  Just plain slow, I am hoping it is a compatability issue with win 10.

Bruce


Re: DX Lab Launcher takes forever to launch

Bruce N9BX
 

No other apps are running.  CPU is an I7 32 Gigs of Ram.  Just plain slow, I am hoping it is a compatability issue with win 10.
Bruce

Re: Add Needed

Joe Subich, W4TV
 

When we do an 'Add Needed' for QSLs (set to print labels), the Queue
is populated with QSOs that have already been manually marked with
QSL Sent = Y and a QSL Sent date.
When the QSOs were *manually set* for QSL Sent = 'Y' was QSL RCVD set
to 'R'?

If QSL RCVD is not set to 'R', add needed will request the card (again).
I ran into this with OQRS requests ... since labels were never printed
the log was never automatically updated to set QSO RCVD = 'R'.

73,

... Joe, W4TV



On 3/9/2018 7:49 AM, Scott Stembaugh radio.n9ljx@... [dxlab] wrote:
i am helping a friend get settled in with DXLabs. Last night we noticed an
anomaly I can't explain.
When we do an 'Add Needed' for QSLs (set to print labels), the Queue is
populated with QSOs that have already been manually marked with QSL Sent =
Y and a QSL Sent date. QSL Aging had not been set up. And some of these
were recently sent (last month or so). They have not been confirmed yet,
but being so 'young' I would not expect to seem them still being added to
the QSL queue. I do not see this behavior in my log.
where should I look for an explanation?
thanks,
--scott
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx