Swisslog slower after Update to V 5.113

[DL5OAH]

Hello Community,

I´m not sure, if it´s a Problem with Swisslog or maybe my PC, but since the newest Update,
Swisslog works very slow.
The Problem manifests itself as folows:
When the programme is running and no input is made, except for updating the DX-Cluster, nothing can be detecting.
Only when I enter a Call and all the necessary data, does the programme freeze and it takes approx. 4-6 seconds
before another entry can be made.
Question: Could it also be that the update requires more "power" from the PC?
Sorry, i´m not particularly knowledgeable about PCs
Important: The problem only occured after the last update!

Thanks for helping!

Klaus - DL5OAH

[EA3GCV]

Hi Klaus,

Please read carefully this thread:

https://www.swisslogforwindows.com/forum...hp?tid=912

Normally adding the exceptions and compressing the database is enough. The next important thing is the Automatic update function from the World Map function. If after doing all this you experience issues, close World Map or disable the CAT button in World Map and try again. This function can cause slowdowns in old CPU. If all these doesn't help, it could be a corrupted configuration file SwisslV5.ini.

In such case, take screenshots of all your transceiver, rotor, online logbooks configuration, etc. Afterwards, rename the SwisslV5.ini file to SwisslV5_old.ini in the C:\Swisslog folder. When you start Swisslog it will create a fresh configuration file but you will have to register and configure Swisslog again. Initially register and configure transceivers and try to save a QSO to see if all works well. If so, continue configuring Swisslog.

I highly suggest to make a backup copy of the whole C:\Swisslog and all its contents. In case of troubles you can always restore a particular file.

73

[DL5OAH]

Hello Jordi,

the problem is solved.
It was enough to compromise!

Thank you for your help!

best regards
vy73 Klaus DL5OAH

[EA3GCV]

Hi Klaus,

Could you explain to all users which option was the one which solved your issue?

73

[EI4KF]

I think Klaus meant compression instead of 'compromise'. Keep your databases at optimum performance. I believe Swisslog prompts to do this at regular intervals? Regardless, every Sunday I compress my logbook as a matter of good housekeeping.