VERY SLOW winlog.in

[F5LCI]

Hello OMs,
Every time I adjust a parameter in Winlog32, it takes a lot of time, and very often is not taken in account.
Opening or closing the program is very slow, too.
At this point, I make only one modification at the time, and wait a very long time to dare doing another mod
I completely deinstalled / reinstalled the program (on another HD) without any effect.
W Defender and antivirus : no warning messages. Neutralized without any effect.
My current version : 7.3.49. Update for the latest : no effect...
Using Windows 10, K2 and KX3 ("K3"), and port splitter VSPE (Eterlogic).

Looks like that any modification of the winlog.ini file takes a lot of time (when it works !).

Any suggestions ?

73 de Jean, F5LCI

[G0CUZ]

Hi Jean

Not sure what the problem is at this time, you don't say if this is a new behaviour or it has always been so on your installation?

I can only suggest that you disable various options you have enabled until Winlog32 is restored to normal behaviour.

It could also be anti-virus, verifying when files are being modified, what is the installation path of Winlog32 on Windows 10?

Try also enabling debug more (menu/File/Maintenance/File Maintenance), if this was already enabled it may show some clue, if not already enabled, you will have to wait for next occurrence of problem to see any result.

73 Colin
G0CUZ

[F5LCI]

Thank you Colin for your so fast answer !

Adding a single option to the plain program takes a long time, and so on.
But with patience I finally managed to add my 2 rigs and a DXcluster., one by one.

Anyway, closing WL has always been slow, except in some rare occurences that surprised me, and without noticeable reason...

My antivirus (and Defender) does not show anything, same with Virustotal.

Path is now on a separate SSD disk : F:\Winlog32, faster than before.

Best 73,
Jean, F5LCI

[G0CUZ]

Hello Jean

Curious to know what is causing this, shutting down winlog32 (when it writes the ini file to disk), should only take 2 - 3 seconds even on a older computer, I just shut down my installation on an old laptop (with SSD) and it took 2 seconds to close down.
Writing an individual setting, which sometimes takes place on-the-fly is usually added only to memory with no save to disk usage, and should not be noticeable, so something unusual is going on if it is greater than that.

Winlog32 does not use much in the way of resources as it is older software mostly developed when PC's were of MUCH lower spec. than nowadays.

As I said -enable the debug mode in case there are trappable errors occurring which may give a clue to the problem, the debug text file is readable, if there is anything in it after a few uses - copy/paste into an email and send to me for evaluation.

73 Colin
G0CUZ

[F5LCI]

Good evening Colin, and good news :
No more problem after I stopped VSPE port splitter (and reassigned the ports, of course).
Now I wonder how to use Winlog32 and NAP3 in the same time

Thanks for your assistance, and season's greetings !
73 de Jean, F5LCI

[G0CUZ]

Thanks for the feedback Jean

I am not familiar with VSPE, but port splitters are usually problematic in my experience.

What is NAP3?

Thanks for the greeting and all the best you you and yours for the forthcoming festivities and new year.

73 Colin
G0CUZ

[F5LCI]

NaP3 is "Not another P3", a rig interface with powerful panoramic display, another brilliant British software.
https://telepostinc.com/NaP3.html
Interesting, but not essential
Best wishes,
Jean