Re: DXkeeper "Look-Up" is slowed.....Error Logs attached
Pete Smith
Mine is the same. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your favorite "retail" DX cluster. On 4/10/2020 9:54 AM, Gary Smetana
wrote:
|
||
|
||
Re: RBN as a propagation check
Pete Smith
Hi Chuck - I attempt to do user support for the RBN, and would like to help. What you need to do is to connect to a "retail" DX Cluster and use that cluster software's command set to filter. Your story suggests that you may be connected to one of our relay servers, which have no filtering (they're stripped down for speed). Alternatively, you can
go on the RBN web site and tell it only to display spots of your
call. I think that's how most people do what you want. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your favorite "retail" DX cluster. On 4/10/2020 9:58 AM, Chuck, WS1L
wrote:
|
||
|
||
How to search all Q's for a particular band
I know there’s an easy way to do this: how do I search
DXKeeper for all QSO’s, say on 6M?
Mike W4UM
|
||
|
||
Re: DXkeeper "Look-Up" is slowed.....Error Logs attached
Dave AA6YQ
+ AA6YQ comments below On Fri, Apr 10, 2020 at 09:54 AM, Gary Smetana wrote:
+ Reboot Windows into "Safe Mode with Networking", and then start DXKeeper. Any change in performance? 73,
|
||
|
||
Re: Infected file for Commander 14.5.5 update?
Jacob Derenne
I use to use AVG, but always missed something, all my ham software is on separate drive and flagged for defender to accept and once a month I run rogue killer off a usb thumb drive, never a issue here with viruses or such on my system
W9BLI Jake
Sent from Mail for Windows 10
From: neil_zampella
Sent: Friday, April 10, 2020 12:33 PM To: DXLab@groups.io Subject: Re: [DXLab] Infected file for Commander 14.5.5 update?
I've been using it for over 20 years ... AVG Internet Security. On 4/10/2020 12:42 PM, w6de wrote:
|
||
|
||
Re: Infected file for Commander 14.5.5 update?
neil_zampella
I've been using it for over 20 years ... AVG Internet Security.
On 4/10/2020 12:42 PM, w6de wrote:
|
||
|
||
Re: Import trouble, unexpected "," in County field
Dave AA6YQ
+ AA6YQ comments below On Fri, Apr 10, 2020 at 07:39 AM, Martin Sole wrote: Many thanks. I think I can work some Excel trickery to combine the 2 columns. + You can definitely do that with Excel. I suppose that is specified in the ADIF information, I should read more :) + Correct: http://adif.org.uk/310/ADIF_310.htm#Sponsor_Defined_Code_Format 73,
|
||
|
||
DXkeeper "Look-Up" is slowed.....Error Logs attached
Gary Smetana
Hi Dave,
A Dell "Premium Support Technician" resolved issues with my desktop PC, & did the latest Windows Updates.
Since then....."Look-up" in DXkeeper, to scroll between QSO's...is slowed a lot Not instantaneous, as before. The hourglass shimmers for 4-5 seconds.
I've created the Error Logs below.
Arranged as: DX Launcher / DXkeeper / DXview
3 MB.?!
What Next Steps do you recommend?
73,
Gary W1EBM
|
||
|
||
Re: Infected file for Commander 14.5.5 update?
w6de
Neil, what virus detection program do you use. I like how you describe it works.
Dave, w6de
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of neil_zampella
Sent: 10 April, 2020 02:45 To: DXLab@groups.io Subject: Re: [DXLab] Infected file for Commander 14.5.5 update?
There is no trojan or virus in any DXLab executable. Just as there is no virus or trojan in other ham radio programs like JTAlert, WSJT-X, and many others that get 'triggered' due to some algorithm only known to Microsoft. I have never had a problem with any DXLab program, nor with the others I mentioned. On 4/9/2020 8:10 PM, Jack Brabham - KZ5A wrote:
|
||
|
||
Re: Upgrade DX Keeper from 7.1.9 to 15.4.9
Jim McPhee
Great, Greg. Glad that worked for you too!
-- Jim McPhee Placitas, NM W5ABA
|
||
|
||
Re: Upgrade DX Keeper from 7.1.9 to 15.4.9
KE9UR
that worked Jim. Thank You Greg KE9UR
On Fri, Apr 10, 2020 at 9:51 AM Jim McPhee <jmcphee@...> wrote: I had a similar problem yesterday. In my case, it was Defender quarantining dxkeeper.exe. Every time I went into the dxkeeper folder, made a copy of the most recent dxkeeper executable (that was in the folder), and renamed it dxkeeper.exe, Defender would quarantine it. When I attempted to update to the newest version from Launcher's Config, I would get the same "file is in use or dxkeeper.exe is write protected" message. I finally caught on and told Defender to exclude the entire DXLAB folder from scans. That fixed the problem.
|
||
|
||
Re: RBN as a propagation check
If you’re connected to a node that sends spots from Skimmers:
Send TEST WS1L WS1L TEST on CW. When you see a spot for your call in SpotCollector, right click on it and select Display spots of WS1L near (freq) in CW.
A window will open listing spots for you from all the CW skimmers that have received you with your signal strength.
I have a CW memory to send that message to check propagation, especially when I don’t hear much activity on a band.
Just now, with 100W and my antenna pointed east:
Jim N7US
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Chuck, WS1L
Sent: Friday, April 10, 2020 08:58 To: dxlab@groups.io Subject: [DXLab] RBN as a propagation check
Hello to all, here’s hoping all are well during this time of real biological virii, as well as the false positives of the computing variety.
I will often look at the RBN webpage to see were my CQ's are landing on a band that may or may not be open. http://www.reversebeacon.net/dxsd1/dxsd1.php?f=0&c=ws1l&t=dx
I know there is an RBN source feeding Spot Collector, and I brought up it’s window and tried to feed a few CC Cluster commands to it to show my recent spots but the RBN window just kept pumping spots at me like a firehose.
Ideally I’d like to be able to have the RBN show me where my signal is reaching, as a means of checking for an open band. I know it’s not strictly DX related but it’s at least DX-adjacent. Is there a way to filter RBN spots like this? I did try filtering Spot Collector by my Call but no results there either.
73 de Chuck, WS1L _._,_._,_
|
||
|
||
Re: Upgrade DX Keeper from 7.1.9 to 15.4.9
Jim McPhee
I had a similar problem yesterday. In my case, it was Defender quarantining dxkeeper.exe. Every time I went into the dxkeeper folder, made a copy of the most recent dxkeeper executable (that was in the folder), and renamed it dxkeeper.exe, Defender would quarantine it. When I attempted to update to the newest version from Launcher's Config, I would get the same "file is in use or dxkeeper.exe is write protected" message. I finally caught on and told Defender to exclude the entire DXLAB folder from scans. That fixed the problem.
-- Jim McPhee Placitas, NM W5ABA
|
||
|
||
Re: Import trouble, unexpected "," in County field
Martin Sole
Bob,
toggle quoted messageShow quoted text
Many thanks. I think I can work some Excel trickery to combine the 2 columns. I suppose that is specified in the ADIF information, I should read more :) 73 Martin, HS0ZED
On 10/04/2020 18:57, KA9JAC wrote:
The proper format for the County Field is (State,County) ie: NJ,Monmouth
|
||
|
||
Re: RBN as a propagation check
ve3ki
Do *not* connect directly to the RBN cluster node - that does not accept filter commands. It is intended solely for the use of other cluster nodes.
toggle quoted messageShow quoted text
Instead, connect to a regular DX cluster node that carries RBN spots. The regular VE7CC cluster node is one such; you can find others by going to <https://www.dxcluster.info/telnet/index.php> and looking for the "(+CW Skimmer)" notation in the left-hand column beneath the name of the cluster node. You may need to issue a command to the node to tell it to turn RBN spots on. 73, Rich VE3KI
On Fri, Apr 10, 2020 at 09:58 AM, Chuck, WS1L wrote:
|
||
|
||
Re: RBN as a propagation check
DAVID BERNHEISEL
Have you investigated PSKreporter? https://pskreporter.info/pskmap Dave, N2DPF
On 4/10/2020 8:58 AM, Chuck, WS1L
wrote:
|
||
|
||
RBN as a propagation check
Hello to all, here’s hoping all are well during this time of real biological virii, as well as the false positives of the computing variety.
I will often look at the RBN webpage to see were my CQ's are landing on a band that may or may not be open. http://www.reversebeacon.net/dxsd1/dxsd1.php?f=0&c=ws1l&t=dx
I know there is an RBN source feeding Spot Collector, and I brought up it’s window and tried to feed a few CC Cluster commands to it to show my recent spots but the RBN window just kept pumping spots at me like a firehose.
Ideally I’d like to be able to have the RBN show me where my signal is reaching, as a means of checking for an open band. I know it’s not strictly DX related but it’s at least DX-adjacent. Is there a way to filter RBN spots like this? I did try filtering Spot Collector by my Call but no results there either.
73 de Chuck, WS1L
|
||
|
||
Re: Infected file for Commander 14.5.5 update?
Pete Smith
In Defender's "defense"
(sic), I've used it as my sole anti-virus for maybe 5 years. It
does sometimes warn me when I'm installing a new program that
will try to do things that its network security sometimes thinks
are risky, but it offers an easy option to say "no, it's OK."
This last episode with Commander was the first time I've had it
interfere with a DXLab download in several years. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your favorite "retail" DX cluster. On 4/9/2020 10:44 PM, neil_zampella
wrote:
|
||
|
||
Re: Import trouble, unexpected "," in County field
KA9JAC
The proper format for the County Field is (State,County) ie:
NJ,Monmouth
Hope this helps 73 Bob, KA9JAC On 4/10/2020 6:49 AM, Martin Sole
wrote:
Hi,
|
||
|
||
Import trouble, unexpected "," in County field
Martin Sole
Hi,
I am helping a friend to convert his excel file logbook and import it into DX Keeper. All has gone well so far by changing a few field headings to make them recognised and then exporting the Excel file as a tab delimited file. This file imports into DX Keeper fine with what seems to be one strange effect that I have not been able to track down. In DXKeeper the imported log shows a , in front of every county, so instead of Monmouth it shows ,Monmouth this of course produces a lot or errors with county changed and invalid secondary administrative subdivision. Looking at the tab delimited file there is no evidence of the spurious , Is there a simple explanation for whats going on? Martin, HS0ZED
|
||
|