WriteLog
[Top] [All Lists]

Re: [WriteLog] How often during a typical contest weekend do youhave to

To: "W. Wright, W5XD" <w5xd@writelog.com>, <writelog@contesting.com>
Subject: Re: [WriteLog] How often during a typical contest weekend do youhave to restart WriteLog?
From: "Georgens, Tom" <Tom.Georgens@netapp.com>
Date: Sun, 17 Jul 2011 17:30:34 -0700
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Wayne

It has been years since I have had a problem with Writelog during a
contest.  I generally operate with two networked PC's running Writelog.
The main PC does the logging, rig control, and talks to the W5XD keyer
for SO2R.  The other PC has a copy of the log, records the audio, and
displays multipliers.  Networking has been nearly effortless and very
resilient since the TCP/IP option became available.

When I was running Win98, Writelog would almost never last an entire
contest without needing a reboot.  Once I moved to Win2K, and later to
WinXP, it has been flawless.  My suspicion always was that networking
was the source of the disruptions.

Hopefully that helps.  For completeness, while you asked about
networking, there is a bunch of other functionality that I never use
(packet, Band maps, digital modes, morse decoding, PC CW, etc.) that may
have issues that I have never seen.  I also have never used Win7 or
Vista.

There are a few features I wish Writelog had, but reliability has ceased
to be a concern for me.  I tell people that I have not lost a single QSO
due to Writelog for at least 5 years. 

73, Tom W2SC 8P5A 



-----Original Message-----
From: W. Wright, W5XD [mailto:w5xd@writelog.com] 
Sent: Saturday, July 16, 2011 3:21 PM
To: writelog@contesting.com
Subject: Re: [WriteLog] How often during a typical contest weekend do
youhave to restart WriteLog?

All:
Thank you for all the responses. My poll was not well designed enough to
derive much in the way of quantitative metrics. Here are the only
numbers I
can back up from my emails received:

44 answers
roughly 1/2 said "never" or "48"
worst case among the answers was an estimated 12 hours, which I assigned
to
3 of the responses. (specifically "3 times per 48 hrs" which I will
translate to "mean time to failure" by dividing 48 hours into 4
trouble-free
timeperiods of 12 hours each)

How I got the numbers:
Counting all the answers I could find, there are 44 answers. My question
was
poorly formed, so some answered only directly to me, some only to the
reflector, and some to both, so I could have introduced an error just by
collating. I don't think it is meaningful to try to assign an average or
anthing other the best case and worst case, which I present above.

My original question to the reflector failed to ask whether WL
networking
was being run. (Specifically, "Setup/Link to Network"). Do users of that
feature have more problem with forced shutdowns?

Thanks,
Wayne, W5XD

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/
_______________________________________________
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>