Page 1 of 1

ver 2.6 loging problem

Posted: 16 May 2020, 20:00
by sq7bcn
After a few minutes of work the program can not be logged QSO does not enter the database.
You need to restart program and it's ok for a few minutes, then the same.
This applies to manual login from the Log4Om as well as from external programs, e.g. JTDX

Re: ver 2.6 loging problem

Posted: 16 May 2020, 21:44
by NN7D
Dear ??

The version number consist of 4 segments. You referenced only two.

There was a brief time (minutes) that version 2.6.0.0 was available before 2.6.1.0 replaced it. If you are running 2.6.0.0, please update to 2.6.1.0. Then retry.

Also, please sign with your name.

Thanks.

Doug
W7DRM

Re: ver 2.6 loging problem

Posted: 17 May 2020, 06:45
by DF5WW
Did you have checked that latest Windows 10 (if you use it) update has changed all administrator
settings ? Running here 2.6.1.0 without any problems of direct logging in the UI and/or logging
via JTDX with/or without JTalert.

Please go to your relevant .exe files (e.g. LogomUI.exe, Omnirig.exe, JTDX.exe)) and check in the
properties that the softwares running as administrator. Ifr these settings are all o.k. please tell us
again.

;) ;)

Re: ver 2.6 loging problem

Posted: 17 May 2020, 12:57
by sq7bcn
I use version 2.6.1.0 and Windows 7
Marek
SQ7BCN