During the WW CW weekend I used WL for the first time in a multi-op environment. On rare occasions one could be confronted with the need to re-boot a computer in the middle of a contest. In our multi
Just to confirm what Eric said, my experience was similar durig this past CQWW CW where I ran WriteLog for the first time in a network configuration. At first, it worked perfectly, but then, my main
given this problem. I expect several will chime in to defend WL in a networked environment. My experience is limited to 2 CQWWRTTY contests with 2 networked computers. Computer A is recent with WIN2
Guys, While I, too, would like to see a more streamlined process, it's not THAT bad. For example, after my fiasco of setting up a WPX log by mistake, I shut down at 0004Z to create new CQWW logs from
Thanks for taking the time for your detailed response John. I do have a couple of questions / comments below: That's understandable, and expected. However, if I'm going to set up a network of say, 8
And don't forget it does a poor job of remembering configuration, like font setting, cluster tings, etc. At least it does for me and I would like others to check that to see if I am alone here? Resta
Well, a little better than a guess, but I think you nailed the problem as above. Some screen savers simply do not scan the keyboard or mouse for an interrupt ( back to business ) after a certain peri
am Sorry Gil I disagree with you mate !!! I have never had that problem happen at all Gil. Or maybe I am just one of those "saddo's" that actually reads the instructions front to back ;-) Though I o
I agree here and that is why I use it instead of the former TRLOG. It just is that it has the problem I stated in a previous post that it does not remember those settings. You have to CHANGE the fon
SORRY for posting this. It was meant as a private reply . To avoid the somewhat arrogant reply I did not leave it here, sorry again. _______________________________________________ WriteLog mailing l