I've experienced this as well. What really helped me was:
use a fresh database for the contest
set a shorter spot timeout
set up strict spot filtering on the node you're connected to
use WinKey for cw
Barry N1EU
On Sat, Dec 27, 2014 at 10:16 AM, Rick - DJ0IP / NJ0IP <Rick@dj0ip.de>
wrote:
> Tell me about it.
> Last year it lamed my computer to the extent that it would not even send
> code properly.
> I had to send the exchanges myself throughout the entire contest.
>
> This year I modified the process priorities in the Task Manager, giving the
> contest software a higher priority than the telnet stuff. It worked OK
> then.
>
> 73 - Rick, DJ0IP
> (Nr. Frankfurt am Main)
>
>
> -----Original Message-----
> From: TenTec [mailto:tentec-bounces@contesting.com] On Behalf Of Barry
> N1EU
> Sent: Saturday, December 27, 2014 10:49 AM
>
> The contest logging program is a high cpu user if it's connected to the
> hyperactive spotting network during a major dx contest.
>
> Barry N1EU
>
> _______________________________________________
> TenTec mailing list
> TenTec@contesting.com
> http://lists.contesting.com/mailman/listinfo/tentec
>
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|