If only I had your problem ...
Well, looking at the other responses here's what I think I'd do:
1. Setup an "extra" logging computer on the network that just does the
saves every 10 (or 20 or whatever) QSOs that is not involved with actual
contesting. No big deal if it takes a while.
2. Set the run computers up for a very large autosave interval and then
do it on demand once in a while when things get slow (if they do).
Marty Tippin wrote:
> We used Writelog 10.39C last weekend in the ARRL DX SSB contest
> Multi-Two effort from PJ2T. Computers ranged from a 450MHz Pentium II to
> a 450 MHz Pentium III. Overall, the program worked great as it usually
> does.
>
> However, there was a nagging problem which grew more obnoxious with
> every QSO: After we reached somewhere around 2000 Qs, saving the log
> started taking longer and longer, up to about 10 seconds at the end of
> the contest when we had 12500 contacts in the log. During the time the
> log was being saved, the computer was worthless -- any Auto CQ would
> hang the radio in transmit, and you couldn't type anything in the call
> entry window. Basically, we were forced to abandon the use of the DVK
> when we thought an autosave might be coming up, and had to "fill"
> airtime while waiting for the machine to become usable again.
>
> The problem was most evident on the Pentium II machine, and generally
> not an issue at all on the PIII box.
>
> Anyone had similar experiences? Solutions? Suggestions?
>
> Thanks
>
> -Marty NW0L
> martyt@pobox.com
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
>
--
Bruce Ferry, AK8B
|