QSO STime reads as 0000 after Windows 10 upgrade

You may post here if you are having problems with Winlog32 that others may be able to help you with. You may also report bugs so that the author may act upon them.
Post Reply
OH2IS
New user
Posts: 1
Joined: Thu Aug 20, 2015 11:04 am

QSO STime reads as 0000 after Windows 10 upgrade

Post by OH2IS »

The date field is correct, but automatic QSO start time reads 0000, and updating with right click yields the same 0000. Any pointers?
G0CUZ
Site Admin
Posts: 461
Joined: Wed Jan 02, 2002 7:12 am

Re: QSO STime reads as 0000 after Windows 10 upgrade

Post by G0CUZ »

Just assure everyone, I don't think this s an issue with Winlog32, I had one other report, but it seemed to correct itself - perhaps after a restart.
Has anyone an ongoing problem with 'Time'?
G0CUZ
Site Admin
Posts: 461
Joined: Wed Jan 02, 2002 7:12 am

Re: QSO STime reads as 0000 after Windows 10 upgrade

Post by G0CUZ »

Just to add, I have found an issue when Windows Locale Time format is set to display with a decimal point e.g. 00.00 where more usual format like 00:00, it is almost certainly this causing the problem, and possibly is due to some changes introduced in Win.10
I will be fixing this shortly.
Sorry to the Scandinavian guys who are most likely the ones suffering this problem.

73 Colin
G0CUZ
Post Reply