Laurie: Been doing some digging. They had server issues earlier in the week that I reported. You cannot get into their help website/page. I'm guessing it is there problem as you suggested. Bob W8RID

#HRD #JTDX #FT8

Philip, Thanks for the confirmation that setting change was the fix. I received about 6 other similar reports, so I am confident that is the answer. The next JTAlert release, currently with the Beta t

#FT8 #JTDX

JTDX is not compatible with JTAlert 2.13.0 with respect to Callsign highlighting instructions sent by JTAlert. JTDX users need to turn off the "Color Band Activity Callsign with alert colors" checkbox

#JTDX #Important #Announcement

Got it fixed. I mistyped one of the TCP server numbers. Bob

#JTDX #HRD

When I installed JTalert 2.12.10 my logging into HRD ver 6 starts to make a logging that is ok an then it makes a logging an emty line with date 1999. Any body have a solotion. 73 de oz6hq

#JTDX

Thanks Laurie great help. I loaded AC log, imported my LOTW adi and then did the JTALERT scan and got the yellow off my screen. Thanks heaps. de Mick VK3XN

#JTDX #FT8

Folks, I did try Log4OM and miraculously enough, it does not show this problem. It will take me some time to get used to it's other features.

#HRD #JTDX

Please be advised, Current builds of JTDX are producing Bad Mode spots, FT8 spotted as T10,JT9 or JT65 sent direct to PSKReporter. It appears that if a user is monitoring FT8 activity and changes thei

#WARNING #JTDX