Hi Drew, No I do not.

Has anyone gotten Timewave Navigator to work with macOS Big Sur yet? I hate to upgrade and lose my WSJT-X capability. Thanks and 73, David, WA1OUI

Are you using "Quick Boot"? Disable it.

Yes, I have reloaded the program numerous time Jacques. I'll keep trying. I'm more than happy to take my chances with security and Windows 7 vs this nightmare. If the Russians, Iranians or the

Hi there, I am trying to record my own messages coming from WSJT-X for logging purposes and found that I had to write a small patch. This just adds a new utf8 field, tx_message, at the end of the UDP

Thank you for the follow up with my problem. Sorry to hear that you also have issues with Win10. Yes, there are so many people with configuration problems, loss of this or that, program freezing all

Hi Bob, Glad to hear that you have been as lucky as I had until last Saturday. It looks like keeping up with Win 10 has been like rolling some dice. If you throw the right numbers.If not problems

I'm not sure if my unsolved problem is related but ever since I installed the program on W10 machine, I have receive lock-up continually on receive, no pattern. I have tried everything suggested with

Charles, sorry I missed the obvious info in your subject line. I build the release kit for 64-bit on Ubuntu 20.04 using only packages installed from the official repositories other then Hamlib. The

Ubuntu 20.04, Bill. It compiled just fine with Boost 1.74. Now I should be good for a while. 73, Charles - NK8O On 11/23/20 1:09 PM, Bill Somerville wrote:

understand this point. maybe a compromise is in order. limiting to 2 minutes is indeed annoying. keep in mind that if a station is working F/H mode then he/she is rare and lots of folks will be

On Mon, Nov 23, 2020 at 02:08 AM, JP Tucson, AZ wrote: Hi Hank, Yes, "normal" - one of those very annoying "features" of wsjt-x; supposedly to "prevent it from becoming an automatic QSO machine".

Hi Charles, I guess you are building for Debian 9 or something based on it. The next release of WSJT-X will build using Boost v1.62 which should solve your issue using distribution versions of

Hi Bill Trying to run RC2 but keep getting memory error - this occurred with both Catalina and Big Sur. .2.2.2 runs fine…and all prior to 2.3 as well... 73 Dana VE3DS

Just an FYI. I had a small problem compiling 2.3.0 rc2 because it requires a new version of Boost. I did not have any problems previously, from version 2.1 through 2.3.0 rc1, and I really don't know

Gosh! I have the latest MS update for Windows 10 Pro 64 bit, running on an HP EliteBook 6930P, and have not suffered any of these issues. Wonder why? I'd suspect non-MS drivers being used, or those

I think it is a good idea to check for open spectrum more frequently in F&H, esp as all the calling stations are in a narrower passband than for typical ops.... /K1BZ

Bill, Good point. I guess I was in the habit of looking at the colors of WSJT before I installed JTAlert. I just turned off the WSJT internal highlighting so the colors in JTAert alert

Tony, you can substitute the WSJT-X ADIF log file with one of your choice, but as I said, you will not necessarily get the same results as WSJT-X does not tale account of

Bill, Thanks for the info. Is it possible to update the WSJT's log file with the same ADIF file I used to update JTAlert? N2TK, Tony