¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

DXKeeper problem with CWSkimmer


 

Hello,?
I using for a long time DXLab with my CWSkimmer? with Com0Com software.
Neve has any problem
Till last? 2 weeks When I start te launcher and also CWSkimmer than it take more than 40 sec if? dxkeeper is start.
when I search a call in DXKeeper it takes 30 sec.
If I close CWSkimmer than it is 7 sec and the call is found in DXKeeper.
Are there more users of DXLab and CWSkimmer who have problems with this?
I'm know that? it is easy to say than CWSkimmer is not good but i have Alex also send a mail with this same issue.
but I hope there is? some one who have a idea? to fix this problem?
Using Win10 64 bite?
16 GB Ram I7 Proccesor
Much enough i.m.o to work with dxlab
When I try is with a other program FLDigi, MixW cwskimmer just works fine.
So there is a connection between CWSkimmer and DXLab that is bad.

Tnx?
Rien, PA7RA?


 

Rien

I am not sure I understand your problem.? ?I have run DXLab with CW skimmer for many years.

Is your problem the time it takes for the programs to start or clicking on a call in CW Skimmer and having DXKeeper recognize the call.

What program do you use to link CW skimmer and DX keeper

Don
WB6BEE


 

Hello Don
?
thanks for the reply
I have CWSkimmer separate from DXLab running here
I also have the Microkeyer here with Cat 1 for Commander
and Cat 2 for CWSkimmer
Now my problem
is that if CWSKimmer turns and I want to click on a spot in the spot collector it takes a long time before the spot goes to my capture screen
if I close CWSkimmer this goes much faster.
Similarly when I look up a Call in DXKeeper with CWSkimmer roaring in the background, this takes more than 30 seconds before DXKeeper comes up with the call and has finished searching.
If I close CWSkimmer this is 7 seconds at most
I hope it is so clearer for you Don sorry for my bad english this is also done in Google translator.
But how did you connect CWSkimmer to DXLab?
for me it is not connected but I have been working this way for years
So that's just so strange.
? Thanks again
?
73 'Rien, PA7RA


 

+ AA6YQ comments below

thanks for the reply
I have CWSkimmer separate from DXLab running here
I also have the Microkeyer here with Cat 1 for Commander
and Cat 2 for CWSkimmer
Now my problem
is that if CWSKimmer turns and I want to click on a spot in the spot collector it takes a long time before the spot goes to my capture screen
if I close CWSkimmer this goes much faster.
Similarly when I look up a Call in DXKeeper with CWSkimmer roaring in the background, this takes more than 30 seconds before DXKeeper comes up with the call and has finished searching.
If I close CWSkimmer this is 7 seconds at most
I hope it is so clearer for you Don sorry for my bad english this is also done in Google translator.
But how did you connect CWSkimmer to DXLab?
for me it is not connected but I have been working this way for years
So that's just so strange.

+ When two applications whose interoperation has been smooth suddenly begin taking tens of seconds to communicate, the most likely cause is a misconfigured or incompetent anti-malware or firewall application - particularly if your anti-malware or firewall applications are allowed to update themselves at will.

<>

73,

Dave, AA6YQ


 

Rien

I have CW skimmer linked to the K3 using Com-0-Com.? ? ?I use CWSkimmer to DXKeeper, which allows me to click on a signal in CW skimmer and it will automatically populate my DXK capture window.? ?



I think Dave is right on a firewall issue.

Don
WB6BEE


 

Okay I work with a NOD32 virus scanner but no idea how to handle this
Does anyone have an idea how I can see if it is indeed my firewal
sorry but am really a computer dummy
so please provide more info about how I can best approach
thank you in advance


 

+ AA6YQ comments below

Okay I work with a NOD32 virus scanner but no idea how to handle this
Does anyone have an idea how I can see if it is indeed my firewal
sorry but am really a computer dummy
so please provide more info about how I can best approach
thank you in advance

+ My advice is to contact NOD32 Support.

73,

Dave, AA6YQ