Good evening Laurie and all, I have discovered a relationship between the disappearing menus in JTAlert and the effect of having two monitors attached to my PC. I recently have begun to run two video

I just upgraded to 2.16.3, but my B4 function does not seem to be able to scan my ADIF log. All stations logged since the upgrade do indeed display that they were worked B4, if they were worked after

The latest JTAlert version 2.16.4 is now available @ https://hamapps.com/JTAlert/ This is the official public release which has the HRD 6.7.0.269 FT4 compatibility fixes of

Ok this is embarrassing. I was so sure that I had the path to the adif log correct that I fail to check it carefully. I was saving the log exported from LOGic to ALMOST the right directory (a few

I know Laurie said to look in the help section for a solution to this startup issue. I cannot pinpoint the exact date this started showing up and I really don't want to have to go back and delete

Your patience and expertise is noted and appreciated. At this point in time, we hams have the benefit of a great hobby with great tools. Be safe and healthy! -- 73, Bernie, VE3FWF

Got up this morning everything is back to normal. Text msg once again is working. Not more TCP/IP port error. 73, Kit W3KIT

I keep having issues with Defender running, even after I mark the installer as safe. Sometimes with JTAlert running, it identifies the program as malicious and kills it! I do not know what the process

I just got a text message from an OM who is displayed as "Offline". So the offline indicator seems to be unreliable. I did the tests available under Web Services -> TCP/IP Network Ports and all show

My bad. It is not a text but a notice I logged the qso. -- 73 Bob K1RI Sent from my Rotary Phone

Thank you Laurie for the info. RTFM, oh dear! Now need to figure why some fields such as Name are not being updated by HRD when logging QSO. Same problem as PC1Y. -- 73, Bernie, VE3FWF

I realized I did not have latest version. After update from 2.15.7 to 2.16.3 I no longer hear "DX" for /MM. 73, Andy, k3wyc

Laurie, ave also the HD .269 and Jtalert .2.16.3 build 2 working together ok........ Only notices that the propagation details are now not transferred into HRD .... don't know if it is in hrd or

There are several maritime mobile stations active on 40 m and some of the call signs are those of DX I have not worked on 40 m. JTAlert calls "DX" each time one of these /MM stations is decoded but

This does not exist in JTAlert and there are no plans to create such an intrusive feature. How are you determining that the logged station is receiving a text message from you?

Just loaded v2.16.3 to a clean install meaning all previous files removed. Setup all my preferences. Ran some tests and works faster and this is a great update. One thing it does when logging the

*** IMPORTANT PLEASE READ*** JTAlert users who have upgraded their version of HRD to 6.7.0.269 and followed HRD instructions on updating their existing FT4 QSOs to be adif 3.1.0 compliant, Mode-MFSK,

Hi Laurie Must have disappeared into the ether, I replied to your locked post. They have introduced a number of issues for third party apps! Note second para, this from Mike at HRD

No need. I have already provided the answer here https://hamapps.groups.io/g/Support/message/28940 de Laurie VK3AMA

I don't see any waiting moderation message from you. This issue is easily resolved by telling JTAlert it needs to log ADIF 3.1.0 compliant FT4 now that your HRD log has been