[Dxspider-support] sh/dxcc not showing DXCC

[Dirk Koopman]

On 21/01/2023 18:55, Kirill Ryabov via Dxspider-support wrote:
> Dirk, it doesn't depend on prefix

Well, it does, but only to determine the country code so that it can 
then do the query with that code.

>
> sh/dx dxcc r5
> R5ACQ de R5ACQ-1 21-Jan-2023 1838Z dxspider >
>    7149.9 RW1F        21-Jan-2023 1833Z <SV2SKD>
>    7150.6 RW1F        21-Jan-2023 1832Z 73 tnx <PD0NHM>
>    7122.0 R3ZZ        21-Jan-2023 1831Z HADX CONTEST <RA3CW>
>  144174.0 RD6F        21-Jan-2023 1829Z <TR> FT8 -20 dB 1399 Hz <UA4AQL>
>
> OK, it shows Eu RU calls but still does not show the DXCC name.
> In old version of DXSpider, for example 1.55 build 249 it was like this
> sh/dxcc j8nki
> Prefix: J8 Dxcc: 94 (St-Vincent-J8)
>            Dxcc: 94 (The-Grenadines-J8/G)
>            Dxcc: 94 (St-Vincent-J8/V)
>  21076.0  J88CU       20-Jan-2023 0107Z <KD5JGA>
>  14254.0  J8NKI       19-Jan-2023 1710Z  IOTA NA-025  POTA J8-0016 <S55G>
>  14254.0  J8NKI       19-Jan-2023 1708Z  POTA J8-0016 <OH6GAZ>
>  14254.0  J8NKI       19-Jan-2023 1657Z  POTA J8-0016 <K4CAE>
>

Having not touched this for a while (git diff is very useful here) I 
realised that I had a drastic rewrite of the show/dx command - which was 
started in 1997 - to use the filtering subsystem (not started until 
1999),  to running via, much improved, filtering system in 2020. The 
only issue here is that sh/dxcc does something extra that the filter 
system can't do (what is effectively a sh/prefix). I can add that to the 
show/dx command for the next release.

> And one more:
> when I try to see who was spotting me with command
>
> sh/dx r5acq
> R5ACQ de R5ACQ-1 21-Jan-2023 1841Z dxspider >
>
> it returns nothing.
> But I am sure there were some spots of my call.

I did a show/dx R5ACQ and got back two spots from December last year. On 
the other hand, when I do a sh/dx by R5ACQ, I can see you have been a 
very busy boy with a screenful of spots just today.

>
> even more
> When I try to login to my node or, for example, to pi4cc.nl with my 
> call (using Windows telnet clien) I always got this:
>
> login: r5acq
> Sorry R5ACQ is an invalid callsign

Windows telnet was always a shitty, non-standards compliant program. I 
see that in Win 10, I have google how to find it, then go through three 
screens to check a box to enable it and then wait for Windows to reboot. 
But while I am waiting, I shall speculate that the same old problems 
with it trying to apply telnet protocol to ports other than 23 is at 
work here - despite that the relevant RFC specifically states that 
telnet protocol shall only be used on port 23 and switched off for any 
other port. I'll let you know when it's finished "updating" whether this 
is still the case.

Sadly I have to report that it now works just fine for me, both my local 
machine and on a couple of others that I maintain, all running the 
latest mojo. It even "beeps" in a pleasant, melodious way (which would 
still get very annoying, just less quickly).

This is GB7TLH located on a computer somewhere or other.
Please treat this as your own.
Have fun.
login: r5acq
Hello Kirill, this is GB7TLH in Midhurst, West Sussex
running DXSpider V1.57 build 483
Capabilities: ve7cc rbn
************************************************************
* please do not use this node - use GB7DJK instead *********
* this is test software and may not be connected   *********
************************************************************
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   28333.1 N6JSO       21-Jan-2023 2107Z USB                          
<WA3AER>
    7020.0 EC5K        21-Jan-2023 2107Z CW HA DX Contest             
<UA4WAU>
   14313.0 N6GR        21-Jan-2023 2106Z                               
<K3WJV>
   21399.4 W0BM        21-Jan-2023 2106Z                                
<N3NR>
   21286.9 TI2VV       21-Jan-2023 2106Z                              
<KC3TAU>
-------------------------------------------------------------------------------
Callsigns connected to GB7TLH
G1TLH-2      R5ACQ
-------------------------------------------------------------------------------
Date        Hour   SFI   A   K Forecast                              Logger
21-Jan-2023   21   209  18   3 No Storms -> Minor w/R1               <AE5E>
-------------------------------------------------------------------------------
Date        Hour   SFI   A   K Exp.K   R SA    GMF   Aurora Logger
21-Jan-2023   21   218   7   3     0 197 act   qui       no <DK0WCY>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Nodes: 2/433 Users [Loc/Clr]: 2/5130 Max: 1/5130 - Uptime:  14h 26m 36s
R5ACQ de GB7TLH 21-Jan-2023 2107Z dxspider >
DX de K3QH:      21324.5  KI0R USB                            2107Z
DX de PU5YSV:    21075.3 9H5TB                                       2107Z
DX de NP4DE:     24919.0 W7VOA                                       2107Z
unset/DX de HI3MPC:    14228.0  NJ4P USB                            2107Z
beep
Beeps are now off
R5ACQ de GB7TLH 21-Jan-2023 2107Z dxspider >
DX de W3LPL:     18082.0  K3Y/KL7      Heard in CA                    2107Z

>
> If I use PuTTY it is all ok and I got no errors. 

No surprises there, IIRC it is mentioned in the original DXSpider User 
Manual that it is the preferred option. Advice which I would stick to if 
asked.

Hope this helps

73 de Dirk G1TLH