I also have occasionally received the message "An unknown error occurred while accessing.. (logfile)". This has been going on for months and happened again during the 2015 CQ WPX CW contest. But this
Bruce W1CSM Thanks!! I have many keyboard shortcuts set up here, but didn't have those. They work great to highly increase the efficiency of managing the selection of spots on the bandmap instead of
Put a %E at the end of the message. Keith W3KB Greetings, I'm attempting to use the RTTY contest exchange messages in WriteLog for this weekend's RTTY RU. What is the sequence of symbols and letters
Gary: Are you using a 3 contact (stereo) plug to the key jack? A 2 contact plug will short things out and key the rig. Also, if the FT-950 has a built in keyer is it turned off? If the built in keyer
I kept getting the same error ("An unknown error occurred while accessing {my log file path and name}" until one day, I got a "Server Busy" notice. That gave me a clue. I do not network Writelog, it
Well, here's a different perspective. I run Writelog V12 after updating from V11 and importing the .ini settings. I run Windows 7 Home Premium on a system with legacy serial ports and use a homebrew
This is a test only. Had some issues that my messages were not getting posted. Re-subscribed. Keith W3KB _______________________________________________ WriteLog mailing list WriteLog@contesting.com
Yet another way to do it is look to the upper left of the letters. For example: QWE would be the number 123. I had to do this several times during the contest. So a report of: TOO QWE QWE would be 59
I updated to the new Version 12.05 today. One of the new additions in the update is: Add ability to disable CW space sent on startup. The update was immediately causing a startup error and I got the
I, of course, used in the In-State version, but the situation is the same. As a work-around, open the Cabrillo file in Notepad. Edit the line to read: CONTEST: PA QSO Party (or you could simply put P
Thanks, that solved it here too. 73, Keith W3KB thanks Rich and Ron, that solved the problem... now if I can just remember that for the next time!!! I'll be on 10 SB.... slow going but maybe somethin
Just upgraded the station's Windows 10 Pro computer with what's called the "April Update" of Windows 10 (the one with Timeline, etc) Now the WriteLog (latest Version 12.27C) BandMap has failed. Worke
Randy K5ZD: That's exactly what fixed it. Reinstalled Writelog Version 12.27C and now the BandMap works again ! Good grief......Windows Updates. Many thanks, Keith W3KB --Original Message-- From: Ran
Had the same thing happen here in NAQP RTTY, but occasionally it would highlight a new station. Things were not consistent. Keith W3KB During the NAQP RTTY dupes or any type of high lights like new s
Mine was indeed checked for DE during the NAQP. Like I said earlier, some calls were highlighted that way when RittyRite Scanned for DE Keith W3KB I don't think that I have ever checked on the "DE "
Well, this is something I've never noticed before: If I hold down any F key in Writelog, it will constantly repeat the specific programmed CW message for that key ! I use a WinKeyer. Is this somethin
Randy K5ZD Exactly.....I have never seen this before either in my numerous years of using WL. Just as a check, I fired up DX4WIN. It does NOT repeat the F keys in the CW keyer of DX4WIN if I hold dow
The issue described below is that if you hold down an F Key in Writelog it will transmit the message several times. Apparently, this is a part of Writelog (which I never knew). My problem was I using
My Yaesu FT1000MP Mark V works just fine on FT8. Driven with RigBlaster audio interface and use Upper Side Band (USB) to transmit. Keith W3KB GM Randy This idea of FT8 and RTTY Roundup got my
I do not use the radio interface on FT8 for that exact reason. WSJT will run without it. Use FT8 on one side of the screen with no radio control and a logging program on the other side of the screen