OOPS. My mistake. Yes they are about the same. Guess I'll just let it download and see if it makes it. Your downloads are always real quick. Wonder what's up for me with this one. No other obvious pro

Beta build 0003 was 16.7KB. This one 0006 says 16.4MB. Yes MB, and download time estimated 20min+. I'm running great on 0003 and don't need the Marathon, but wonder what's happening? Tried several tim

Thanks Laurie, I'll try again. Usually they are very quick, thus when it said 20min, I was perplexed. I tried going to HamApps group direct rather than thru the email, but still the same. Must be just

Laurie, I'm enjoying 2.15.7 Beta build 0003 with Log4OM V2 running just great!!!! Many thanks for your quick response to the Log4OM changes. As I find myself operating with my setup here tonight, I of

Something seems wrong. Download time is taking forever.

Did a reboot, and now port 2235 started working. Settings were OK. I just need to remember with Win10 to just keep rebooting when things are not running as expected.

When I disable the Last QSO API which I have set on port 2333, JTAlert will not log to Log4OM V2 via the normal port 2235 as I set it up as you suggested. I do have UDP Inbound ADIF Messages set up in

So far so good. Thanks for the Beta. I'm running both Log4OM V1 & V2, and just about ready to abandon V1. A bit confusing trying to keep both logs aligned with each other, and with JTAlert Scan Log an

Laurie, Just checked and the new additional monitor just happens to be the same resolution as the other one. I tried moving JTAlert back to the other monitor were I had it working on the Regular Versi

Just some info FWIW. I'm a Windows 10 user. Today I rearranged the additional monitors used in the shack, and no longer can use the regular version of JTAlert. The Menu is missing like I've seen many

Hey Gary....thanks for the tip. Wish I would have known you can do that. Sure will save scrolling thru the miles of log. Herb WB8ASI.

There all kinds of filtering options on the Decode History window. I like using it rather than the regular call display.

Thanks Laurie for your usual speedy response and service. The new beta 0009 seems to be working fine now. At first it didn't appear to show improvement so I restarted the computer. It still didn't app

Since upgrading to 2.15.6, I seem to be missing over half the SP bearings both on the Decodes Window and hovering over the callsigns in the Call Display area. I haven't seen any others mention this pr

I'm seeing the same thing. Herb WB8ASI

From another Log4OM user, I increased my "Check QSO Log Record" to 7 secs. and rarely have the no log warning anymore. It's always actually logged anyways. All is well. 73, Herb WB8ASI

Enable ACLog Logging is not checked. Put a check in that box and you should be good to go.

Hey Vince....Yes, once I found it, it is the best. So much easier to quickly view the list and catch what you're looking for. I've got my layout setup down to just the basics of what I want to quickly

Sounds great Laurie. Looking forward to V3. Can't even imagine how this digital stuff would work without JTAlert. The only reason I still use the decodes at the top is to click on the underlined calls

I've found it easier to just use the Decodes History window all the time. No longer need any rows in the Decodes Callsigns Display.