Log4OM

I use JTDX and JTAlert with log4om 2 and tell you that in v 2.4.0.0 when selecting a new DX in JTDX automatically the log40m 2 shows on the main screen the data of the DX and its QRZ.com photo perfectly and instantly, but In the new v2.5.0.0 it fails, it does not always work or refresh correctly between one DX and another.

Windows 10 64Bits
TQSL 2.5.1

I am a QRZ.com paying member with subscription on payday.

Seeing the problem I decided to restore the windows to a previous state and go back to v2.4.0.0 and everything works fine again.

Thank you very much for your work and effort in this wonderful program.

https://subefotos.com/ver/?515b90499c92 ... e30b8o.jpg

Did you ncheck your settings against the instructions in the LATEST USER GUIDE

If I check it, but in v2.5.0.0 I have not gotten it to work well and smoothly as in v2.4.0.0, that does work perfectly.

I've been reviewing the LATEST USER GUIDE but it doesn't work as I said before in the last v 2.5.0.0

Nor does anything happen as I have returned to 2.4.0.0 I am left with the one that, if it works well, my intention was to warn you of the problem that I found in order to help improve.

I experienced the same here. Are there any workarounds etc.?
73 de HB9FPC

OM,

Running 2.5.0.0 and seeing no issues with forwarding of DX Call from WSJTx via JTAlert to V2. All info is displayed including photos, if available.

Note - I use HamQTH as primary Info Provider. If you use QRZ and are still having difficulty, you might try HamQTH to help isolate this issue.

Doug
W7DRM

In my case, JTAlert is not involved at all. Did work fine with 2.4.0.0 doesn´t work with 2.5.0.0. The first contact is displayed, the next one(s) most of the time not.

Try HamQTH as Info provider.

Doug
W7DRM

I will try. But it does not explain, why QRZ works fine with 2.4.0.0 and not with 2.5.0.0. Are you trying to push Hamqth for reasons unknown? What about their data base? Is it as big as QRZ´s. I still consider QRZ as some kind of international standard and feel a little uncomfortable to be pushed in a different direction. Anyway, thanks for the hint. As I said, I will give it a try.

hb9fpc wrote: 26 Apr 2020, 08:35 I will try. But it does not explain, why QRZ works fine with 2.4.0.0 and not with 2.5.0.0.

This is to test if it is an issue with Log4OM or with your connection/login to your on line provider, its like asking you to try a different fuel in your car.

Are you trying to push Hamqth for reasons unknown?

No I am sure Doug was not promoting HamQTH and just trying to resolve your problem as above.

I still consider QRZ as some kind of international standard and feel a little uncomfortable to be pushed in a different direction.

No one is pushing you and I find it quiet offensive that you should think one of our testers was doing anything other than trying to help you.

Its your choice if you want to try the suggestions we offer, but not mandatory, you have a choice!

Sorry about that. It wasn´t meant as an offense. But changing the source of information is probably something I could figure out by myself. I assumed that the advice was based on some kind of background knowledge like changes in the code etc. Obviously it wasn´t. Thanks for the support anyway. By the way: I checked and changing the info provider to hamqth in 2.5.0.0 didn´t help in my case. (Yes, I registered an acount with them as well). I went back to 2.4.0.0 and remed out the version check in config.ini. Everything is fine now. Thanks again from a supporter of your great software.