Page 1 of 1
QSO STime reads as 0000 after Windows 10 upgrade
Posted: Thu Aug 20, 2015 11:11 am
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?
Re: QSO STime reads as 0000 after Windows 10 upgrade
Posted: Fri Sep 18, 2015 6:09 pm
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'?
Re: QSO STime reads as 0000 after Windows 10 upgrade
Posted: Sun Sep 20, 2015 10:15 pm
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