Thanks Laurie. I deleted the "decodes" files per your instructions, and the Fatal Error went away. Just to clarify, my Decodes Window was populating just fine. I got the Error when clicking on a CQ st

Just got home after operating 3 months at my secondary station location during Stay-At-Home. Had flawless operation with JTA while away. I've got my monitors all reset, and changed my Gridsquare. Usin

You can toggle it off and on using F9. I'm using Delete Old Files and filtering out Worked B4. 73 Herb WB8ASI

Take a look at the JTA Decodes window. I use it all the time because I can scan everything vertically much faster, and you can fine tune any filtering you desire. Try it and I think you'll like it. 73

Also, you could use the Decodes Window to see the entire list. 73 Herb WB8ASI

I'm a long time JTA User and have just looked at GridTracker cuz I like the graphic look of the activity. I just enabled the JTA rebroadcast to a port 1240 which was there from earlier setup with Log4

If you are getting sounds from Windows, you should get sound from JTAlert. It should be using your normal default sound card. Check on the Sound Card page in JTAlert. Do you have the default sound car

Mine still toggles, but not a big deal. 73 Herb WB8ASI

Yes, I have it. JTA 2.16.5 Win10 64bit. It started for me several updates ago. 73 Herb WB8ASI

Jim, I'm a Log4OM user. I know I can change the column positions on log page, but can we change it on the Main UI window since that's where I look first? That would be great. 73 Herb WB8ASI

Laurie, I don't know about a Retry, but seems it might be possible. There is the Last QSO Log that it tells us it's there. I have stumbled around in the past and somehow got it to get it back in the l

OK Joe. Consistency is good for me, but atleast you have a reason.

Happy to report that Terry responded in the Log4OM forum that the Zone problem should be fixed in the next release. Now my SUGGESTION BOX item for JTALERT is that since I've been focused on zone probl

...and Log4OM also has the correct zones in its Main UI window, however something goes wrong upon the logging of the QSO. It happens over and over again. Guess we need more chatter on the Log4OM forum

Thanks Dave. I'm not alone. Now that I'm aware of what is happening I keep on top of it best I can, but still seems to like logging ITU 6 and CQ 0, even tho the Log4OM main screen and JTAlert say othe

Thanks Jim. This Zones thing is driving me crazy. Not sure where data is coming from. Just finished QSO with N3BNA. All agree Grid is FN10uf. Log4OMv2 has location as ITU/CQ as 8/5, and so does JTAler

I've started seeing CQ zone=0. In my pursuit of accurate data I find many misloggings of ITU and CQ zones based on a good Gridsquare. I know there is confusion when some one is operating from a differ

Can't imagine your backlog. Hope you had a good getaway. Bet you're ready to start your next vacation. 73 Herb WB8ASI

Norton gave me the usual warning that it's very new, but let me "Trust Now" and move along. No problems. 73 Herb WB8SI

Edmundo, When you work the station on 20m it will then show up with the Worked B4 color. When you see him again on 30m, the Worked B4 will be missing on the new band so he will appear as a new contact