Log4OM

I too went back to a previous version and the problem appeared there too.

I tried running the .exe as administrator and although it spent 1 minute after "Save and apply" doing nothing when I did go back to adif settings the checkbox had cleared.

I am now beyond my last straw. I have completed all the diagnostics I can conceive of and I'm at my wits end.

Please I beg you help. If necessary I'll drive the 4 hours to Essex.
I REALLY don't want to USE HRD, that was the worst £85 I've spent

I'm getting desperate now, if you hadn't noticed.

Please email me a support request from the help menu so that I can replicate your set up on one of my PC's to test

Meanwhile you could use the UDP connection which is detailed in the user guide, its far better than ADIF monitor.

Did you see my concerns about losing real time QSOs using UDP if Log4OM is not running because I forgot?

I created a support pack. Where do I send it?

If it.comes down to it I could mail you my laptop.

G6FZU wrote: 03 Dec 2023, 20:36 I created a support pack. Where do I send it?

Email to my address on QRZ please

OK. Give me 30 minutes to find it.

Support request received I will check it and respond to you as soon as I can

Using your configuration file on a Windows 10 PC I was able to replicate your issue.

I can now confirm that there is a problem which we will investigate and hopefully fix in time for the next release.

Meanwhile you can either handle the QSO's manually or use a UDP connection which I am sure that you will find trouble free.

1st: im not insane. Do you appreciate that I was convinced I was going crazy?
2nd: is there a fudge I can apply, e.g. manually set something in a configuration file?
3rd: will I lose QSOs if I log them in JTDX but Log4OM is not running if I use UDP?