May I ask you what's wrong with Windows 8? I've tested T-Clock there and it was working fine^^
Actually my HD space is limited and my PC isn't the best as well, so I can't install Win8 on a virtual machine... all my testing was limited to remotely testing it on a friends machine.
So what doesn't work there?
I've also read your article
(at least the updated stuff) and want to let you know that my "fork" as you've called
(which isn't that wrong) doesn't currently use stuff from TClockLight kt... I've just thought about using its NTP stuff/tool since it's improved over T-Clocks. But never did so as of now
Did Stoic Joker really talk about rewriting T-Clock? Sure there's stuff that has to be improved... but I see no real reason to rewrite it from scratch
(I do so little by little ) One could improve the way it hooks into the clock, how the DLL and executable work together to further improve performance and stability on possible crash... but T-Clock is already light in RAM and CPU usage
PS: I'm still not done with T-Clock... for example one still wants proper TZN support, but I'm still kinda stuck there as there isn't just one unified timezone name per time offset... PST/PDT etc. for USA seems ok... same as UTC for England.. maybe even CET for "Central European Time"... but there are other countries beside some in Europe that use UTC+1 and it gets even worse going further east... There are multiple names for the same time offset... not easy to unify that for T-Clock... some will be happy, others not.
So if someone got a good timezone list with just 1 name per offset, I'll be happy
(even though it cannot be done perfectly...)