Laurie, I am currently using version 2.9.4 of JTAlert with WSJT-X 1.7.1-devel r7627 and HRD Log 5.24. When I work a station on a new band, I often "mouse over" to the call sign on the Log Fields to se

Mike, You are correct!!! I guess that even long-time users of JTAlert such as me need to check for new settings now and then. This probably was in the release notes as well...my bad. Ed, K0KC k0kc@arr

Laurie, I forgot to mention another change in JTAlert behavior that I have observed perhaps with 2.9.1 or maybe earlier. When a station calls CQ DX (say CQ DX K0KC EN80), the asterisk (*) shows in the

Laurie, I installed 2.9.2 this morning hoping that the last two characters in the Grid would not be forced to ALL CAPS as was the case with 2.9.1. Unfortunately, it still seems that all characters in

My bad...sorry! :( Ed, K0KC k0kc@... http://k0kc.us/

Any ideas on this, Laurie? Ed, K0KC k0kc@... http://k0kc.us/ ----- Forwarded Message -----

Laurie, I installed version 2.9.1 of JTAlert yesterday (3/14) and it appears that about that time (1900 UTC) the application started logging most (but not all) contacts with the two least significant

Steve, I am not really sure of the differences between the versions of JTAlert for WSJT-X and JTDX, but is it possible that you have started the wrong version of JTAlert.? Ed, K0KC k0kc@... http:

Mike, Don't ever give up JTAlert! I have made over 11,000 JT65/JT9 contacts over the past five years or so and I could not have done that without JTAlert. I consider it an essential part of WSJT-X whi

Mike, Yes, just the CQ fails to appear in the RX frequency window. I suspected it might be a JTDX issue; I guess I will try to contact the author directly since he appears to know English. Ed, K0KC k0

Laurie, Thank you for adding JTDX compatibility to JTAlertX 2.8.5. I have been testing JTDX off and on for a couple of weeks now and have noticed a minor issue when used with JTAlertX (using the short

Dwight, My guess is that those guys who send an R report after a CQ do not understand that R should mean that they have received your report ok. I think that they just believe that R means that they a

I had a similar problem and just re-starting JTAlert fixed it. Ed, K0KC k0kc@... http://k0kc.us/

The settings are in WSJT-X rather than in JTAlert if I am understanding your question. Ed, K0KC k0kc@... http://k0kc.us/

Laurie, I am unable to send you the support files as I still get the "Error Allocating Memory" message when I try to send the email. I did delete the debug_* files in the indicated directory. As I rec

I will probably have to delete that file that you mentioned to get the Contact Support to work. Can you give me its name and location? Ed, K0KC k0kc@... http://k0kc.us/

Laurie, I tried your suggestion below, but B4 is still not working in the call display area, but it does show (for a station that I have previously worked) in the log display area. Ed, K0KC k0kc@arrl.

Laurie, I uninstalled 2.7.3 this morning and went back to 2.7.1 this morning so that I could do some JT65/JT9 operating today. I will have to reinstall 2.7.3 to try your suggestion below. I will let y

Laurie, I have a similar problem to Geoff, but in addition Worked B4 does not work. I tried to Contact Support and send you the configuration, but when I click on the Send Email button, I get a memory

The HamApps web site was down here this morning, but Laurie's link below worked fine for me. http://dnl.hamapps.com/JTAlert/HamApps_JTAlert_2.6.30_Setup.exe Ed, K0KC k0kc@... http://k0kc.us/