Hi Dave Thanks very much for taking the time to have a look at the problem I have been experiencing. As you can see from my message to Mike, I have now managed to sort it out - I do feel somewhat stup

#FT8

On 07/03/2023 8:08 am, Gene Sullivan wrote: Good to hear. I forgot that there is a section in the help file under "Troubleshooting" titled "WSJT-X / JTDX / MSHV not responding to JTAlert Callsign clic

#FT8

On 03/03/2023 2:27 am, Dave Tucker Nu4N wrote: The default behavior for JTAlert is to show ALL callsigns without regard to B4 status. If you don't want to see B4 stations than simply set the "Do not s

#FT8

Hi, I have exact the same problem (AutoIT error). It occurs once a week. I restart my computer to solved it. Running flex6500 4x wsjt-x v2.6.1 4x jtalert v2.60.5 Windows 10 73 Geert Pa3cps

#FT8

The decodes 2.60.5 window works fine, but still can't get any decodes for the callsign #1 or #2 window with the above settings. I'm not sure why no decodes in the callsign window at all?

#FT8

Dear Dave G0DJA I set to ignore the B4 for old QSOs. I will uncheck it. De JG1OGM

#FT8

On 22/02/2023 11:47 am, Phil Stanley via groups.io wrote: Q65 is supported with respect to logging and B4 checks. Q65 it is not supported for the Wanted Alerts when set for tracking by individual mode

#Beta #FT8

I tried a local loopback test using just 1 slot as Fox. The ADIF message does get sent to JTAlert but JTAlert doesn't seem to forward it to the logger (Log4OMV2 in my case) -- Laurie -- is there some

#FT8

Mike, Jim, and Laurie, You are the BEST! I went with Jim's settings then clicked configure after are reboot. The UDP server then did the update to 224.0.0.1, 2237. All is working perfectly now!!! Than

#FT8

Hi JoAnn, If I correctly understand your question, the following is what I use to prevent seeing CQ transmissions highlighted from stations that I have worked B4. There is a way to make WSJT-X no long

#FT8

On 26/01/2023 5:25 pm, Dave Tucker Nu4N wrote: You never answered my question "You mention two identical setups. Is the problem only occurring on one of the PCs and not the other?" de Laurie VK3AMA (J

#FT8

On Wed, Jan 11, 2023 at 11:56 AM, Joe Subich, W4TV wrote: That is a question for the moderator/list owner of the WSJTX list. Good luck with that. You must have said one of the banned words. Bad Bad Li

#FT8

Got it to work. When I copied the app password it left off the last character. That's what the problem was. Thanks for the help. 73 Pat N6PAT

#FT8

Just confirming ClubLog is working again Thank you! George vk3oi

#FT8

Downloaded the new version on 2 of my computers. Looks like it's doing great Laurie!!!

#FT8

Hi Laurie, Thanks for your email. Understood! Best wishes for the New Year! 73 George VK3OI

#FT8

On 01/01/2023 12:33 pm, David Michael Gaytko // WD4KPD wrote: good running computer with w10, 260.3, and jtdx improved. problem just keeps cropping up....jtalert is set to notify new/needed dx. clicki

#FT8

On 24/12/2022 1:03 am, Morris WA4MIT via groups.io wrote: Morris, This is the first time I have anyone made that claim. Is this only with JTAlert 2.60.3 or has it been occurring over multiple JTAlert

#FT8

Laurie, never heard back from you on this . . .

#FT8

This is a WSJTX error message. It is discussed along with the fix in the WSJTX help files (F1 in the program). 73, ... Joe, W4TV

#FT8