Set the autosave feature in WriteLog to a very large number (100, 1000,
5000) and save the log manually (ctrl S) during band changes. Since
WriteLog creates a backup file with every qso and there is a duplicate log
on the second computer there is very little risk of loosing data.
I experienced the same problem with over 2000 Qs in my PI 133 laptop that we
ran M2 this weekend. It didn't seem to bother the DVK but it reeked havoc
on the CW keying during the ARRL CW contest.
73,
Zev N2WKS
-----Original Message-----
From: Marty Tippin [mailto:martyt@pobox.com]
Sent: Wednesday, March 05, 2003 5:31 PM
To: writelog@contesting.com
Subject: [WriteLog] Save is Slow with large logs
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
CONFIDENTIALITY NOTICE: This communication and any attachments are
confidential, and are only for the use of the intended recipient. If
you have received this transmission in error, any disclosure, copying,
distribution or the taking of any action in reliance upon this
communication is strictly prohibited. If you have received this
communication in error, please contact the sender immediately and
delete the original message. Thank you.
|