开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. DXLab
  2. Messages
Expanded Topics Messages Polls
Date
Re: Invalid administrative subdivision errors

 

Well, isn't this an adventure, grin.? I've made suggested changes to this single log entry.
?
First, I tried to make the changes in the error report and upload that, but it is a text file, not ADIF.
?
Second, I loaded the ADIF file into ADIF Master, searched for the entry for KR1STA and saved that single entry into a new ADIF file, and made changes there and tried to import the ADIF into DXKeeper.? The result was an error text file.? Error file says:? "no valid ADIF records found"? I rechecked the ADIF Master entry and all seemed OK, and the ADIF check routine in ADIF Master did not find an error.
?
I was going to attach the ADIF file for the single entry but I don't find a way to link files here, and I don't know how to convert it to a text file.
?
Looking for help.
?
Thanks
Rich, NU6T
Re: SpotCollector is local spotting my FT8 decodes

 

开云体育

On 14/03/2025 6:35 am, Richard via groups.io wrote:
Unfortunately I had to do a clean reset of Winows 11, now I have been reinstalling and configuring my applications. SpotCollector is now local spotting my FT8 decodes and I would like to stop it from doing that as I use SC for DX hits only. Can someone please tell me how to stop it? Please excuse my lack of comuter knowledge.
?
Thanks
?
Richard / N5YPJ

HamSpots shows you spotting from JTAlert indicating your use of JTAlert. That suggests that the SC local spots are likely originating from JTAlert. Turn off SC spotting in the JTAlert Settings windows "DXLab Suite" section.

de Laurie VK3AMA
(JTAlert author)

Re: SpotCollector is local spotting my FT8 decodes

 

Are you using "direct" integration between WSJTX and DXLab
(SpotCollector) or JT Alert? The solution is different for
each configuration.

73,

... Joe, W4TV

On 2025-03-13 3:35 PM, Richard via groups.io wrote:
Unfortunately I had to do a clean reset of Winows 11, now I have been reinstalling and configuring my applications. SpotCollector is now local spotting my FT8 decodes and I would like to stop it from doing that as I use SC for DX hits only. Can someone please tell me how to stop it? Please excuse my lack of comuter knowledge.
Thanks
Richard / N5YPJ
SpotCollector is local spotting my FT8 decodes

 

Unfortunately I had to do a clean reset of Winows 11, now I have been reinstalling and configuring my applications. SpotCollector is now local spotting my FT8 decodes and I would like to stop it from doing that as I use SC for DX hits only. Can someone please tell me how to stop it? Please excuse my lack of comuter knowledge.
?
Thanks
?
Richard / N5YPJ
Re: Invalid administrative subdivision errors

 

Thank you, Joe.
Rich, NU6T


On Wed, Mar 12, 2025, 7:31?PM Joe Subich, W4TV via <lists=[email protected]> wrote:

QRZ.com shows that KR1STA is a vanity call with a Hawaii
address.? It also shows a previous call of WH6DEY so there
is a rather good chance that she's in Hawaii.

Have you imported the QSOs already - if so simply change
Code/DXCC/Entity in the existing QSOs to KH6.? If not,
edit the ADIF file as explained below and import it.

73,

? ? ... Joe, W4TV

On 2025-03-12 9:31 PM, Richard Hill via wrote:
> Rich, thank you.? I believe she was in Hawaii.? This was some 23 years ago,
> so memory may be lacking... but this was one of my first contacts with
> Hawaii.? She was a young ham, in a contest, doing much better than me,
> grin.? I'll check and figure out how to fix this.
>
> Thank you!
>
> Rich, NU6T
>
> On Wed, Mar 12, 2025, 5:09?PM Joe Subich, W4TV via <lists=
> [email protected]> wrote:
>
>>
>> Your ADIF file identifies KR1STA as Country=USA.
>>
>> To make <CNTY:8>HI,Kauai valid, change the DXCC (prefix) for those
>> QSOs to KH6, Change "Code" to 110 or change "Entity" to Hawaii (if
>> you change one the other two will change automatically).
>>
>> If you want to edit the ADIF before import, change <Country:3>USA
>> to <Country:6>Hawaii for the two QSOs.
>>
>> 73,
>>
>>? ? ? ... Joe, W4TV
>>
>>
>> On 2025-03-12 7:55 PM, Richard Hill via wrote:
>>> I'm trying to import ADIF files into DXKeeper.? I have errors I need to
>> fix for a single QSO with Hawaii that shows " <CNTY:8>HI,Kauai ".? I've
>> been trying to learn how to properly fix this error without success.? Any
>> help will be appreciated.? What have I done wrong?
>>>
>>> The original CQ Magazine references are no longer available.? County
>> Hunter seems to have taken over.? I suspect there is an authoritative
>> source I have not found.
>>>
>>> ERROR summary: <CNTY:8>HI,Kauai
>>> References:
>>>
>>>
>>> *?
>>>
>>> My error notices:
>>> 1.? invalid primary administrative subdivision: HI:
>>> <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB
>> 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
>>>
>>> 2.? invalid secondary administrative subdivision: HI,Kauai:
>>> <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB
>> 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
>>>
>>> Thanks
>>> Rich, NU6T
>>>
>>>
Re: LOTW Last Time On

 

This is a case of a station that makes infrequent trips to C6.
He's only just gone back after being away for a couple of years.

Notice the last upload for C6AJB on the LotW site was just yesterday
- too soon to show in the "Users" listing (prepared on Sunday night)
that Dave downloads and updates a couple times a month for DXView
and that Laurie downloads and incorporates in the JT Alert Callsigns
Database which is updated about once a month.

Any "new" users or updated LotW "last upload" dates do not get reflected
in the "users" file until Sunday night and can not be incorporated in
user applications (DXView, JT Alert, WSJTX, etc.) until then.

73,

... Joe, W4TV

On 2025-03-13 11:04 AM, TOM-KQ5S via groups.io wrote:
Just saw C6AJB on 17M FT8. ?DXView shows the last time on s 2023-03-21. ?The drop-down menu on JTAert shows the same. ?When I go to LOTW online and look up the last on time it shows 2025-03-12.
This is just one example. I usually use 6-9 months for what I consider an active LOTW member. ?I have found out I need to check online if a call appears that I want to work. ?I've seen several calls, where DXView or JTAlert show the last upload more than 2 years ago but when I check online the last upload was within a month or so. ?I update the LOTW file with every new release.
I know this isn't a DXLab or JTAlert issue but just a heads up to folks.
Tom-KQ5S
LOTW Last Time On

 

Just saw C6AJB on 17M FT8. ?DXView shows the last time on s 2023-03-21. ?The drop-down menu on JTAert shows the same. ?When I go to LOTW online and look up the last on time it shows 2025-03-12.
This is just one example. I usually use 6-9 months for what I consider an active LOTW member. ?I have found out I need to check online if a call appears that I want to work. ?I've seen several calls, where DXView or JTAlert show the last upload more than 2 years ago but when I check online the last upload was within a month or so. ?I update the LOTW file with every new release.
?
I know this isn't a DXLab or JTAlert issue but just a heads up to folks.
?
Tom-KQ5S
Re: Windows 11 fiasco --I think I am going to wait

 

?You are correct Laurie.....an expensive lesson learned. Like I said I am out a grand.
Re: Windows 11 fiasco --I think I am going to wait

 

开云体育

?

There it is but use at your own risk. I have had no problems without it but you can never tell. ?

?

Outlook LT Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

?

?

From: [email protected] <[email protected]> On Behalf Of Gary W9TD via groups.io
Sent: Thursday, March 13, 2025 8:47 AM
To: [email protected]
Subject: Re: [DXLab] Windows 11 fiasco --I think I am going to wait

?

I think the issue here is not Windows 11 per se, but the latest major release, 24H2, is known to be buggy on some hardware. It is advised to not upgrade to 24H2, stay on 23H2. There is an app , InControl that will effectively block the 24H2 update from being downloaded and installed. When MS fixes the issues, you run InControl again and lift the block.

Gary

W9TD

?


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop
Re: Windows 11 fiasco --I think I am going to wait

 

Thank you all.? I think that I have been over-thinking this change.? I have to upgrade my computer due to age and capability and will use the advice here to do so.? I will be careful but will upgrade to Win11 with the new PC.??

73,

Guy K4CNF

On Thu, Mar 13, 2025 at 9:47?AM Gary W9TD via <w9td=[email protected]> wrote:
I think the issue here is not Windows 11 per se, but the latest major release, 24H2, is known to be buggy on some hardware. It is advised to not upgrade to 24H2, stay on 23H2. There is an app , InControl that will effectively block the 24H2 update from being downloaded and installed. When MS fixes the issues, you run InControl again and lift the block.
Gary
W9TD
?
Re: Windows 11 fiasco --I think I am going to wait

 

I think the issue here is not Windows 11 per se, but the latest major release, 24H2, is known to be buggy on some hardware. It is advised to not upgrade to 24H2, stay on 23H2. There is an app , InControl that will effectively block the 24H2 update from being downloaded and installed. When MS fixes the issues, you run InControl again and lift the block.
Gary
W9TD
?
Re: Windows 11 fiasco --I think I am going to wait

 

开云体育

One data point - I updated from W10 to W11 about a year ago without issue here.? No reinstall or other complications encountered with any of the ham or other apps on the machine.

73/jeff/ac0c
alpha-charlie-zero-charlie
On 3/12/2025 2:42 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
I got the impression that this sounded like a computer issue, not an OpSys?issue. However, like many others who are working with Win 10 and DXLab I am looking at upgrading computers and systems to avoid the consequences of losing support.? (I lost a lot of my log with the end of XP due to a virus.)? So I am looking at moving to Win11 with my?DXLab intact.? Can you advise what we need to do or look out for in making that transition?but keeping our DXLab programs working correctly?? I know there are folks out there who have made the move to Win11 and have not reported any issues with DXLab operations.? I admit that this has got me concerned.? I'm not a computer guy (no pun intended) and would?really appreciate your comments and advice.
+ I cannot provide advice without turning this into a Windows Support Forum, but I can share my experience:

1. I have no experience upgrading a PC from Windows 10 to Windows 11, as my Windows 11 systems were pre-installed on new hardware. Since I first began using Windows in 1985, I have always upgraded to a new version by copying all critical files to external storage media, erasing the contents of the C: drive, installing the new version of Windows, and then restoring all critical files from that external storage and re-installing my applications. I don't know if Microsoft's "Windows version upgrade" mechanism has improved to the point where it is trustworthy, and thus I defer to those here with this experience. Step-by-step instructions for DXLab applications are here:



2. Windows 11 version 23H2 is stable. I have not encountered problems when running Adobe, DXLab, Google, or Microsoft applications on this version.
?
3. I have Windows 11 configured to inform me when a new Windows Update is available, but to not automatically download and install it; Perplexity can provide step-by-step instructions for doing this.

4. When I am informed that a new Windows Update is available, I direct Perplexity to report any adverse side effects that have been reported; until there are no relevant problems with an update, I hold off.

5. None of the Security Intelligence Updates for Microsoft Defender Antivirus that I have applied have caused trouble.

Perplexity is a free AI search engine that I have come to rely on for Windows management, and many other subjects, from home repairs to cosmology;? it cites its sources, which makes it easy to check the accuracy of its response and obtain additional information. I have no affiliation with the company.

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ
?


? ??





?
Re: Invalid administrative subdivision errors

 

QRZ.com shows that KR1STA is a vanity call with a Hawaii
address. It also shows a previous call of WH6DEY so there
is a rather good chance that she's in Hawaii.

Have you imported the QSOs already - if so simply change
Code/DXCC/Entity in the existing QSOs to KH6. If not,
edit the ADIF file as explained below and import it.

73,

... Joe, W4TV

On 2025-03-12 9:31 PM, Richard Hill via groups.io wrote:
Rich, thank you. I believe she was in Hawaii. This was some 23 years ago,
so memory may be lacking... but this was one of my first contacts with
Hawaii. She was a young ham, in a contest, doing much better than me,
grin. I'll check and figure out how to fix this.
Thank you!
Rich, NU6T
On Wed, Mar 12, 2025, 5:09?PM Joe Subich, W4TV via groups.io <lists=
[email protected]> wrote:


Your ADIF file identifies KR1STA as Country=USA.

To make <CNTY:8>HI,Kauai valid, change the DXCC (prefix) for those
QSOs to KH6, Change "Code" to 110 or change "Entity" to Hawaii (if
you change one the other two will change automatically).

If you want to edit the ADIF before import, change <Country:3>USA
to <Country:6>Hawaii for the two QSOs.

73,

... Joe, W4TV


On 2025-03-12 7:55 PM, Richard Hill via groups.io wrote:
I'm trying to import ADIF files into DXKeeper. I have errors I need to
fix for a single QSO with Hawaii that shows " <CNTY:8>HI,Kauai ". I've
been trying to learn how to properly fix this error without success. Any
help will be appreciated. What have I done wrong?

The original CQ Magazine references are no longer available. County
Hunter seems to have taken over. I suspect there is an authoritative
source I have not found.

ERROR summary: <CNTY:8>HI,Kauai
References:


*

My error notices:
1. invalid primary administrative subdivision: HI:
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB
2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>

2. invalid secondary administrative subdivision: HI,Kauai:
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB
2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>

Thanks
Rich, NU6T
Re: Invalid administrative subdivision errors

 

Rich, thank you.? I believe she was in Hawaii.? This was some 23 years ago, so memory may be lacking... but this was one of my first contacts with Hawaii.? She was a young ham, in a contest, doing much better than me, grin.? I'll check and figure out how to fix this.

Thank you!

Rich, NU6T


On Wed, Mar 12, 2025, 5:09?PM Joe Subich, W4TV via <lists=[email protected]> wrote:

Your ADIF file identifies KR1STA as Country=USA.

To make <CNTY:8>HI,Kauai valid, change the DXCC (prefix) for those
QSOs to KH6, Change "Code" to 110 or change "Entity" to Hawaii (if
you change one the other two will change automatically).

If you want to edit the ADIF before import, change <Country:3>USA
to <Country:6>Hawaii for the two QSOs.

73,

? ? ... Joe, W4TV


On 2025-03-12 7:55 PM, Richard Hill via wrote:
> I'm trying to import ADIF files into DXKeeper.? I have errors I need to fix for a single QSO with Hawaii that shows " <CNTY:8>HI,Kauai ".? I've been trying to learn how to properly fix this error without success.? Any help will be appreciated.? What have I done wrong?
>
> The original CQ Magazine references are no longer available.? County Hunter seems to have taken over.? I suspect there is an authoritative source I have not found.
>
> ERROR summary: <CNTY:8>HI,Kauai
> References:
>
>
> * ?
>
> My error notices:
> 1.? invalid primary administrative subdivision: HI:
> <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
>
> 2.? invalid secondary administrative subdivision: HI,Kauai:
> <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
>
> Thanks
> Rich, NU6T
>
>





Re: Windows 11 fiasco --I think I am going to wait

 

Most people don't understand that MS expects each hardware and software vendor to test each new release of Windows on their product(s)? Some vendors do a good job and some do not which is why some people have very few issues with Windows updates and some have more problems. I built and managed the Windows test lab at IBM for 8 years during Windows NT and Windows XP.?
?
Bob AF9W
DXLab user since 2011
Re: Windows 11 fiasco --I think I am going to wait

 

TNX

Guy K4CNF

On Wed, Mar 12, 2025 at 6:10?PM W0MU via <w0mu=[email protected]> wrote:

I have been using Windows 11 since it came out and it is a solid if not more so than 10.? I have no idea what people do to their computers that give them so much issue.? Never upgrade always start fresh and reload.

W0MU

On 3/12/2025 2:54 PM, james aprile K5KND via wrote:
Thanks for the reply Dave......yeah not trying to do a support forum...no refund offered by the company strict policy....In any event I will buy another computer but not now. The Win 11 platform is not stable even when the guys have working computers! I read this forum and use it daily. I think I will stay with Win 10 and pay the fee while MS figures out how to write decent operating system software.
?
My apologies and this will be my last post re this matter....Jim K5KND
Re: Invalid administrative subdivision errors

 

Your ADIF file identifies KR1STA as Country=USA.

To make <CNTY:8>HI,Kauai valid, change the DXCC (prefix) for those
QSOs to KH6, Change "Code" to 110 or change "Entity" to Hawaii (if
you change one the other two will change automatically).

If you want to edit the ADIF before import, change <Country:3>USA
to <Country:6>Hawaii for the two QSOs.

73,

... Joe, W4TV

On 2025-03-12 7:55 PM, Richard Hill via groups.io wrote:
I'm trying to import ADIF files into DXKeeper.? I have errors I need to fix for a single QSO with Hawaii that shows " <CNTY:8>HI,Kauai ".? I've been trying to learn how to properly fix this error without success.? Any help will be appreciated.? What have I done wrong?
The original CQ Magazine references are no longer available.? County Hunter seems to have taken over.? I suspect there is an authoritative source I have not found.
ERROR summary: <CNTY:8>HI,Kauai
References:


* ?
My error notices:
1.? invalid primary administrative subdivision: HI:
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
2.? invalid secondary administrative subdivision: HI,Kauai:
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
Thanks
Rich, NU6T
Re: Invalid administrative subdivision errors

 

The DXCC code is for the continental USA (not Hawaii), the CONTinent code is NA (not OC), the CQ zone is 4 (not 31), the ITU zone is 7 (not 61), and the COUNTRY field is USA (not Hawaii). All of those are incompatible with the State (HI) as well as the county. If KR1STA was really in Hawaii, then all of these fields need to be corrected..
?
73,
Rich VE3KI
?
On Wed, Mar 12, 2025 at 07:55 PM, Richard Hill wrote:

I'm trying to import ADIF files into DXKeeper.? I have errors I need to fix for a single QSO with Hawaii that shows "<CNTY:8>HI,Kauai".? I've been trying to learn how to properly fix this error without success.? Any help will be appreciated.? What have I done wrong?
?
The original CQ Magazine references are no longer available.? County Hunter seems to have taken over.? I suspect there is an authoritative source I have not found.
?
ERROR summary:??<CNTY:8>HI,Kauai
References:
https://adif.org/315/ADIF_315.htm
https://adif.org/315/ADIF_315.htm#Primary_Administrative_Subdivision
? ?* ?https://countyhunter.com/counties.htm
?
My error notices:
1.? invalid primary administrative subdivision: HI:?
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
?
2.? invalid secondary administrative subdivision: HI,Kauai:?
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
?
Thanks
Rich, NU6T
Invalid administrative subdivision errors

 

I'm trying to import ADIF files into DXKeeper.? I have errors I need to fix for a single QSO with Hawaii that shows "<CNTY:8>HI,Kauai".? I've been trying to learn how to properly fix this error without success.? Any help will be appreciated.? What have I done wrong?
?
The original CQ Magazine references are no longer available.? County Hunter seems to have taken over.? I suspect there is an authoritative source I have not found.
?
ERROR summary:??<CNTY:8>HI,Kauai
References:
https://adif.org/315/ADIF_315.htm
https://adif.org/315/ADIF_315.htm#Primary_Administrative_Subdivision
? ?* ?https://countyhunter.com/counties.htm
?
My error notices:
1.? invalid primary administrative subdivision: HI:?
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
?
2.? invalid secondary administrative subdivision: HI,Kauai:?
<BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor>
?
Thanks
Rich, NU6T
Re: DXKeeper: New County Lookup

 

Hello I am the VP of MARAC and have been involved with MARAC for years and years.? I am happy to help however needed.

MARAC has indeed started to issue own USA-CA award since CQ is essentially defunct.? We have done everything in our power to keep the Award numbers the same and continue forward, not that this has much to do with DX Keeper.

If you are serious about County Hunting and the MARAC Awards, join the club and get our logger which was designed specifically for our awards.

Mike W0MU

On 3/11/2025 4:33 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

TQSL applies some of the same "fuzzy matching" for. County names. One other is to change "ste." to "Saint". I'm going to steal some of Dave's ideas as well, as that's valuable experience.

+ I've sent you all of DXKeeper's U.S. County spelling correction code.

73,

Dave, AA6YQ
481 - 500 of 228573