Greetings Nolan, Juergen et al.
My previous message proved that nightly work is the root of all evil, Hi!
Forgot to pass important info:
- desktop PC, 16GB RAM, 4GHz system clock, a whole lot of HDD space
- Windows 8.1 64 bit
- Log4OM 2.2.0.0
- do NOT use JTAlert
In addition, manual QSO edit doesn't help at all - still no distance calculated (showed).
The fact that Log4OM2 works as expected in your installs is O.K.
but as it appears this is not necessarily the same in the average user case.
I agree with this statement "
The only 0 distances are logged if no
locator was found at external services or found in JTDX logs."
when speaking of YB1NWE and 3W1T stations.
But not for BA8MM, because QRZ.com has correct Grid Square.
Occasionally, simultaneously to Log4OM2 I run/launch Log4OM V1.4
where in regard aforementioned stations this scenario did not happened.
- BA8MM.png (194.98 KiB) Viewed 4223 times
Above screen shot taken shortly after conducting QSO with BA8MM.
JTDX digital clock shows different time but if you look at the left pane of JTDX,
in the very first row there is "001800" string confirming time of the event.
Sometime ago I had also at least _ONE_ such event
but decided to keep sharp lookout and only then report.
I do have also Windows 10 native installation
with JTDX, Log4OM V1.4, Log4OM2 and some other soft.
Time permitting, I will monitor whether such scenario happens also there.
What else should I, or you like me to supply in order to help
you conduct investigation in this, I would say, crucial matter?
Name it and I will do my best, please.