Hi, let me answer you on cons, that are the most important part of your thread.
hb9ryz wrote: 18 Jan 2020, 06:52
a) Logging with JTDX v2.1.0 does not work
I'm running JTDX without issues. If you have some more details maybe we can find where the error is.
hb9ryz wrote: 18 Jan 2020, 06:52
b) Logging with WSJT-X v2.1.0 with the second UDP-Port as written on page 134 in your new manual, does not work
Again, this is working for several thousands of users. I start believing you have something preventing communication, like a firewall or an antivirus not correctly set. Again, your log could help us finding the issue
hb9ryz wrote: 18 Jan 2020, 06:52
c) DX-Cluster view is not that confortable like in the version 1.40 - I have to refresh manually to see the cluster informations the first time
Nobody else reported that, once again a log of your application can help us.
hb9ryz wrote: 18 Jan 2020, 06:52
d) In the status bar I can't see if the Comm Services (UDP-Ports) are up-and running
Correct. Log4OM can open an unspecified number of ports, inbound and outbound. Putting an array of bullets in the status bar is not possible. You can see running services in the HELP MENU -> "Open diagnostic page". A generic bullet that reports "at least one service is active" would not have sense.
hb9ryz wrote: 18 Jan 2020, 06:52
e) not supporting the SQL-DB from version 1.x (JTDX will not support the new DB version)
You probably mean JTAlert. In that case we can't do anything on that... JTAlert author is working on.
hb9ryz wrote: 18 Jan 2020, 06:52
So I went back to the old version v1.40, where erveything works fine for me
Hope to see you soon here

As you can imagine, working without data is hard for us. Please check the application log for issues, if you share them we can help you but "it's not working" is not enough for us to find a solution
Best 73 de HB9RYZ
Wolfgang
www.hb9ryz.ch
[/quote]