I checked the "show DXCC name".  I have the decode call sign set for 2 lines and 8 per line.  The first line decodes with call and country/state but the second line only shows country/state and NO call sign. The info above is blank.

Thanks Jim

I did something that stopped JT alert from showing me info when I hover my mouse over a call sign. Now I can figure out how to undo it.

I was trying to figure out how to switch it from showing in km and show in miles.

Sometimes things are better off left alone.
Thanks ahead of time.

Gerry
KB9PKI

_._,_._,_

---

Gerry,

In the menu at the top left (if you're using 2.16.5) of JTAlert, go to Alerts/Decoded Callsign Data Tooltip. Click Enable. That should do it for you.

73,

Jim N6VH

Your Anti-Virus is been a bit draconian.

There is an ‘Out of Shack’ alert that is based on decode distance. It is only per instance not per band but it’s better than nothing.

Tom

P.S. 1500 miles bit long for 6m - I have it set here to 500 Miles and it alerts me fine when band is open.

--
73

Tom
GM8MJV (IO85)

Take care no checks are by properties playing and recording..... Listen to this device..... My was ticked and this override the soundcard.  73 de PC1Y. Peter

I downloaded and installed version 2.16.5. 

When I clicked on the desktop icon to start the program, I received the message "The item 'JTAlert.exe' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly."  Do you want to delete the shortcut?

When I open the folder where JTAert was installed -- c:\JTAlert, I do not see a JTALert,exe file.  I do see a JTAlert.OLD.  When I open that folder I get a message that JTAlert started directly or with an incorrect shortcut and it asks me to select the JT mode application that JTAlert will use.  When I click on the WSJT-X button version 2.16.5 does start up.

FYI the operating system is Windows 10

Any idea as to what is happening?

I have deleted and re-download several times, with the same result.

Jim
W2SM

I would like to see a user defined alert based on decode distance. This would be useful for VHF/UHF bands. On 6 meters for example, a decode greater than 1500 miles would alert, on 2 meters, a decode greater than 100 miles, etc. Obviously this would not be useful on HF.

73 de Sebastian, W4AS

Assume u r running 2.16.5 of jta. Same exact issue here. Work around is run v2.16.4. Glad u isolated issue to McAfee. Tu.
 .de Tom
KE0ABA

You mean other than removing McAfee?   

Look to see where you can whitelist the directory where JT-Alert is loaded.   You should be able to do that without a problem.

If you can't, and McAfee was provided 'free' by your ISP, remove it, and actually find an antivirus that allows you to do this, as it sounds like McAfee is quarantining files. I suspect its done that to the JT-Alert executable.

 

Neil, KN3ILZ

On 19/05/2020 06:28, Jim WA3ERQ wrote:

Neil;

Thanks for pointing that out.  Yes I am using 2237 but I'm hesitant at changing this since I'm not too computer literate when it comes to IP addresses and UDP Ports.  I have selected Multicast in GridTracker and from what I can see on Google, this should allow that port to be used for several applications.   If not, do you have any suggestions on my settings for GridTracker?

Thanks again.

Jim
WA3ERQ

Hi Jim,

using multicast UDP only works if all the servers use multicast, unfortunately, because of limitations in the tools Laurie uses to write JTAlert, JTAlert does not support multicast UDP at present. The JTAlert feature to "rebroadcast" (they are not really broadcasts but are resends) works around some of the limitations allowing one other server to receive USP traffic that comes from WSJT-X instances.

JTAlert listens on the port specified in WSJT-X (2237 by default), JTAlert clones and resends incoming traffic on another port (2334 by default), another application like GridTracker can be set to receive WSJT-X style traffic on this port 2334.

73
Bill
G4WJS.



--
73
Bill
G4WJS.

When I added Mcafee to my computer my JT Alert Shortcut  does not work.  I get this "PROBLEM WITH SHORTCUT"  The item JT Alert.exe' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly.  I even went to the windows 10 menu I tried to launch from there. Same message....I uninstalled it and downloaded it again and the same process happened again.  Any ideas....everything was working properly prior to installing McAfee.

Thanks
Mal
WF5K

Yes it is a Windows function, but one that can be changed by the programmer, at build or run-time depending how the menu is created, as to which letter is the Active one for each Menu item.

In fact the 'Sound xxxx' ' menu also uses the same 'S'.

I had not noticed that you can change the Hot Keys - Thanks.

Neil;

Thanks for pointing that out.  Yes I am using 2237 but I'm hesitant at changing this since I'm not too computer literate when it comes to IP addresses and UDP Ports.  I have selected Multicast in GridTracker and from what I can see on Google, this should allow that port to be used for several applications.   If not, do you have any suggestions on my settings for GridTracker?

Thanks again.

Jim
WA3ERQ

I'm guessing you're using JT-Alert's UDP rebroadcast feature?    Just to verify, you aren't using the default 2237 port as that's the one WSJT-X uses to talk to JT-Alert.  

Neil, KN3ILZ

I don't know what the exact problem is, but if it's the callsigns all
disappearing when you start transmitting, I'd be happy to test. I
just saw the problem a few minutes ago. It's not consistent, I've
only seen it once in the last half hour or so.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

I have this also posted on GridTracker.  For some reason, I can't get messages to be transmitted to GridTracker even though the IP and ports are correct.  The only way I can get a UDP message to be sent is to open the Settings menu and as soon as I click on APPLICATIONS SETTINGS, a message is received.  If I don't do this, no messages are sent.  I can duplicate this issue several times.  Is there a timing setting that I am missing in JTAlert to adjust for sending these messages?

Thanks

Jim 
WA3ERQ