[WT-support] CQWW CW issue

[Matt IZ3EYZ]

Unfortunately (as I expected) the 0hz thing doesn't solve at all the problem 
which comes up using RBN.
I installed and used 4.7 dev during last cqww cw and due to the fact several 
skimmers actually spot S&Ping stns it means MANY mult spots are soon 
overwritten in a matter of few seconds. :-((
Each op here devoleped his own strategy:
a)writing down calls and qrgs on paper
b)putting them into bandmap (but they are still overwritten)
c)storing qrg's into rtx memories
d)making sh/dx xyz to recall a certain call

All of above is far from ideal.

I just hope developers someday will understand the real need of introducing 
a new feature or eventually remove the overwriting (and keep it just for the 
same call spots )thing as ES5TV suggested.
Looking at MS, M2, MM, SOA scores it can be seen how an automatic spotting 
system like RBN brought mult numbers to another level. Actually I feel those 
800 dxcc scores could be improved even more!

73

eyz


----- Original Message ----- 
From: "Peter" <pc2a at pi4cc.nl>
To: <support at win-test.com>
Sent: Monday, November 29, 2010 4:08 PM
Subject: Re: [WT-support] CQWW CW issue


> Mikael Larsmark schreef:
>> Hello
>>
>>
>>
>> I hope that some day you will understand how much the need to be able to
>> shut down the spot bandwidth. Maybe its because you lads don't work much
>> CW Contests (?) but this is a MAJOR issue.
>
> This is fix in the latest  dev version (4.7)
> Worked great here with the spot wide set to 0 (zero) hz
>
> Ppeter
> PC2A
> www.pi4cc.nl
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
> __________ NOD32 5649 (20101125) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>