I downloaded credits today and received this in the report.? How do I go
about fixing it?
73
Stan
KM4HQE
Log file????? = C:\DXLab\DXKeeper\Databases\KM4HQE.mdb
DXCC Account? = 1
Number?? DXCC QSO#?? Confirm??????? Callsign? Entity Code Date????
Band?????? Mode?? Action
???? 1? 1127704703????? card?????????? 4S7AB????????? 315
2022-01-23????? 30M?????? DATA?? no exact match found in log, new
Entity-Band
???? 2? 1127704702????? card?????????? 4S7AB????????? 315
2023-07-23????? 17M?????? DATA?? no exact match found in log, new
Entity-Band
???? 3? 1127704701????? card?????????? 4S7AB????????? 315
2023-04-23????? 15M?????? DATA?? no exact match found in log, new
Entity-Band
Total DXCC Credits????????????????????????????????????? 1521
DXCC Credits already linked???????????????????????????? 1515
DXCC Credits already marked as duplicates????????????????? 3
Results if an AutoLink operation had been performed instead of an
Analyze operation
DXCC Credits missing information?????????????????????????? 0
DXCC Credits matching no QSOs????????????????????????????? 3
DXCC Credits matching multiple QSOs??????????????????????? 0
DXCC Credits matching an already linked QSO??????????????? 0
DXCC Credits matching one QSO but card/LotW ambiguous????? 0
DXCC Credits newly linked????????????????????????????????? 0
DXCC Credits newly linked with card granted new credit???? 0
DXCC Credits newly linked with LotW granted new credit???? 0
DXCC Credits remaining unlinked??????????????????????????? 3
|
The current version of DXKeeper provides an "IOTAmem4win update" checkbox in the IOTA panel on the Configuration window's Awards tab. DXKeeper's Reference Documentation describes this checkbox thusly:
------- This panel's?IOTAmem4win?checkbox?determines whether??will also create?IOTA_Worked?and?IOTA_Confirmed?update files for??in DXKeeper's?Reports?sub-folder. ? The URL to which IOTAMe4WIN links
http://www.rsgbiota.org/downloads.php4
produces a "page no longer exists" error if one attempts to traverse it.
There is no mention of IOTAMem4WIN in the current IOTA-World documentation:
https://www.iota-world.org/iota-directory/iota-programme-rules/iota-programme-application-procedures.html
My understanding is that DXKeeper's current submission support for IOTA award applications provides the necessary ability to convey QSOs to IOTA-world for IOTA award credit; the file generated for submission to IOTAMem4WIN is not used. ? In the next version of DXKeeper, the IOTA panel on the Configuration window's Awards tab contains 3 new checkboxes: -?????? Mixed -?????? HF -?????? VHF ? To avoid expanding the size of DXKeeper's Configuration window when the Awards tab is selected, I plan to make room by removinig the "IOTAmem4win update" checkbox. If there's a reason to not remote this checkbox, please let me know.
??????? 73,
??????? ??????Dave, AA6YQ
? ?
|
Re: QSO Path in DX Atlas?
+ AA6YQ comments below
Hello Dave - it is my understanding that DX Atlas relies on the Log Provider (i.e. DXLab, HRD, etc.) to show the QSO path. The functionality works great in DXLab, but I am looking for an option to increase the QSO path line density so that the path is more obvious.
+ I don't understand why such an option is needed: here's a screen shot of DX Atlas that I just now made:
+ Please make a screen shot that shows QSO path lines on you DX Atlas World Map, attach it to an email message, and end the message to me via
aa6yq (at) ambersoft.com
73,
Dave, AA6YQ
|
Re: QRZ subscription value?
+ AA6YQ comments below
Yes, I did all that and verified the changes. After about an hour delay sitting, followed by another try... it started working properly.
+ What happened during that first hour? Were error messages displayed? If so, what was their content?
73,
Dave, AA6YQ
|
+ AA6YQ comments below
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.
+ On the Main window's "my QTHs" tab, select the entry for the myQTH you're using in NC. is the Marathon box checked (above the Config button).
73,
Dave, AA6YQ
|
Re: QSO Path in DX Atlas?
Hello Dave - it is my understanding that DX Atlas relies on the Log Provider (i.e. DXLab, HRD, etc.) to show the QSO path.? The functionality works great in DXLab, but I am looking for an option to increase the QSO path line density so that the path is more obvious.? Can you comment, take into consideration this enhancement.? Thanks Dave.? C
|
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
|
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
toggle quoted message
Show quoted text
+ 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
# 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: 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
# 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
# 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
--
|
Re: Recovering from crash - DXKeeper QSOs upload to LoTW error
Got it.
Thanks, Dave.
--
Bruce - W4NDX
|
Craig
W4NDX