Hummm, it was already checked and set for a threshold of 1.5. I changed the colors and left it turned on I also turned off the parameter directly below it: Highlight Signal dB Level. 73, Bill "Setting

I brought up the decode history but did not see how to turn on the DT difference alert. I checked the docs which told me to hover over the DT field, which did not resolve my problem. This is with vers

Rats, that was a VERY useful item for me. Do you have any idea why it was removed? 73, Bill AA4M

It's not there, unless it is there and I don't recognize the phrasing of the option. 73, Bill

At one time if a station's time was 1.5 or more seconds out of sync from mine, the error was highlighted. That is no longer happening and I've dug through settings and alerts but cannot see where to t

I've searched but did not see any posts discussing this problem. I have HI and AK marked as needed on 15M FT8 but I've seen these states on the band and they are not being flagged. So I tested against

Is there any way to remove the B4 QSO's from the grid but still leave them highlighted in WSJT-X? 73, Bill AA4M

The grids are all there. 73, Bill AA4M

Just the same as yours: I reinstalled 2.15.8 which solved the problem. BTW - I'm a retired computer programmer - I know what you're going through, hi! 73, Bill AA4M

That worked, thanks Laurie! 73, Bill AA4M

OK, I just worked a JA who was calling CQ. My QSO was successfully logged into DXKeeper. Then the same JA popped up again calling CQ and was NOT shown as B4. I closed JTAlert and WSJT-X, restarted the

DXLab's DXKeeper is my logger. JTAlert successfully sent both Alaska QSO's to my logger. 73, Bill

I neglected to mention that I had just installed 2.15.9. So after reading Ron's message, I rebooted but both Alaskans had left the band. 73, Bill

I don't understand your question! Maybe if I re-phrase my question. When JTAlert sees a call outside of CONUS, it colors the call red with a yellow background. When I work these stations, JTAlert then

I installed the virtual cable, rebooted, then assigned Windows to my usual sound driver and WSJT-X to its CODEC driver. The good news is that I now have Windows sounds when working FT8, but the bad ne

I just worked 2 different Alaskan stations on 17M FT8, but they continue to be displayed in my NOT "Worked-B4" color scheme. All others on the band seem to be identified OK by JTAlert. What does the p

Every time I start a JTAlert / WSJT-X session, I get this message: Because of hearing problems, I have audio turned off in JTAlert, so why must I see this error message over and over and over . . . FW

I just received a message through JTAlert and I responded. Then I noticed both were dated 2019-13-05 . . . the 13th month of 2019! An easy fix, I'm sure. 73, Bill - AA4M Tucson, AZ

Hello Laurie, Yes, I'm talking about the WSJT-X display. P49X is showing as having 3 signals on a band but only 1 of these is identified with my color scheme (black text, red background) as "B4". Actu

Right now P49X is on 40M calling CQ in 3 spots. I've worked the station on this band, but only 1 of their 3 signals is being tagged as "B4". Is this as intended or is it an oversight. FWIW, I consider