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

On 23/11/2020 04:22, Reino Talarmo wrote: Hi Tom, Mark, and Reino, with an all digital Tx audio chain not using one of the WSJT-X split modes may be OK but I would agree with

YES! last update removed all of my sounds systems and driver and disabled the desk top speaker. Took all day to get everything reinstalled and working with the right driver down loads. Thanks MS for

With a Flex you don't need to use Fake It or Split. Both on RX and TX you can open your filter width and TX band width really wide. I run my Flex with a TX band width of 8k, When using DIGU mode

make sure your tqsl program is up to date Dave Garber VE3WEJ / VE3IE

Tom, If 'Fake it' is working use it. The User Guide in 4.2. Radio recommends: Either method will result in a cleaner transmitted signal, by keeping the Tx audio always in the range 1500 to 2000 Hz so

Looks like I got DXKeeper working with jralert. But now when I try to upload a qso to Lotw it rejects FT8 modes. Need to figure out to correct that problem