I thought I'd seen this issue (COMDKG32.ocx missing) discussed in
the past, but it doesn't come up when I searched the archives.
I'm seeing this error all of a sudden when either trying to start a
DXL app from? it's exe file in C:\DXLab\DXKeeper (for example), or
when trying it from the launcher.
The launcher start buttons are currently red for installed apps. One
other odd thing is the config button in the Launcher lower left has
the "o" whited out like C nfig.
Any clue would be appreciated!
-Steve K8LX
|
David
Thanks for the info, I will check it out!
On Mon, May 19, 2025 at 7:43?AM David Westbrook via <dwestbrook= [email protected]> wrote: >?Is there a way to find a Maidenhead grid or beam heading for a park easily? The POTA app does not provide that info.
Kent -- If you use the "POTAPlus" Chrome Browser extension [I'm the author], it adds the bearing & distance (and a lot more information, including?ATNO's for you based on official?hunter log) into the POTA spots page.? It's also possible to integrate it with Commander and DXKeeper,? so you can QSY and also log directly from the spots page, including the park info, with just a button click, and no copy/paste needed.? ? ?
73 --david K2DW
I have to agree with Bob. The thing that people might want to track for POTA is the park from which they operated?from. You can do that currently with "my QTH's". If people did it correctly, their uploads to LotW would show the correct location. I use "my QTH's" to track my SOTA activations.
The other thing you might want as a chaser of POTA or SOTA is a beam heading of the park or summit. I currently do this for chasing SOTA by opening the ?(you have to be?logged?in to get the correct heading) and then click on the summit to get the heading. I then enter the heading manually?into DXView. I don't know how to find?the heading for a park. Is there a way to find a Maidenhead grid or beam heading for a park easily? The POTA app does not provide that info.
The current way SpotCollector displays SOTA info is great, you click on the spot and the summit reference?is entered into the DXK capture window and logged. I think DXLabs is the easiest?way to chase SOTA.
I dont understand why you would even think about extending support
for pota
The pota folks contacts are all tracked on the pota data system
activators have to submit logs, those chasing them dont have to do
anything...
73
Bob, KA9JAC
PS way to dang many of them upload garbage to lotw...
On 5/18/2025 2:55 AM, Dave AA6YQ wrote:
A new poll has been created:
Do you pursue POTA and/or SOTA awards?
1. I'm pursuing POTA awards but not SOTA awards
2. I'm pursuing SOTA awards but not POTA awards
3. I'm pursuing both POTA and SOTA awards
Click Here To Vote
Do not reply to this message to vote in the poll. You can vote
in polls only through the group's website.
|
>?Is there a way to find a Maidenhead grid or beam heading for a park easily? The POTA app does not provide that info.
Kent -- If you use the "POTAPlus" Chrome Browser extension [I'm the author], it adds the bearing & distance (and a lot more information, including?ATNO's for you based on official?hunter log) into the POTA spots page.? It's also possible to integrate it with Commander and DXKeeper,? so you can QSY and also log directly from the spots page, including the park info, with just a button click, and no copy/paste needed.? ? ?
73 --david K2DW
I have to agree with Bob. The thing that people might want to track for POTA is the park from which they operated?from. You can do that currently with "my QTH's". If people did it correctly, their uploads to LotW would show the correct location. I use "my QTH's" to track my SOTA activations.
The other thing you might want as a chaser of POTA or SOTA is a beam heading of the park or summit. I currently do this for chasing SOTA by opening the ?(you have to be?logged?in to get the correct heading) and then click on the summit to get the heading. I then enter the heading manually?into DXView. I don't know how to find?the heading for a park. Is there a way to find a Maidenhead grid or beam heading for a park easily? The POTA app does not provide that info.
The current way SpotCollector displays SOTA info is great, you click on the spot and the summit reference?is entered into the DXK capture window and logged. I think DXLabs is the easiest?way to chase SOTA.
I dont understand why you would even think about extending support
for pota
The pota folks contacts are all tracked on the pota data system
activators have to submit logs, those chasing them dont have to do
anything...
73
Bob, KA9JAC
PS way to dang many of them upload garbage to lotw...
On 5/18/2025 2:55 AM, Dave AA6YQ wrote:
A new poll has been created:
Do you pursue POTA and/or SOTA awards?
1. I'm pursuing POTA awards but not SOTA awards
2. I'm pursuing SOTA awards but not POTA awards
3. I'm pursuing both POTA and SOTA awards
Click Here To Vote
Do not reply to this message to vote in the poll. You can vote
in polls only through the group's website.
|
On 2025-05-19 10:16 AM, Kent N6WT via groups.io wrote: I don't understand your concern. The SOTA, POTA and WWFF fields have
been part of SC for about 5 years now. And processing that data takes a finite additional time for each spot. It represents an unnecessary degradation in performance for the vast majority of users who do not engage in SOTA/POTA/WWFF/LH/CASTLES, etc. and for SOTA/POTA/etc. users who use the proprietary tools when dealing with those arbitrary patches of dirt. 73, ... Joe, W4TV On 2025-05-19 10:16 AM, Kent N6WT via groups.io wrote: On Mon, May 19, 2025 at 6:38?AM Joe Subich, W4TV via groups.io
Here, I would object to POTA/SOTA specific fields with their associated
overhead in SpotCollector. The improvements in SC 9.9.2 are great and
SC appears to be processing spots almost twice as fast as previous
versions.
Joe
I don't understand your concern. The SOTA, POTA and WWFF fields have been
part of SC for about 5 years now.
Thanks
73
Kent
N6WT
On Mon, May 19, 2025 at 6:38?AM Joe Subich, W4TV via groups.io <lists=
[email protected]> wrote:
On 2025-05-18 11:18 PM, Tom ai4th via groups.io wrote:
POTA and SOTA seem to be polarizing to some parts of the ham
community. Live and let live. If Dave is gracious enough to put
fields in Spotcollector to support these public-facing parts of the
hobby, good on him. Here, I would object to POTA/SOTA specific fields with their associated
overhead in SpotCollector. The improvements in SC 9.9.2 are great and
SC appears to be processing spots almost twice as fast as previous
versions.
This version actually appears to run reasonably on a "toy" system -
an 800 MHz Intel N100 (four cores, four threads) with 16 GB single
channel RAM. It can "keep up" with four clusters (each with open
skimmer feeds) plus IRC during normal operation (I have not tried
to benchmark it during a major contest) with sufficient CPS cycles
to support normal WSJTX and DXKeeper operation. That was not the
case with previous versions of SpotCollector.
I would hate to see anything that would result in any degradation
in performance for the majority of users to support niche operation
- particularly since DXLab can never fully support POTA/SOTA due
to their closed data systems and unique operating paradigm.
73,
... Joe, W4TV
On 2025-05-18 11:18 PM, Tom ai4th via groups.io wrote:
POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in
Spotcollector to support these public-facing parts of the hobby, good on
him. I will strain my few remaining brain cells to make use of the new
tools. (Mainly PoTA. I'm too out of shape for summits, even in Va.)
Tom ai4th
|
On Mon, May 19, 2025 at 6:38?AM Joe Subich, W4TV via Here, I would object to POTA/SOTA specific fields with their associated
overhead in SpotCollector.? The improvements in SC 9.9.2 are great and
SC appears to be processing spots almost twice as fast as previous
versions.
Joe I don't understand your concern. The SOTA, POTA and WWFF fields have been part of SC for about 5 years now.
On Mon, May 19, 2025 at 6:38?AM Joe Subich, W4TV via <lists= [email protected]> wrote:
On 2025-05-18 11:18 PM, Tom ai4th via wrote:
> POTA and SOTA seem to be polarizing to some parts of the ham
> community. Live and let live. If Dave is gracious enough to put
> fields in Spotcollector to support these public-facing parts of the
> hobby, good on him.
Here, I would object to POTA/SOTA specific fields with their associated
overhead in SpotCollector.? The improvements in SC 9.9.2 are great and
SC appears to be processing spots almost twice as fast as previous
versions.
This version actually appears to run reasonably on a "toy" system -
an 800 MHz Intel N100 (four cores, four threads) with 16 GB single
channel RAM.? It can "keep up" with four clusters (each with open
skimmer feeds) plus IRC during normal operation (I have not tried
to benchmark it during a major contest) with sufficient CPS cycles
to support normal WSJTX and DXKeeper operation.? That was not the
case with previous versions of SpotCollector.
I would hate to see anything that would result in any degradation
in performance for the majority of users to support niche operation
- particularly since DXLab can never fully support POTA/SOTA due
to their closed data systems and unique operating paradigm.
73,
? ? ... Joe, W4TV
On 2025-05-18 11:18 PM, Tom ai4th via wrote:
> POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in Spotcollector to support these public-facing parts of the hobby, good on him. I will strain my few remaining brain cells to make use of the new tools. (Mainly PoTA. I'm too out of shape for summits, even in Va.)
> Tom ai4th
>
|
On 2025-05-18 11:18 PM, Tom ai4th via groups.io wrote: POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in Spotcollector to support these public-facing parts of the hobby, good on him. Here, I would object to POTA/SOTA specific fields with their associated overhead in SpotCollector. The improvements in SC 9.9.2 are great and SC appears to be processing spots almost twice as fast as previous versions. This version actually appears to run reasonably on a "toy" system - an 800 MHz Intel N100 (four cores, four threads) with 16 GB single channel RAM. It can "keep up" with four clusters (each with open skimmer feeds) plus IRC during normal operation (I have not tried to benchmark it during a major contest) with sufficient CPS cycles to support normal WSJTX and DXKeeper operation. That was not the case with previous versions of SpotCollector. I would hate to see anything that would result in any degradation in performance for the majority of users to support niche operation - particularly since DXLab can never fully support POTA/SOTA due to their closed data systems and unique operating paradigm. 73, ... Joe, W4TV On 2025-05-18 11:18 PM, Tom ai4th via groups.io wrote: POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in Spotcollector to support these public-facing parts of the hobby, good on him. I will strain my few remaining brain cells to make use of the new tools. (Mainly PoTA. I'm too out of shape for summits, even in Va.)
Tom ai4th
|
Re: DXKeeper 18.1.4 and SpotCollector 9.9.2
Tnx Dave
?
very happy with this upgrade!
?
73,? Aart PA3C
|
True that. But the tiered chaser awards are very popular. The parks (and operators) are not one-and-done. On Sun, 18 May 2025 19:07:34 -0700 "Dave AA6YQ via groups.io" <aa6yq@...> wrote: + There are fewer activators than chasers. -- 73 -Jim NU0C
|
updated eQSL AG, LoTW, and RDA databases are available ...
... via the Databases tab of DXView's Configuration window. Terminate DXKeeper, WinWarbler, and SpotCollector before directing DXView to update these databases. ? ??? 73, ? ??????????? Dave, AA6YQ
|
+ AA6YQ comments below
POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in Spotcollector to support these public-facing parts of the hobby, good on him. I will strain my few remaining brain cells to make use of the new tools. (Mainly PoTA. I'm too out of shape for summits, even in Va.)
+ POTA, SOTA, and WWFF fields were added to SpotCollector in version 8.7.2 back in August 2020. SpotCollector inspects the notes fields of incoming spots, recognizes POTA, SOTA, and WWFF tabs, and inserts them into Spot Database Entries.
?
? ? 73,
? ? ? ? ? ?Dave, AA6YQ
|
+ AA6YQ comments below
Here is the file for all the SOTA Summits.
?
+ Thanks, Kent! Nearly 178K summits are defined in that file.
?
? ? ?73,
?
? ? ? ? ? ?Dave, AA6YQ
|
POTA and SOTA seem to be polarizing to some parts of the ham community. Live and let live. If Dave is gracious enough to put fields in Spotcollector to support these public-facing parts of the hobby, good on him. I will strain my few remaining brain cells to make use of the new tools. (Mainly PoTA. I'm too out of shape for summits, even in Va.)
Tom ai4th
|
Dave?
Here is the file for all the SOTA Summits.
+ AA6YQ comments below
I am fairly sure there is a file for SOTA summits. I don't know about POTA.?
+ This file contains the names and locations of 74K Parks around the world:
?
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
+ AA6YQ comments below
I am fairly sure there is a file for SOTA summits. I don't know about POTA.?
+ This file contains the names and locations of 74K Parks around the world:
?
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
Re: DXKeeper 18.1.4's new ability to QSL via the Windows Clipboard...
+ AA6YQ comments below
I just tried this and got:
A61BG on 18.102 in FT8 at 2025-05-17 21:26:45Z (A6: United Arab Emirates)
Your example shows:
Callsign: FK8HM
Frequency: 28.076
Mode: FT8
Date: 2025-04-20
Time: 23:58:45Z
SNR: -09
Not only is the formatting different, but mine did not give me the SNR: for an FT8 contact. I pasted this into Windows Notepad.
+ You selected the "Copy to Windows Clipboard" command at the bottom of the right-mouse menu.
+ Try the new "QSL to Windows Clipboard" command; it's in the middle of the right-mouse menu.
73,
Dave, AA6YQ
|
Re: DXKeeper 18.1.4's new ability to QSL via the Windows Clipboard...
I just tried this and got:
A61BG on 18.102 in FT8 at 2025-05-17 21:26:45Z (A6: United Arab Emirates)
?
Your example shows:
Callsign:? FK8HM
Frequency: 28.076
Mode:????? FT8
Date:????? 2025-04-20
Time:????? 23:58:45Z
SNR:?????? -09
?
Not only is the formatting different, but mine did not give me the SNR: for an FT8 contact. ?I pasted this into Windows Notepad.
--
Tom-KQ5S
|
I am fairly sure there is a file for SOTA summits. I don't know about POTA.?
I have heard that portable operations are the fastest growing part of ham radio.
Thanks
73
Kent
N6WT
+ AA6YQ comments below
Yes, I use it to see POTA stations also. However, if I double click on a POTA/SOTA spot the beam heading is for the operators home QTH. It would be great to have a way to show the correct beam heading to the park or summit in DXView.
+ If someone can point me at a file or online resource that contains grid locations or latitudes and longitudes for POTA parks, I'll be happy to enable DXLab to exploit it.
My question is, what are you proposing for DXLabs as far as POTA/SOTA?
+ I haven't proposed anything; I am assessing interest levels.
? ? ? ?73,
? ? ? ? ? ? ? ? Dave, AA6YQ
|
+ AA6YQ comments below
Unworked parks is not the only thing sought after. There are also awards for working parks and activators multiple times. Each award has multiple tiers. That's not even considering the various activator awards.
+ There are fewer activators than chasers.
?
? ? ? 73,
?
? ? ? ? ? ? Dave, AA6YQ
|
Re: help with commander + WSJTX+JTALert for flex 8600
+ AA6YQ comments below
I would love to but the link you sent said instance 1 should use dxcommander and no rig name extension .
Instance 2 should connect directly to the radio and use a rig name extension. Did I read it wrong? ?
+ Yes, that's what the first two steps say in
+ According to this article
you can specify a slice as the rig-name parameter.
+ You might ask Joe WQ6Q, as I believe he employs this technique.
73,
Dave, AA6YQ
|
Unworked parks is not the only thing sought after. There are also awards for working parks and activators multiple times. Each award has multiple tiers. That's not even considering the various activator awards. On Sun, 18 May 2025 18:00:48 -0700 "Dave AA6YQ via groups.io" <aa6yq@...> wrote: + There are awards for working stations in parks:
+ DXLab could identify active stations in unworked parks. -- 73 -Jim NU0C
|
Kent N6WT
aart wedemeijer PA3C
Jim Shorney
Tom ai4th