Like I said that is not always true. I've filled a number of needed band slots simply by calling a needed entity that was not currently transmitting but was receiving me as indicated by Ham Spots and

#FT8

You didn't give your name... Will you be around tomorrow we could connect and see what's going on with your system? I help a lot of people. I'm normally around after 0800 Central time. Call me at 217-

#FT8

I have to agree with you Bill. My dumbing down of the JTAlert/WSJTX setup instructions to 4 simple bullet points with pictures and numbers has had little benefit in reducing the support requests. Some

#FT8

Sorry, should have sent this as a pdf iguess

#FT8

I have found locking your TX box and setting your red TX marker on a clear open spot on the water fall works great. If someone stays too close or right on top of your red marker then just move it to a

#FT8

Text Messages are directed to a Callsign only, there is no provision for separating Callsign messages on a per JTAlert instance basis. How would a station sending you a message know that it needs to g

#FT8 #JTDX

Glen, I previously asked but got no answer... Does using the "Sound -> Test Sound Output" menu produce the same delay? This question is important. The test function uses the same code and an identical

#FT8

If WSJT-X is responding to JTAlert Callsign click events by setting the DXCall then JTAlert <-> WSJT-X UDP comms is working correctly. There is nothing else that can be done by JTAlert. The decision t

#FT8

There is no harm in installing the NET 5 Desktop Runtime, even if your version of JTAlert doesn't use it. If it installs correctly without showing an error you can be reasonably confident that you can

#JTDX #FT8

TNX much for your help. That did the trick.. 73..Phil W8PP

#FT8

The Last QSO function has not changed for many versions. The code in 2.50.2 is identical to the code in 2.16.17. Since the new 2.50.x releases are not working that suggest to me that your PC Protectio

#FT8

I have no problem with edge. When the SAVE box pops up, with the blocked warning, just click on KEEP and KEEP on the next popup. Bobby/N4AU

#FT8

I changed the WSJT-X startup to include "rig-name" and everything started working. Norton is still installed and running. JTAlert Instance : #1 JTAlert Start Params : /wsjtx WSJT-X Window Title : WSJT

#FT8

Hello OM Bill, Eureka ! With 5.0.6 it worked immediately. Thank you so much for your help. I delayed the update for 7 days. After 7 days and Windows will update does this mean that JT Alert stops ???

#FT8

I got it to work!!! WSJT -> JTAlert -> Log4OM Uninstall .Net 5.0.7 Uninstall JTAlert Reboot WSJT Reporting Tab: Log4OM Settings: JTAlert Settings: These settings worked for me, your mileage may vary.

#FT8

FYI, A fixed JTAlert is currently with the Test Team. I expect to make a public release in 2 or 3 days. Why 2 or 3 days you may ask. The audio fix/workaround is tacked onto the upcoming 2.50.2 release

#FT8

I'm using the built-in Windows Defender stuff. 73, Randy, KS4L

#FT8

I just had the same problem. I tried every suggestion I could find, all to no avail. I reverted JTAlert back to 2.16.17, and all is well. No changes other than installing 2.16.17. 73, Randy, KS4L

#FT8

I'm using Norton and now JTAlert has quit working, again. I have added a bi-direction rule to allow UDP 2237 from anywhere. I have installed 2.50.1 and based on a previous, I changed to a multicast ad

#FT8

Hi, Laurie, and thanks. BTW, UDP settings are clicked in WSJT-X, in case you may think that as the problem. It works in v2.16.4 but not in 2.50.0. Clicking on the View menu brings it up but clicking o

#FT8