WriteLog
[Top] [All Lists]

[WriteLog] writelog sticks with a lot of qsos

To: writelog@contesting.com
Subject: [WriteLog] writelog sticks with a lot of qsos
From: Kostas SV1DPI <sv1dpi@otenet.gr>
Date: Wed, 30 Sep 2015 00:27:25 +0300
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
I have noticed that writelog sticks momentarily sometimes. I have noticed it happening after 1000 qsos in the log. It happens on cw and rtty. On cw while I hit the function key, I am waiting for 1-2 seconds to start sending. On rtty it starts keying something like RY for a while and after 1-2 seconds the message starts. It happens after some hours. A fresh reboot corrects the problem for a while but it happens again. The result of this is that I use the wintest the last time for cw contests but I prefer writelog. The biggest problem is that I noticed it on rtty also the last time...
Is anyone other who has noticed this behaviour?
The keying device is microham in the first radio and winkey plus homemade interface to the 2nd radio (I don't think the problem is in hardware as it works fine with wintest and dx4win). Computers are in network and I use the 11.28 version but I have noticed it in all of the last versions. Computers in the shack are duo-core with 2gb memory and windows 7. A 3rd laptop is used for backup and runs the clusters. I can not reproduce it in my home computer. I believe this is why the computer is not so many hours on or the clusters spots are no so many. My first thought was that heavy spots from the clusters was the cause but on rtty I had not skimmer on and the spots were much lower. I talked it with a friend of mine who runs a much older version of writelog and a new computer with lot of memory and he has noticed it also. This is why I am asking for comments...

73 Kostas SV1DPI


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>