There are clearly some unexplained differences between experiences here, and
from my personal perspective they are *not* related to computer speed or RAM.
Steve experienced the problem as described, and I *always* find it a problem
on CW over 2000 QSOs.
The difficulty is aggravated by the fact that setting the AutosaveCount=-1
does *not* work. This was validated by Steve and myself from separate stations
in the middle of CQWW SSB such a problem was it. Wayne N.B.
I presently have the count set to 100, and that is a workaround, since I am
then simply prompted to save after 20 QSOs. I can then execute a Ctrl S when
convenient.
I first experienced this problem when using a Pentium I 200Mhz with 64Mb of
RAM, and was told that a faster processor and more RAM would solve it. This
has proved *not* to be the case and even the present 750Mhz Duron with 256Mb
RAM is equally as slow.
I re-iterate Steve's comment that this is a serious problem for serious
contesters; just wish I were one of them!
73
Clive
Dick Green wrote:
> 1) What value did you set for AUTOSAVECOUNT, 2) are you sure you typed the
> parameter name correctly, and 3) what was the CPU speed and memory of the
> machine(s) in question. At 8P8P we did over 10,000 QSOs, sometimes at
> 10-minuyte rates approaching 500/hr, and the autosave was never a problem.
> It was more visible later in the contest, but not slow enough to matter. Our
> autosave count as set to 20. One CPU was a 500 MHz PIII and the other was a
> 700 MHz PIII. I've experienced the slowdown on a 100 MHz PII (or maybe it
> was a PI), but Wayne later did something that sped things up. I recall some
> posts complaining that the slow save was back, but now I use machines that
> are so fast it doesn't matter.
>
|