DXCC question

[LA0FA]

RumLogNG consequently recognizes HC2AO/8 as Ecuador while it is Galapagos (HC8). Also Clublog recognises it as HC8. I can't find it in the invalid or exception list either.
In RumLog Classic its OK.
73 LA0FA

[DL2RUM]

That's a logical problem in the software. Same for UA or EA. I have to change the code.
As workaround you could add the call sign in your private exception list in the Preferences under the DXCC tab.

[LA0FA]

I have introduced HC2AO/8 with a valid timeperiod in the DXCC exception list - for a new QSO it is correctly recognised as HC8.
But I can not change to correct DXCC when editing a QSO already in the log. When I converted/imported the classic DB i saw the
QSO was corrected wrongly to HC - and now I am stuck with it. Any advise ?
73 LA0FA

[DL2RUM]

Two ways are possible:

• Double click the QSO to bring it into the Edit mode
• Change the call sign by adding a letter or deleting something
• Revert the changes
• This should recalculate the dxcc
• Save

Another way:

• Select the affected QSO
• Use Menu-->Logbook-->Recalculate DXCCs

I should add an option to do this task automatically after adding an entry into the exception list.

Further I optimized the dxcc entity recognition for portable call signs like this for:

• UA, UA2, UA9
• TI, TI9
• EA, EA6, EA8, EA9
• HC, HC8
• 3B7, 3B8, 3B9
• 9M2, 9M6
• ZL, ZL7, ZL8, ZL9
• and some more

This will be available in the next release.

[LA0FA]

Thanks - works perfectly !!
73 LA0FA/Matthias

[n1ho]

Thank you for the suggestions on how to fix my log, because I did discover
a potential bug - I had a QSO with a guy in North Carolina whose call is
KG4xyz, and RUMlogNG (after converting the log from Classic to NG) listed
him as being in Guantanamo Bay.

The problem is, while the prefix for Guantanamo Bay is KG4, only those KG4
call signs with two letter suffixes (e.g., KG4XX) are there; the FCC issued
KG4 + 3 letters to folks living in the southeastern US (e.g., KY, NC, SC, etc.)
as part of the regular stream.

So far, that's my only glitch with RUMlogNG - thank you for all of the hard work
that you've put into it, because it's a great program and I love it!

Very 73 de N1HO

[DL2RUM]

Tnx for pointing me to KG4. It will be corrected in the next version.