Ed: Yes, I've been trying to download the full version of 10.64D this afternoon, and getting the same message. 73, Jeff K8ND _______________________________________________ WriteLog mailing list Writ
Bob: I have, and I do. The web server message, cited by Bob below, is unrelated to having a current license. 73, Jeff K8ND _______________________________________________ WriteLog mailing list WriteL
I am testing the current version of Writelog for use in the upcoming CQWW 160 CW Contest, and have an unexplained problem. The radio assigned is my K3, and the program is correctly displaying and fol
All: After playing with this issue for over an hour and having it behave as described below, I saved the log and re-started Writelog, and the problem vanished! If anyone has speculation as to why thi
The current version of Writelog (10.69d) includes a new packet window for Skimmer, to allow connecting to a packetcluster *and* a Skimmer simultaneously. For Skimmer: "Window -> Incoming-only Packet
The Writelog Cabrillo file generation in Writelog v10.69D is broken for Multi-Multi entries. I don't know if this is also true of the newest version (10.71C?). The PJ2T log was rejected by the ARRL r
I am tracking down a problem at PJ2T. We have used Winkeyer USB devices with Writelog for several years, and suddenly cannot get the Winkeyers to work. This is an issue on three stations where they w
No longer than 15 minutes after posting, I found the solution here. The good news (to me!) is that I have resolved the problem. Seems that when the batteries were removed, the battery jumper was not
G'day Rick: No, the Winkeyer USB is an integrated solution. It uses the WK2 chip, and the USB is integrated onto the single board. BTW, the newer ones have no battery jumper to confuse the dozey tour
Has anyone else experienced Writelog packet windows being left running after Writelog is terminated, and which will not die when clicking the "X'? At PJ2T, we installed the Writelog 10.73D release on
G'day Art: You've probably already figured this out, but there is a check option: "View > Lock docked windows". Un-check it, and the windows will move. It's a good idea to lock windows when you are
I received an inquiry about Writelog behavior that I cannot answer. Google and searching the reflector archives has not found an answer. "During the few seconds that the callsign is being entered, a
G'day Ed: I was reading that in the docs when your email arrived: thanks! Any idea why it would work one way on one PC and differently on three others? All are running the same version of Writelog (v
We experienced a couple of network issues at PJ2T during CQWW CW, and the Writelog log that resulted when things settled back out has several cases of groups of QSOs out of chronological order. Is
Thanks, Ed! Nailed it! BTW, it was not the networking issue (exclusively) that presented the problem. It appears that one of our four station Windows 7 PCs on the network got out of time synch. They
Thanks for the clarification, Randy! There is something primal acting when one sees that the log is out-of-order, something which must be corrected. It is fixed. 73, Jeff K8ND The good news is
I'm using Writelog v11.09b for my casual operating as PJ2/K8ND. I started my log running Writelog 10.85A as 'DXpedition Mode' (in order to track QSOs by band and mode). During my stay here, I upg
Just prior to the CQWW 160-Meter CW Contest, I upgraded the PJ2T computers from v11.14 to v11.18c. At the beginning of the contest, we discovered that pressing the 'Ins" key did not send the callsi
I recently upgraded to version 12, and have been unsuccessful in adding 'AutoSaveCount=100' to the configuration. I have Exported, edited to add the line in the [Configuration] section, and imported
Don,OK, I will remove the entry at the next opportunity and test.However, this does not answer why adding the entry did not change the behavior of prompting every 20 QSOs.There is only one 'AutoSaveC