Ed, That message looks like it might be from your browser. What browser are you using? I tested the download with Firefox, Edge and Chrome, with no problems. Incidentally, the messages you show are in

Tom, At this time that "tool bar" is essential. It is the app that brings up the rest of the windows (Callsigns, etc.). It is actually a smaller version of this (see attached). Under "View", you have

Tom, What is the "mini-tool bar" you are referring to? 73, Jim N6VH

Laurie, I vote for user choice. 73, Jim N6VH

Laurie, I just checked this folder (never had a reason to, before), and I see the same situation, although not as much Bill's. I have 61 files in there, dating back to 20210317. Actually, one of them

John, It is possible that the Callsigns window is on top of the main JTAlert window. Try moving the Callsigns window. If the window won't move, click on the cog to open the settings. Go to "Window", a

Dave, The cty.dat file for JTAlert is actually cty.dat.sqlite. The normal Windows search might not find it. The search program I use is everything.exe, and it finds it. The latest version is dated 202

David, Great! Glad it's working for you. Jim

David, See if this works for you. In JTAlert - Settings - Alerts, disable all alerts except for the wanted calls. Then, in the Decodes window, under Filter, check "Show only Alerts". Also check "JTAle

Gilles, Does the QSO get logged to ACLog, even though the error message says otherwise? If so, go to Settings - Logging, and increase the time under"Check QSO Log Record". If the QSOs aren't getting l

Andy, I checked your original message, and I have some questions. You said "what do I need to config to get JT alert to see the spots as I receive nothing." By spots, do you mean you are not seeing ca

Laurie, I wrote a very basic batch file that might help Wyndell. It has been a long time since I have worked with batch files, so it might not be perfect. It does work, however. Wyndell, open Notepad.

Laurie, As an experiment, I tested my suggested method, and it doesn't work. I can point Win4Yaesu to the desired JTAlert shortcut, but Win4Yaesu then points to the location listed in the shortcut, in

Laurie, Yes, that could well be. It will be interesting to see if that is the case. 73, Jim N6VH

On 3/3/2021 3:37 PM, HamApps Support (VK3AMA) wrote: > On 4/03/2021 9:30 am, Wyndell - K5WJF wrote: >> Jtalert will have a pop up about which version to start > > That's because win4icomsuite is start

In my case, I have one from 2016. The only others (a total of 8, not counting the current one) only go back to Feb 25. I don't know what is different in our setups, but I am not seeing a large number

Keith, In JTAlert, go to Help - Open Help File. In the help file, click on Settings - Logging - ACLog. 73, Jim N6VH

Laurie, Yes, very true. The chance of incorrect data is the main reason I don't normally use lookups. I prefer to trust the data sent from JTAlert. 73, Jim N6VH

Dave, I did a test log to Log4OM using WSJT-X 2.3.0 and JTAlert 2,16.17, and kp2/nk4dx logged correctly as US Virgin Islands. I then deleted that QSO from Log4OM and did the same test, except I used J

Glad you got it working. 73, Jim N6VH