+ AA6YQ comments below
Do your thoughts on implementation include using the park specified in the spot to fill out the grid, state, section, etc., in the DXKeeper Capture window?
+ Using POTA as an example, if SpotCollector is aware that DXView has created a POTA database, then when an incoming spot that specifies a POTA tag causes SpotCollector to create a new Spot Database Entry or update an existing Entry that did not previously specify such a tag, SpotCollector would populate the Entry's Primary, Secondary, and Region fields with information obtained by looking up the POTA tag in the POTA database. Double-clicking a Spot Database Entry would populate DXKeeper's Capture window and WinWarbler's "QSO Info" panel as it does today.? + This more precise location information would benefit ops not pursuing POTA - for example, by pinpointing the current location of a station operating portable. However, while a summit is likely to be entirely contained by a grid square, a park may not be; thus the extraction of grid square information may not be the the same for POTA and SOTA.?
One other extension is to have the concept of using the POTA API to confirm the log entry is in the POTA database. That would be more involved as you would need the user’s POTA credentials to do that call for their last 100 log entries. But if it’s in the log, that would be considered verified
+ Where is the POTA API documented? ? ? ? 73, ? ? ? ? ? Dave, AA6YQ
|
Do your thoughts on implementation include using the park specified in the spot to fill out the grid, state, section, etc., in the DXKeeper Capture window?
That would aid in having to fix issues after downloading LOTW info.?
One other extension is to have the concept of using the POTA API to confirm the log entry is in the POTA database. That would be more involved as you would need the user’s POTA credentials to do that call for their last 100 log entries. But if it’s in the log, that would be considered verified.?
Tom
NY4I
|
+ AA6YQ comments below
The existing comdlg32.ocx file is dated 20 years ago, yet this is a recent W11 machine. There are no other symptoms (so far), only with dxlabs. I assume that that file is not installed during dxlabs installation, so reinstalling dxlabs will not help.
+ DXKeeper installs comdlg32.ocx, so you could try uninstalling and re-installing DXKeeper - but it's hard to see how that will cure the Launcher's problems.
Dave
|
The existing comdlg32.ocx file is dated 20 years ago, yet this is a
recent W11 machine. There are no other symptoms (so far), only with
dxlabs. I assume that that file is not installed during dxlabs
installation, so reinstalling dxlabs will not help.
There are suggestions floating around that finding a recent version
, placing it in the syswow64 folder and registering it has a good
chance of success. I might give that a try.
I WILL NOT ask you for advice Windows advice beyond DXlabs :-)
Thanks,
-Steve K8LX
On 05/19/25 3:55 PM, Dave AA6YQ wrote:
toggle quoted message
Show quoted text
+ AA6YQ comments below
Just one.
+ Then your system is likely broken. After you discover the root
cause and correct it, let me know and we'll determine what - if
anything - is necessary to restore DXLab functionality.
? ? ? 73,
? ? ? ? ? ? Dave, AA6YQ
|
I started DXLab suite twice when I was too busy to really get into it, and moved on.? I came back for a third time to really learn it, but a big push was to gain an ability to identify various QTHs for POTA and SOTA, and other such activities.
That is not DXing.? Years ago, I tried to create a new term for Local Expeditions, LXpeditions.? It did not gain any traction, but that was before POTA and when SOTA was still in short pants.? The concept independently existed in various forms including Field Day, IOTA and SOTA, among others.??
Local expeditions are great training grounds for future or existing DXers, especially those with more limited antennas or other equipment.
The local expedition concept should be used to encourage lesser DXers to improve their game and enjoy what they do.? DXLab is a great tool for learning the ropes, but mentoring helps.? These proposed additions may well bring more hams into the game.
With limited time and a limited station, I'm pleased to have some 240 DXCC entities. DXLab will help with the next 100 or so.??
If you have well more than 300, perhaps you have the ability to focus the highly configurable DXLab for your limited needs.? Grin.
Ching, $0.02
Rich, NU6T
+ AA6YQ comments below
The real question is whether doing this "extra" stuff fits into DXLabs' charter. On occasion, Dave has denied other "improvements," saying DXLabs is intended for chasing DX.? So does POTA/SOTA really help in one's quest for DX?
+ Over the past 24 years, I don't recall anyone objecting to DXLab's support for IOTA, even though not everyone pursues IOTA awards. How are POTA and SOTA different than IOTA? + The "problem" with DXCC awards is that there are only 340 current DXCC entities, and not all of those are typically QRV. The 40 WAZ zones don't help much; an HF DXer seeking to continuously improve his or her skills must pursue a wider array of targets: DXCC Challenge, WAZ-bands, WAZ-modes, WAZ-band-modes, DX Marathon, and/or IOTA.? + In 2016, the ARRL hosted a one-year "National Parks on the Air" (NPOTA) activity based on LoTW confirmations. Though implementing the required Leaderboard slowed down our effort at the time to improve LoTW's reliability and availability, the activity was unexpectedly popular. NPOTA was followed by the one-year Centennial and Grid-chase activities, which were also popular. Sadly, the ARRL discontinued these annual activities without converting one or more of them into permanent awards. POTA and SOTA filled the void they left. + Each QSO in DXKeeper has a dedicated SOTA item, which consumes 16 bytes. For POTA, DXKeeper refers to the "user-defined item whose caption is POTA", so no additional space is consumed. Each Spot Database Entry has dedicated POTA, SOTA, and WWFF fields that total 34 bytes - out of an average of ~2000 bytes per Entry. SpotCollector was already inspecting spot notes for IOTA tags; given today's CPU speeds, having this function detect and extract POTA, SOTA, and WWFF tags didn't significantly increase the time required to inspect notes. No one reported any perceived reduction SpotCollector performance after these fields and the process of populating them were added 5 years ago. + DXLab's Realtime Award Tracking (RAT) for DXCC is always enabled, but RAT for IOTA, Marathon, VUCC, WAS, WAZ, and WPX awards are all disabled by default. Maintenance of the database tables required to track progress for one of these awards and realtime checking for needed active stations only occurs if the user enables RAT for that award, minimizing any performance penalty for users not pursuing that award. The same design pattern would be applied to POTA and/or SOTA if RAT were extended to support them. + Increasing DXLab's support for POTA and SOTA could be accomplished via a series of steps: 1. extend DXView to enable the user to download the current POTA and SOTA lists and create/update a searchable database for each so that specification of a POTA or SOTA code in DXView's Main window would enable DXView to display the name and location of the specified park or summit, with short-path and long-path headings and rotator control 2. extend DXView to accept a directive from another application to "lookup" a specified POTA or SOTA tag, displaying the name and location of the specified park or summit, with short-path and long-path headings and rotator control
?
3. extend SpotCollector to respond to new right-mouse menu commands? to "lookup" a Spot Database Entry's POTA or SOTA tag by sending that tag to DXView and directing it to perform the appropriate lookup operation
4. extend DXKeeper and SpotCollector to support RAT for POTA and SOTA
+ Yesterday's poll shows that 50 users here are pursuing POTA, and 29 are pursuing SOTA.? Given the modest development effort required, that seems like more than enough to justify steps 1, 2, and 3.
+ As always, comments, suggestions, and better ideas are welcome.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
|
+ AA6YQ comments below
I would not mind seeing the discussion here.
+ Such a discussion here would be entirely relevant. ? ? 73,
? ? ? ? ? Dave, AA6YQ
|
I would not mind seeing the discussion here.
Support/development for Log4OM has been on again, off again for quite
a while and with the recent loss of W9MBB, I wonder if support and
development is bound for another off again cycle.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-05-19 3:44 PM, Chip - W6MY via groups.io wrote: I was thinking of giving Log4OM a try until i read your post. I would welcome your insights and discoveries that influenced your decision. ?If you prefer not to post please PM me.
w6my@...
|
+ AA6YQ comments below
Just one.
+ Then your system is likely broken. After you discover the root cause and correct it, let me know and we'll determine what - if anything - is necessary to restore DXLab functionality. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ
|
+ AA6YQ comments below
The real question is whether doing this "extra" stuff fits into DXLabs' charter. On occasion, Dave has denied other "improvements," saying DXLabs is intended for chasing DX. ?So does POTA/SOTA really help in one's quest for DX?
+ Over the past 24 years, I don't recall anyone objecting to DXLab's support for IOTA, even though not everyone pursues IOTA awards. How are POTA and SOTA different than IOTA? + The "problem" with DXCC awards is that there are only 340 current DXCC entities, and not all of those are typically QRV. The 40 WAZ zones don't help much; an HF DXer seeking to continuously improve his or her skills must pursue a wider array of targets: DXCC Challenge, WAZ-bands, WAZ-modes, WAZ-band-modes, DX Marathon, and/or IOTA.? + In 2016, the ARRL hosted a one-year "National Parks on the Air" (NPOTA) activity based on LoTW confirmations. Though implementing the required Leaderboard slowed down our effort at the time to improve LoTW's reliability and availability, the activity was unexpectedly popular. NPOTA was followed by the one-year Centennial and Grid-chase activities, which were also popular. Sadly, the ARRL discontinued these annual activities without converting one or more of them into permanent awards. POTA and SOTA filled the void they left. + Each QSO in DXKeeper has a dedicated SOTA item, which consumes 16 bytes. For POTA, DXKeeper refers to the "user-defined item whose caption is POTA", so no additional space is consumed. Each Spot Database Entry has dedicated POTA, SOTA, and WWFF fields that total 34 bytes - out of an average of ~2000 bytes per Entry. SpotCollector was already inspecting spot notes for IOTA tags; given today's CPU speeds, having this function detect and extract POTA, SOTA, and WWFF tags didn't significantly increase the time required to inspect notes. No one reported any perceived reduction SpotCollector performance after these fields and the process of populating them were added 5 years ago. + DXLab's Realtime Award Tracking (RAT) for DXCC is always enabled, but RAT for IOTA, Marathon, VUCC, WAS, WAZ, and WPX awards are all disabled by default. Maintenance of the database tables required to track progress for one of these awards and realtime checking for needed active stations only occurs if the user enables RAT for that award, minimizing any performance penalty for users not pursuing that award. The same design pattern would be applied to POTA and/or SOTA if RAT were extended to support them. + Increasing DXLab's support for POTA and SOTA could be accomplished via a series of steps: 1. extend DXView to enable the user to download the current POTA and SOTA lists and create/update a searchable database for each so that specification of a POTA or SOTA code in DXView's Main window would enable DXView to display the name and location of the specified park or summit, with short-path and long-path headings and rotator control 2. extend DXView to accept a directive from another application to "lookup" a specified POTA or SOTA tag, displaying the name and location of the specified park or summit, with short-path and long-path headings and rotator control
?
3. extend SpotCollector to respond to new right-mouse menu commands? to "lookup" a Spot Database Entry's POTA or SOTA tag by sending that tag to DXView and directing it to perform the appropriate lookup operation
4. extend DXKeeper and SpotCollector to support RAT for POTA and SOTA
+ Yesterday's poll shows that 50 users here are pursuing POTA, and 29 are pursuing SOTA.? Given the modest development effort required, that seems like more than enough to justify steps 1, 2, and 3.
+ As always, comments, suggestions, and better ideas are welcome.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
|
Just one.
On 05/19/25 2:35 PM, Dave AA6YQ wrote:
toggle quoted message
Show quoted text
+ AA6YQ comments below
Clicking the Launcher's "C nfig" button does not
bring up any window.
+ How many monitors do you have?
? ? ?73,
? ? ? ? ?Dave, AA6YQ
|
I was thinking of giving Log4OM a try until i read your post. I would welcome your insights and discoveries that influenced your decision. ?If you prefer not to post please PM me.
?
w6my@...
|
I chase SOTA and sometimes POTA because it gives me something to do while waiting?for the DX to show up. To each his own.
The real question is whether doing this "extra" stuff fits into DXLabs' charter. On occasion, Dave has denied other "improvements," saying DXLabs is intended for chasing DX.? So does POTA/SOTA really help in one's quest for DX?? Dave will have to make this call.? I don't do either one.
--
Tom-KQ5S
|
The real question is whether doing this "extra" stuff fits into DXLabs' charter. On occasion, Dave has denied other "improvements," saying DXLabs is intended for chasing DX. ?So does POTA/SOTA really help in one's quest for DX? ?Dave will have to make this call. ?I don't do either one.
--
Tom-KQ5S
|
+ AA6YQ comments below
Clicking the Launcher's "C nfig" button does not bring up any window.
+ How many monitors do you have? ? ? ?73, ? ? ? ? ?Dave, AA6YQ
|
Clicking the Launcher's "C nfig" button does not bring up any
window.
On 05/19/25 1:28 PM, Dave AA6YQ wrote:
toggle quoted message
Show quoted text
+ AA6YQ comments below
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!
+ Files only disappear when you delete them or when a hardware
or device driver failure causes them to be lost. In combination
with the display problem your report above, I'd be concerned
about the integrity of your system.
+ On the "DXLab Apps" tab of the Launcher's Configuration
window, click DXKeeper's Restore button. Can you now start and
run DXKeeper?
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
Exactly! I really do not understyand why some people are so closed-minded to anything new. If you are not into POTA, then you would not use the new features. Depending upon how it was implemented, the lookup of each POTA entity would not have to be processed that much to get the park location, grid square, state, coordinates, etc. As many of the POTA spots I use to feed SpotCollector come from dx.cqspot.com:1234, that is the only one that gets hit heavily with spots but one that did not connect there would only see potentially the RBN for CW/FT8, etc.
?
It would also be a reasonable thing to add a simple 100 entry cache as many of the park spotsa are repetitive for a given duration. A cache would save doing the lookup (with a small tradeoff in nowadays ubiquitious memory). But those are implementation details...
?
As a use case, it would be great to have this not only for the beam heading but when I click on a spot, the state, section and grid could be put into into the Capture window. I always have to update that info before I save the QSO when I click on a POTA spot even though the park is in the comment from dx.cqspot.com:1234. Granted it gets fixed in the LOTW download, but it would be nice to do it up front.
?
73,
?
Tom
NY4I
|
Re: DXKeeper 18.1.4's new ability to QSL via the Windows Clipboard...
Tnx the add. It works AOK. I reworked my QSL template to accommodate the vertical output.
73 Ron K3LUE
|
If you prefer, this link returns a JSON file:
?
Tom
NY4I
|
+ AA6YQ comments below
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!
+ Files only disappear when you delete them or when a hardware or device driver failure causes them to be lost. In combination with the display problem your report above, I'd be concerned about the integrity of your system. + On the "DXLab Apps" tab of the Launcher's Configuration window, click DXKeeper's Restore button. Can you now start and run DXKeeper? ? ? ?73, ? ? ? ? ? ?Dave, AA6YQ
|
Correction: COMDLG32.ocx
On 05/19/25 1:04 PM, Steve Maki wrote:
toggle quoted message
Show quoted text
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
|
Tom Schaefer - NY4I
Kent N6WT
Ron T