I am already in contact with Bill, G4WJS. I shared with him details about the issue on band change and how I fixed it. @ TomK: I don't think the problem you mentioned is caused by the same

The folder to delete is \Users\[username]\AppData\Local\HamApps Mike W9MDB

On a 2nd note, Laurie, did you see my msg about a JTA error popup and also not sending to QRZ even though it is enabled? Had also asked how to reset JTA config or how to do a complete folder

Blush! I inserted the wrong capture - then misread it, oy! But, YES, the symptom I noted has no waterfall trace at all. I've experienced it at least 10 times over the last 6 months. Each time I

Hi after upgrading HamradioDeluxe with the latest version (6.7.0.301) , JTAlert stop to work. When JTAlert receive the first callsign received from WSJTX it stop to works and crash . If in the

Have you submitted that to the WSJT-X group for inclusion in the main branch of the code? Neil, KN3ILZ

JTAlert has always logged Counties per the ADIF spec, "StateCode comma CountyName", event when the County name returned from an XML lookup is not of the correct format. Log4OMV2 has history with bad

Sounds like the JTTAlert window is placed off-screen. A common problem with Windows such that Windows has mechanisms built in to bring the windows back. Do a Google search on "Recovering off-screen

I strongly suggest you submit a patch to the WSJTX dev team for this fix. de Laurie VK3AMA

Are you sure? F/MM was decoded at 2389Hz, but your waterfall image is limited to 1500Hz. de Laurie VK3AMA

No new monitor.

Might that also fix the ghost signal reports in WSJT? Or has that been fixed already? I note it here since JT Alert reports then as well and I was about to note it here. I then realized it was the

Dave, and all Very sorry, I posted this on the wrong forum... I guess I am getting tired today ! Soory for useless bandwidth ! 73 Paul F6EXV Le 18/10/2020 à 21:42, Dave

you have not selected which adif file to import so importing is not possible til then if you click on load, and find that file, things will import. and this is a log4om issue, you may get a faster

Hi all I have messed up with my 2 callsigns, trying to configure "the whole thing". So I need to completely erase the log under Log4OM, and reimport an adif file. The import menu screen now looks like

why not load jtdx all by itself, or via jtalert ( since you are asking this group) unique names or rig names is what you need, so read the manual about using those. it may give you a solution to

Hi alln me again I am strill struggling very badly.... If I understand things correctly, the JTDX launching is done by opening L4OM Since L4OM allows for 2 (or more callsign)s, would it be possible

Thank you Mike!

Laurie, FYI: In the meantime I've changed WSJT-X's source code and caught/fixed the error there. Now at least my wsjt-x_improved versions should not generate any more false spots when a band change

Hi Laurie I still do not manage... I am lost between all the udp addresses and ports. Where should the 239.255.0.0 address be set ? JTAlert, JTDX (if so, where,primary, secondary...)