toggle quoted messageShow quoted text
One possible explanation for KP and KH calls that don't show up as expected is the country file. If (for instance) KP2ABC is licensed to a stateside (non-VI) address, the country file may be overriding the prefix-based assumption that KP2ABC is in VI because the license is issued to a stateside address.
That's the flip side of the feature that tells your logging program that KV4FZ is in KP2 and KG6DX is in KH2 even though those are plain vanilla stateside calls according to the current FCC rules.
On Mon, Nov 18, 2019 at 2:43 PM Tim Shoppa <tshoppa@...
Mike, historically N1MM has never worked for me in SS or NAQP in showing what are trivially new Canadian mults.
Like you point out it does the wrong the other way too. Like you, even after I had worked VY1AAA, it kept on showing VY1CO as a new mult. There were other Canadian calls that were trivially new mults that don't get lit up.
After I get the callsign into the entry window and space or tab over to the exchange, it lights up as a mult accurately.
I think this is some bad interaction between history file and the trivial callsign to mult mapping but I never have figured it out. Just lived with it for many many years now.
On Mon, Nov 18, 2019 at 1:23 PM VE9AA - Mike <ve9aa@...
I didn't work the SS SSB this past weekend, but did work the SS CW and did unlimited, the "83Q/83Mults" thing.
Pretty much all I did was CTRL-ALT-UP/DN arrows and barely tuned around at all and it worked perfectly at that time.
The only issue I found in SS CW was that , even though I had already worked VY1AAA early on, it kept reporting another VY1 as a mult.
Since it was only one stn, it was easy to ignore.
The jump to the next mult thing worked fine how (in SS CW)...