About a week ago I seen a post that when a POTA,SOTA,etc would auto trigger an alert. I am a avid POTA chaser. But i forgot where the setting was. Any help would be appreciated. Thanks

#FT8

Looks like I found the issue, that was Filters related. Go to Alerts - Filters and deselected LOTW member and changed to No QSL filter ... Seems to work. Hope this helps someone else.

Ahh, Got it. Yes when powering down the computer it also reset the audio As this issue deals with the USB port, I deleted and reinstalled the drivers for the rig usb com ports, ran the system and the

On 28/05/2023 9:14 am, Ray King G0VSS via groups.io wrote: I see TM1SIX in your Log4OM log image which tells me that for some reason JTAlert is not finding the QSO in the log when it does a B4 lookup.

#FT8

On 28/05/2023 9:03 am, Rick KJ4YLO wrote: See the JTAlert Help file, "Tutorials -> ATNO (All Time New One) visual alert" topic which discusses how this Alert is triggered and the Alert Database rebuil

On 27/05/2023 9:49 pm, Courtney - N3AIR wrote: It could be a UDP issue. Perhaps a conflict with some other application. Try changing the inbound UDP port from 2236 to say 3336. It might be an MySQL is

On 28/05/2023 4:54 am, JTAlert Support (VK3AMA) via groups.io wrote: Sorry, I should have read the subject line of the message. Left-click the cog/gear icon of the Callsigns window and set the options

Thank you, Laurie, for the new 'Copy DF to Clipboard' menu option. I'm using it a lot and has improved my operating a lot!

#WISH

The latest JTAlert version 2.60.7 is now available at https://hamapps.com/JTAlert/ Full release notes are available at the end of this message. de Laurie VK3AMA (JTAlert author) Release Notes: > 2.60.

#Announcement #NewRelease

On 27/05/2023 5:47 am, Anthony W. DePrato wrote: Sounds like WSJTX is still producing decodes well into the new decode period. This is symptomatic of an under-powered (old hardware) and/or under-resou

My experience is that when the default layout is used by JTAlert, then the flags, badges, etc revert to default characteristics. Apparently, the customizations get reset when the default layout is for

On 26/05/2023 6:38 am, f i via groups.io wrote: The callsigns display grid on the main JTAlert window was removed starting with version 2.50.0 (2021-Apr-12). It was replaced with the Callsigns window.

Thanks gentlemen my grids are show up now on all bands. I guess you learn something new every day. Appreciate the help.

#FT8

I have made contacts with dx at -24 several times sent by ve3wej on lg phone

#WISH

On 24/05/2023 6:11 am, Larry Banks via groups.io wrote: That's true, but a missing NET 6 Desktop Runtime should not prevent the main JTAlert window from showing, it does not require it. de Laurie VK3A

Thats fixed it, had to reenter and save proper path, all is well

Mea culpa Thank you Laurie. I must have missed this a while back.

Thank you Laurie. I'm glad to know it's planned for V3. 73, John W1JA

Yes! I 'repaired' my .NET installation and now the .EXE files run as expected! Thanks again!

On 20/05/2023 1:28 am, Charlie Webb wrote: You have been lucky in the past with JTAlert not involved in database lookup, which locks the file, at the time when the update was being performed. FYI, wit