That's not how it works. I too would like to see it go to a directory of my choosing when I want to open an existing log that is NOT in the recently used list. Editing the recently used list doesn't
If only I had your problem ... Well, looking at the other responses here's what I think I'd do: 1. Setup an "extra" logging computer on the network that just does the saves every 10 (or 20 or whateve
That's not what I see. I have a laptop that I use for the actual logging with the "main" ham computer sitting nearby. I set up both to autosave at 10 QSO intervals. I see them BOTH save the log even
For me, the telnet cluster works better because I have trouble actually reaching any of the area RF packet clusters. The telnet cluster looks identical to the RF variety. If you have Cable or DSL int
I couldn't find it in Writelog either. Found a nice Freeware program called SymmTime that works nicely. Has lots of configuration options so you can show UTC with or without a date. It can also keep
I too have no difficulties "right out of the box". Writelog gets the offset from your Date/Time settings found in your Windows Control Panel (I just tested this to be sure). If you don't have these s
Last time I looked this was the WRITELOG reflector not the RTTY reflector. I also feel that this does NOT belong here. I'm interested in WRITELOG issues, not what RTTY contesters are having problems
No, WRITELOG is a contesting program. It just happens to do RTTY very well (from what I hear anyway). I do not currently do any RTTY so I don't care about the woes of the RTTY contesters. This thread
I wonder if Writelog is reading the VFO settings (op code 05H) rather than requesting a Status Update (op code 10H) to obtain the "Current Operating Data". -- Bruce Ferry, AK8B
I too have the same problem with a new install. The packet window wouldn't open until I installed the DXTelnet stuff (which I find too cumbersome). When the window opens there is no "function" bar to
I ran the 10 M contest with the shiny new WL 10.37b. Coming from the TR world, here are my observations. 1. Writelog flawlessly read my radio - something TR has trouble doing on a consistent basis (n
Thanks to all who have responded! Some good things did come from the responses and next contest (I think the RAC Winter Contest) will go smoother. I had several suggestions to use F11 (after an INI f
It would only disappear after you hit the space bar to check the call. Of course the callsign would then also have to be included in the "dupe at ..." message at the bottom of the entry window.
Having heard all the back and forth about this I think I have the right combination to clearly state what I have in mind: 1. An OPTION to blank out the QSO entry when the call entered is a duplicate.
The ARRL just did a "survey" of what people use at their Ham stations: http://www.arrl.org/survey.php3?pollnr=198 WIN98 wasn't the biggest number but it was a very close second. SteveWS4F@aol.com wro