开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: QRZ subscription value?

 

Yes, I did all that and verified the changes.? After about an hour delay sitting, followed by another try...? it started working properly.? Go figure.??
Again, thanks for your help.
--
Bruce - W4NDX


Re: ClickFix: how to infect your PC in 3 easy steps

 

Indeed, very easy, thank you very much for this info and making us aware of such a possibility
?
73
?
Juergen, DL8LE


Importing

 

I imported my log from WI into my log down here in NC and now new Marathon entities won't go into the DX Marathon Realtime.
?
73 Dwight NS9I


ClickFix: how to infect your PC in 3 easy steps

 

This one is particularly sneaky!



? ? 73,

? ? ? ? ?Dave, AA6YQ


Re: Invalid administrative subdivision errors

 

Thank you!

Rich, NU6T


On Fri, Mar 14, 2025, 5:38?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below
Dave, Thank you and all the others for helping me get my logs transferred to DXLab.? I have one final error to clear up to finish this initial set of log?imports.?
?
This op appears to be from Moscow, Russia, which seems to be ADIF Country Code 54, Oblast 170, CQ zone 17, ITU zone 29, UA3{ABC} per ADIF 3.0.3 Specifications.? It seems like DXKeeper does not like the "district" KR-14.? It would be happy with KR-13 or KR-15 (from the pull-down menu, no KR-14). The ADIF 3.0.3 Specifications link to the RDA List shows:? "KR-14 BELOREChENSK NEW RDA since 01.01.2025." Is it possible that this new KR-14 is missing from DXKeeper?
+ To obtain an updated Secondary Subdivision Database that reflects the RDA List changes made in January, see

/g/DXLab/message/227144

+Ordinarily, the updated Secondary Subdivision Database would have been included in a next version of DXKeeper by now, but I'm extending "Realtime Award Tracking" to support pursuit of the new IOTA HF and VHF award categories, which is a significant development effort in both DXKeeper and SpotCollector.

+ Alternatively, to stop DXKeeper from considering a QSO with inconsistent Primary or Secondary Subdivisions to be "broken", uncheck the "Subdivision validity checking" box in the "Other Awards" panel along the right side of the Configuration window's Awards tab.

? ? ? ? 73,

? ? ? ? ? ? ?Dave, AA6YQ
?


Re: Invalid administrative subdivision errors

 

+ AA6YQ comments below
Dave, Thank you and all the others for helping me get my logs transferred to DXLab.? I have one final error to clear up to finish this initial set of log?imports.?
?
This op appears to be from Moscow, Russia, which seems to be ADIF Country Code 54, Oblast 170, CQ zone 17, ITU zone 29, UA3{ABC} per ADIF 3.0.3 Specifications.? It seems like DXKeeper does not like the "district" KR-14.? It would be happy with KR-13 or KR-15 (from the pull-down menu, no KR-14). The ADIF 3.0.3 Specifications link to the RDA List shows:? "KR-14 BELOREChENSK NEW RDA since 01.01.2025." Is it possible that this new KR-14 is missing from DXKeeper?
+ To obtain an updated Secondary Subdivision Database that reflects the RDA List changes made in January, see

/g/DXLab/message/227144

+Ordinarily, the updated Secondary Subdivision Database would have been included in a next version of DXKeeper by now, but I'm extending "Realtime Award Tracking" to support pursuit of the new IOTA HF and VHF award categories, which is a significant development effort in both DXKeeper and SpotCollector.

+ Alternatively, to stop DXKeeper from considering a QSO with inconsistent Primary or Secondary Subdivisions to be "broken", uncheck the "Subdivision validity checking" box in the "Other Awards" panel along the right side of the Configuration window's Awards tab.

? ? ? ? 73,

? ? ? ? ? ? ?Dave, AA6YQ
?


Re: Invalid administrative subdivision errors

 

Dave, Thank you and all the others for helping me get my logs transferred to DXLab.? I have one final error to clear up to finish this initial set of log?imports.?

This op appears to be from Moscow, Russia, which seems to be ADIF Country Code 54, Oblast 170, CQ zone 17, ITU zone 29, UA3{ABC} per ADIF 3.0.3 Specifications.? It seems like DXKeeper does not like the "district" KR-14.? It would be happy with KR-13 or KR-15 (from the pull-down menu, no KR-14). The ADIF 3.0.3 Specifications link to the RDA List shows:? "KR-14 BELOREChENSK NEW RDA since 01.01.2025." Is it possible that this new KR-14 is missing from DXKeeper?

I'm thinking the error, in part, is the CQ zone of 16, where the ADIF 3.0.3 specification indicates CQ zone 17 for Moscow.??

DXKeeper is flashing "district" on the "Log QSO" tab in the "Award" panel.

I'm not sure of how to correct this error, thanks for any help:

invalid secondary administrative subdivision: KR-14: <BAND:3>40m<CALL:6>RV6ASU<COMMENT:25>FT8 ?Sent: -19 ?Rcvd: -24<CONT:2>EU<CQZ:2>16<DXCC:2>54<FREQ:8>7.075662<GRIDSQUARE:4>KN94<ITUZ:2>29<MODE:3>FT8<OPERATOR:4>NU6T<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20250227<TIME_ON:6>145430<RST_RCVD:3>-24<RST_SENT:3>-19<TIME_OFF:6>145530<TX_PWR:3>220<APP_LOGGER32_QSO_NUMBER:5>16624<COUNTRY:15>European Russia<eor>

Thanks

Rich, NU6T

On Fri, Mar 14, 2025 at 3:40?PM Richard Hill via <nu6t.rich=[email protected]> wrote:
Thanks, Dave.? Old logs gone, KG6JOT and AE6JW logs imported no errors.? Next to import the big pile for NU6T.??

Rich, NU6T

On Fri, Mar 14, 2025 at 3:17?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
# More AA6YQ comments below
+ I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display>
+ My previous instructions were incorrect: I did say CTRL-CBA. No harm done. Do the CTRL-Delete to remove all QSOs from the current log.

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ



--
Richard Hill



--
Richard Hill


Re: QRZ subscription value?

 

+ AA6YQ comments below

Disabled QSL Queue entry for 6Y7EI on 2025-03-14 at 21:02:17 - station location "Williston, Florida" specified in QSO's QTHID item "williston" doesn't match station location "Williston" selected on the QSL Configuration window's LotW tab

Seems like somewhere there is a QTHID "williston," with station location "Williston, Florida" that is accessed when trying to upload to LoTW.

+ Assuming that you changed the name of your LoTW "Station Location" to Williston, as I suggested, then on the Main window's "my QTHs" tab, the LoTW selector in the Entry whose ID is Williston should specify Williston - not "Williston, Florida".

73,

Dave, AA6YQ


Re: QRZ subscription value?

 

Dave, following your instructions got my DXK running properly again.? ?But when I logged some new QSOs and attempted upload to LoTW a similar problem came up:
?
In DXK QSL tab...
<Add Requested> <Enable All>
LoTW operations panel...
<Upload to LoTW>
all the QSO's enabled are immediately disabled and this error message plays for each:
?
Disabled QSL Queue entry for 6Y7EI on 2025-03-14 at 21:02:17 - station location "Williston, Florida" specified in QSO's QTHID item "williston" doesn't match station location "Williston" selected on the QSL Configuration window's LotW tab
?
Seems like somewhere there is a QTHID "williston," with station location "Williston, Florida" that is accessed when trying to upload to LoTW.
?
Can you help once again?? I really appreciate your patience...
?
Bruce - W4NDX


Re: Invalid administrative subdivision errors

 

Thanks, Dave.? Old logs gone, KG6JOT and AE6JW logs imported no errors.? Next to import the big pile for NU6T.??

Rich, NU6T

On Fri, Mar 14, 2025 at 3:17?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
# More AA6YQ comments below
+ I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display>
+ My previous instructions were incorrect: I did say CTRL-CBA. No harm done. Do the CTRL-Delete to remove all QSOs from the current log.

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ



--
Richard Hill


Re: Invalid administrative subdivision errors

 

# More AA6YQ comments below
+ I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display>
+ My previous instructions were incorrect: I did say CTRL-CBA. No harm done. Do the CTRL-Delete to remove all QSOs from the current log.

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ


Re: Invalid administrative subdivision errors

 

+ AA6YQ comments below
depress the CTRL button while clicking the CBA button above the Log Page Display
+ The CBA button performs a callbook lookup.

+ I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display>

? ? ?73,

? ? ? ? ? Dave, AA6YQ


Re: Invalid administrative subdivision errors

 

I'm losing track in the long series.? I've cut and pasted here.? My comments after the "*". This is where I think I am in the process:
_____________
+ AA6YQ comments below
Repeated steps, Clicked on the "X" to the right of the Filter:None box, Pressed?Control and clicked on the CBA button at the same time.? I got a DXKeeper QRZ Subscriber login text box with the message, " no QRZ callsign specified."? Click OK results in a DXKeeper text box that says, "Callbook error when looking up VU2ELJ: Program Error."
+ In the "Primary Callbook" panel at the top of the Configuration window's Callbook tab, select the "None" option in the upper-left corner".?

? *? Done
_________________

+ OK, then direct DXKeeper to delete all the QSOs in your current log: on the Main window's Log QSOs tab,

1. at the bottom of the tab, click the Filter panel's X button so that all QSOs are present the Log Page Display

2. depress the CTRL button while clicking the CBA button above the Log Page Display

? *? Done
I still see log entries in the log window at the bottom of the "Log QSOs" tab.? I think they should be gone after this operation.? Two log entries are highlighted in pink.? The callsign for one of the highlighted calls is displayed in the top " panel on this QSO:" "Log QSOs" tab.

I thought the above set of actions would empty my logbook.

Rich, NU6T


开云体育 Links:

You receive all messages sent to this group.

View/Reply Online (#228328) | Reply to Group | Reply to Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [nu6t.rich@...]

_._,_._,_



--
Richard Hill


Re: Recovering from crash - DXKeeper QSOs upload to LoTW error

 

Got it.
Thanks, Dave.
--
Bruce - W4NDX


Re: spot with notes from WinWarbler?

 

+ AA6YQ comments below
what I like about it.. the outgoing spot window stays open....I been doing the hard way for years.
?
Hope it helped somebody besides me.? will be chasing POTA cw most the day today.. if wife lets me!
+ Reviewing the Reference Documentation of each DXLab application you've been using may reveal useful functionality that you didn't investigate during your initial scan.

? ? ? ? 73,

? ? ? ? ? ? ?Dave, AA6YQ


Re: spot with notes from WinWarbler?

 

+ AA6YQ comments below
i found it... jezz
?
Depressing the?Ctrl?key while clicking the??button will display WinWarbler's?Outgoing Spot?window, which enables you to specify spot notes?

+ That's described in the 3rd paragraph of the "Generating DX Spots" sub-section of Logging section of WinWarbler's Reference Documentation:?



? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ


Re: spot with notes from WinWarbler?

 

what I like about it.. the outgoing spot window stays open....I been doing the hard way for years.
?
Hope it helped somebody besides me.? will be chasing POTA cw most the day today.. if wife lets me!
?


Re: spot with notes from WinWarbler?

 

i found it... jezz
?
Depressing the?Ctrl?key while clicking the??button will display WinWarbler's?Outgoing Spot?window, which enables you to specify spot notes?
?
Murf


spot with notes from WinWarbler?

 

Can I spot with notes from WinWarbler?
say working a POTA station... I log him from WW then go to dxkeeper
right click on his call to get the spot with notes to come up and?
inform that he is pota.? I did not find in on a quick search.
I did expand the layout on WW and did find I have a POTA window
Tx for the software... before the suite...and learn something new
all the time. Powerful!? Tnx dave.
Murf
n7uvh
?


Re: QRZ subscription value?

 

On 2025-03-13 9:03 PM, Ron DeBlock wrote:

- import from LoTW. LoTW confirmations are imported and count toward
QRZ awards.
That does appear to be a better way to simplify getting QSOs into
QRZ log for non-subscribers.

One can create a logbook for a previous callsign. I did so for my
prior call. That one has not been reassigned, I'm not sure how it
would work if it were reassigned.
I tried it and at least for callsigns that have been reassigned one
needs to "prove" ownership for the time period in question. That
will be a real problem for my original Extra Class call from 1978-
1995 ... I doubt that I have copies of that license and it was
prior to the records in the current FCC ULS (although they could
verify a claim if the bothered to *gasp* look in a printed Callbook
from that era).

73,

... Joe, W4TV

On 2025-03-13 9:03 PM, Ron DeBlock wrote:
One can submit? QSOs to QRZ for free via multiple methods, I have used them all:
- manual entry at QRZ.com
- import ADIF files
- import from LoTW.? LoTW confirmations are imported and count toward QRZ awards.
One can create a logbook for a previous callsign.? I did so for my prior call.? That one has not been reassigned, I'm not sure how it would work if it were reassigned.
QRZ awards are all free.
My normal practice is to upload my logs from DXKeeper to LoTW? then import to QRZ from LoTW.
I do have a QRZ subscription because I find value in the site and want to support it.? However I have not configured DXKeeper to upload and sync with QRZ because...well, laziness :-)? I'll get around to it someday.
73,
-Ron KR2D
On 3/13/2025 8:50 PM, Joe Subich, W4TV wrote:


On 2025-03-13 8:29 PM, Dave AA6YQ wrote:

Charging for the ability to submit confirmations for QRZ awards limits the number of ops will submit confirmations via QRZ. One can
satisfy "A QSL is the final courtesy of a QSO" by uploading
confirmations to Club Log, eQSL, and LoTW - all at no charge.
It appears that one can export an ADIF file of QSOs and manually
import that file to QRZ log.? One can not use the API interface
supported by DXKeeper unless one is a QRZ.com subscriber and one
can not download confirmations - even an ADIF file - unless one
is a subscriber.

I have not attempted to determine if one can set up a logbook for
a previous callsign (particularly if the call has been reassigned)
as it would be pointless.

73,

?? ... Joe, W4TV

On 2025-03-13 8:29 PM, Dave AA6YQ wrote:
One thing that the ARRL got right is that anyone can submit confirmations to LoTW at no charge, whether they are an ARRL member or not.

Charging for the ability to submit confirmations for QRZ awards limits the number of ops will submit confirmations via QRZ. One can satisfy "A QSL is the final courtesy of a QSO" by uploading confirmations to Club Log, eQSL, and LoTW - all at no charge.

73,

Dave, AA6YQ