Hi All, I had described my problem of setting both WSJT-X and ACLog to auto-start (in this sequence) in another thread, but the subject had meandered there, so I'm starting a new thread here. It was s

I will try as suggested, and report back. Thanks, all!

I've set JT-Alert to auto-start both WSJT-X and ACLog, but the two apps can't seem to start in the right order. ACLog usually launches right away, which for some reason takes away the TCP port from WS

I like your workaround, and will use it till the feature is added (if it's added).

A possible answer - CQ Marathon counts both DX and CQ Zones (each combination counts once), so if a station in the same country but different CQ Zone appears, the alert is triggered.

Hi David, Thanks for the offer - I will send you an email in a bit. I recently changed my callsign, so haven't filled out my QRZ profile yet, but will do so soon; thanks for the heads up.

I looked at this more closely this morning, and can confirm again that JTAlert and ACLog are synced correctly, and have also come to conclude that there is NO issue between ACLog and LoTW, as I could

Thank you all very much for your input, Mike, Larry, and Laurie. I will surely check that MA is logged correctly in ACLog - I suspect that this is where the problem might be... however, if it is NOT l

Larry, I track by INDIVIDUAL BAND, and also INDIVIDUAL MODE. I've done some investigating, and it appears that JTAlert and ACLog are sync'ing fine... it's between ACLog and LoTW that has me stumped. B

I've been struggling to sync JTAlert's Worked-All-States to LoTW records, but can't seem to get it right - I'd welcome any comment on this... LoTW shows that I no longer need a particular state for WA

I use N3FJP programs while contesting, and realize that each new contest-specific database (I've only used the RTTY-RU program thus far) will show me WAS; however, JTAlert is much easier to use, with

Dave, Could you elaborate? What changes do you make to JTAlert? Thanks.

During contesting this past weekend, I realized that I had no way of knowing which states I still needed to work in order to rack up multipliers, as my JTAlert's database is set to only trigger alerts

I just edited my original post, as I mistakenly wrote JTALERT in place of WSJT-x in the first line. To sum, WSJT-X decodes panel shows station as JTALERT-highlighted/grid-needed, while the station is

I just began collecting grids, and have noted the following: At times, a station with a grid-needed highlight shows up in WSJT-X decodes panel (left-hand side), when it has in fact been worked before;

In my experience, color highlights at times seem incorrect due to Alert Priorities being set inappropriately... I suggest that you check those, as a first step.

After rebooting the computer, everything seems to be working now; whew! Laurie stated that Tab 1 was required, not TX1; my mistake.

Thanks to Scott, I've discovered that I need to set up JTALERT specifically for his contest software. I've now done so, but problem persists... I think it's because WSJTX seems to be stuck transmittin

I'm trying my hand with the FT Roundup this weekend, using ACLog, and noted something peculiar: JTALERT is not picking up U.S. States from QSOs, and the popup shows that it's unable to log the QSO to

Thanks, both problems resolved.