WSJTX/JTALERT/LOG4OM logging not working

[W4GHV]

Problems persist.
One went away NOT EXITING when we turned off LOTW update on exit. We will deal with that later.

Following is my setup guide, based upon the docs to the best of my knowledge.

The setup works perfectly for ME, but his is still disabled.

Callsign entry in WSJTX does not transform to the logger, nor does the 'log this qso' transfer to the log. Our setups, rigs, software are the SAME
Windows 10 PC, 16gb memory, fast CPU, latest Log4OM (admin mode), Omnirig (admin mode), Win4Icom latest version, WSJTX & JTalert latest versions, & IC-7610.
-------------------------------------------------------------------------
Win4Icom, IC-7610, Log4OM, WSJTX, JTAlert setup guide 6/6/22

Win4Icom
CI-V COM 6 115200
Virtual COMM ports 16,14,13,10,18,20 all 38400
Omnirig COMM 10
Auto Launch Omnirig, Log4OM

Omnirig
Set to run as admin
COMM 10, 38400,8,N,1,low, low,100,100

Log4OM
Set to run as admin
Config, connections
UDP_INBOUND ADIF_MESSAGE 2235
UDP_INBOUND JT_MESSAGE 1240
UDP_INBOUND N1MM_MESSAGE 12060
Note, the Outbound message (in the docs) is not set since it said V1

Applications UN-click Import

External services LOTW
My call, 1st, 2nd, 4th clicked
Upload flag REQUESTED (also in Confirmations)

JTAlert
Logging - unclicked Last QSO, unclicked standard adif file
Log4OM Enable,Send, 127.0.0.1, 2235, 2241
Applications, WSJTX Resend WSJTX UDP packets, 127.0.0.1, 1240

WSJTX
Settings, reporting, Enable PSK reporting, 127.0.0.1, 2237, 3 clicks to the right
----------------------------------------------------------------------------------------------------
Comments greatly appreciated.
Bo W4GHV since '54

[W4GHV]

I will start with "I hope so!"

First I solved my buddy's problem with lack of logging by deleting and re-installing JTalert, including its files that are not normally uninstalled.

Second I solved Omnirig problems, by having everything NOT running in admin mode. It boots/runs faster now.
The Omnirig docs has an excellent debugging tool/procedure I should have used from the start.

Third, for the Icom rigs, this required a simple fix to Omnirig .ini for the radio, to force it to stay on filter 1 for data modes.

Thanks for all the help.

Evidently, running in admin mode is very complicated and probably dependent on individual computer setups.

At 82 this very old dog CAN still learn new tricks, but I have to write it down before I forget it.

If you haven't been reading my posts, this is about Win4Icom, Log4OM, Omnirig, JTAlert, & WSJTX on a Window 10 PC.