This is almost certainly a security setting--the Win98 side is happy to send its log contents to all comers, but the W2K is not so readily convinced. The comments about XP here apply to W2K as well:
I researched this and find that version 10.38 introduced a problem: that version and all since fail to honor the the the "CW Only" comment in the "CW PTT Setup" dialog that you get when you press "CW
Sorry I was not clear in my first posting. There is no need to wait for an update as there is a workaround. Recent WL versions will handle PTT correctly if you go to the CW PTT setup and switch from
Fellows, Maybe I miss the point, but wading through 15 irrelevant emails about viruses on what used to be known as the WriteLog reflector is not how I would choose to use my time. If what you want fr
You have a choice. I understand that the N4PY software controls the Orion and presents an interface to WriteLog: http://www.ralabs.com/n4py/ The N4PY software is available now. A "built-in" WriteLog
The following WriteLog update works with version 10.40 (and later). http://www.writelog.com/downloads.htm#InstallVkNaCty After the update, WriteLog's beam headings and sunrise/sunset data will take i
I am unable to duplicate this reported problem. Can you be more specific as to call sign, band and mode? Can you do this by creating a log with just the two QSOs in it? Wayne
I talked to Ron today in the hospital. He had knee replacement surgery last week and is now in re-hab. No word on when they'll let him out. Wayne, W5XD
request noted. I did a quick google search on psk63 and didn't spot anything I would call a definitive/authoritative document on the mode. I'm not willing to allocate time to write code to a guess as
OK. Are there any additional WL users beyond Gil that would use PSK63 if it were in the program? And, if so, are you willing to find out what it is or, at least, figure out who knows? Thanks, Wayne
As of version 10.40, this is no longer true. WriteLog's Great Circle Beam Headings and sunrise/sunset goes through a sequence of "country files". This is documented in the [GreatCircleLookups] secti
It was removed intentionally because there is another way to do it. 1. File Open one of the logs to be merged. 2. File Save As ...ADIF format 3. File Open the other log. 4. File Import the first ADIF
There is one important exception to the statement that the _bck.adi file has enough information to restore the .wl file after a crash: the WAE contest with QTCs. When WL logs receipt or transmission
The "WLnnnnUPG.zip" installs upgrade any version of WL less than a year older. You don't need to use the UPG installs between. When you pay for a renewal or as a new customer, you get a "FULL" instal
Since WL doesn't know anything about that footswitch PTT, and since your report indicates your audio is making it into the rig without that PTT switch engaged, the only guess I have is that engaging
You may identify your station as any callsign while running WL. It does not attempt to cross check it with the call its registered to. (Sometimes I think it should, but that is a very different discu
One little fact you might want to consider regarding hum and iron core transformers: The cores are designed to restrict the coupling to include only the windings on the core (that part is obvious), b
...stuff deleted This request is already on my list. I expect to get to it, but I can't make any promises about when. But what was on my list was a bit different than described here. The request bef
Not quite. The answer is "we have been over this before". If you consider that the alternative "better work arounds"--which reportedly involve logging a different serial number than was sent over th