Log4OM

In the shack i have an old computer (4 Years) with win10, which works with log4om.
But the performance of the system was really bad. So moved to win 7.
Log4om worked after the reinstallation.

In the last few days I may have reinstalled wsjt or n1mm, after which log4om no longer works properly.

but I set up the whole computer from scratch. with win7 and everything else.
but i also reinstalled wsjt and n1mm.

the last few days i try to reinstall log4om, but nothing helps

thanks for your help

oe5mzl wrote: ↑04 Oct 2021, 19:24 In the shack i have an old computer (4 Years) with win10, which works with log4om.
But the performance of the system was really bad. So moved to win 7.
Log4om worked after the reinstallation.

In the last few days I may have reinstalled wsjt or n1mm, after which log4om no longer works properly.

but I set up the whole computer from scratch. with win7 and everything else.
but i also reinstalled wsjt and n1mm.

the last few days i try to reinstall log4om, but nothing helps

thanks for your help

Martin,

So you have scrubbed Windows 10 and went backwards to Windows 7 installation?

Your problems might be related to that old Windows 7 O/S. May be a lot of driver issues involved with that, but I can't say for sure.

If Terry has time he might also offer some observations with respect to going to an older O/S.

Hello!

It would be great if he had time to give some advice.

Best regards
Martin

What is the Log4om release number? See help/about

Release note – Version 2.17.0.0

oe5mzl wrote: ↑06 Oct 2021, 15:52 Release note – Version 2.17.0.0

And what happens when you click the test buttons indicated below by the red arrows?

send me by EMAIL not by posting here - BY EMAIL

1. The config.json file located at C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2\user

2. A log file - Help/open log file

to g4pop (AT) arrl.net

OK I actually missed the issue in the screenshot that you posted but having installed your config file that you emailed me onto my PC to replicate EXACTLY your settings I noticed that you have both primary and secondary lookups DISSABLED!

I selected the sources and everything works fine including the test lookup.

This is your set up using your config - The disabled checks are stopping it using the lookups!




This is after I changed the settings, note the test is working.





And just to prove it all works here is a live lookup of your call.



One thing to add is that you are only a ham member at QRZ to obtain full lookups you must have a PAID XML subscription to QRZ e.g. this is why your locator is not shown on the lookup.

If when you have enabled the lookups as above you still have problems then something is blocking the lookup on your PC try reducing the UAC (User account control) to the minimum or check for other malware protection blocking you.

This has to be a self inflicted issue or at least a local set up issue because yours is the only complaint of this kind from our full user base which is tens of thousands of users.

Hello de it9bor
I also have the same problem and couldn't figure out what may have happened.
I have done all the possible tests, I have not made any changes to the software and to the system, and for some weeks I have not been able to connect via log4om with the QRZ.COm and HAMQTH providers.
Why??
73 de it9bor