switch I took a close look at this and can't duplicate exactly what's described in the posting--it was not weird, and it was very consistent, but I did find one thing that was consistently wrong. If
There have been several reports of the "File Web Update Data Files" not working. I believe all of these are due to space characters in the file name (or in the directory name containing the file). Th
I'm pretty sure that the files are getting updated and that the error message refers to a problem restarting Writelog. Dick, I found the file. But Writelog did not extract any of the updates from it,
I am interested in the MK-1100, but I need a better understanding of its operation than I could get from the website description. I will refer to connector labeling that is shown on the website proto
and I server 2000 The first thing to change is the Tomcat version. The WL server was built and tested with 3.2.4, which you can still get here: http://archive.apache.org/dist/jakarta/tomcat-3/archiv
All, Ron asked me to post this. He has unexpectedly been admitted to the hospital this week. He is hoping to be out Friday, but will certainly not make the trip to Dayton. Your good news is that, to
1. I clicked this button. (or I typed this) (or I edited the INI to say this) 2. I opened the RTTY screen using <however you did it> 3. A box appeared on my screen that said <whatever> This is my sec
a window All, This problem with RTTY and CW shows up only in version 10.49 and only if you have a new registration code (one that you received since mid-September 2004). The problem actually is in t
After the very first production run of the keyer, the parts driving the PTT outputs (and CW outputs for that matter) were replaced. Both were photo-darlingtons, but the newer part was empirically sho
The SHIFT+Fn recording feature did not work in 10.47 through 10.50. If you have 10.50, you can patch it with this fix: http://www.writelog.com/Downloads/WriteL1051a_test.zip Instructions: With WriteL
All, I have a report of a fatal problem that happens in the combination of TCP/IP networking and creating a sked, and I confirm the problem. There are no workarounds except to either NOT use TCP/IP n
All, I have just posted a patch at http://www.writelog.com/downloads.htm that fixes many, if not all, of the instabilities running TCP/IP networking. I apologize there is not a more complete explanat
The workaround I mentioned in my previous post on this topic is incorrect. Not running TCP/IP does workaround the problem with TCP/IP and skeds. Not entering a sked, but running TCP/IP networking doe
Try making a keyboard shortcut (Tools Keyboard Shortcuts) and use the "Command to Run" BandsBandUpRetainCall or BandsBandDownRetainCall Wayne _______________________________________________ WriteLog
There have been a couple of reports of problems with TCP/IP networking. In hopes of gathering more information, I have added some diagnostic information to a new version of the WriteLog networking co
interface Windows WL, so I suspect this is caused by the number-of-stop-bits setting WL is using when setting up the COM ports. Way back since about 1991, WL has set all COM ports for rig control to
I read through most postings on the writelog reflector daily and I understand how not everyone would be happy with the way WriteLog supports the LPT ports, especially on Windows XP. But I have not ch
1. With respect to the "created by" line, please express your annoyance to the contest sponsors, not to the writelog list, as its the sponsors that require this information. I know of no contest tha
partial answer: In WriteLog's online help, try the Search tab and enter WinKey. It will find a page that tells you how to deal with the autospace. As for "compensate shortened CW character lenghts",
The information on this thread is not quite accurate. WriteLog does not ignore networked stations when assigning serial numbers. But it only takes into account Q's that have already been logged when