windows DST Handling is idiotic... it actually moves the hardware clock instead of just correcting itself according to TZ information. its that stupid.
This has always been a problem and indeed, because of this some clock times really do re-occur twice which mixes up many applications. At one place where I worked, the db admin would shutdown the server during DST switch night and bring it back up the next morning... otherwise it would take him all day to fix all the db time breakups and license servers which all failed starting at midnight :-) -MAx On Sat, Oct 2, 2010 at 8:35 PM, Carl Read <[email protected]> wrote: > > On Sunday, 3-October-2010 at 13:12:09 Graham Chiu wrote, > >>Hi Carl >> >>It was very odd ... Rebol was reporting TZ as +12 for part of the day, an= d >>then it suddenly changed to +13:00! >>I was watching it on Altme too .. posts were out by an hour and then >>suddenly they came into sync. >> >>Check your tz now, I'm guessing it is now +13:00 > > Hmm. Yes, it is +13:00 now! > >>Probably an obscure Rebol bug. > > More likely a Windows' one, since REBOL goes through Windows to get the t= ime, I'm assuming. And when daylight saving ended this year in April, this = XP's clock was two hours out! And according to Microsoft's webpage, clocks = are put forward in October in the Southern Hemisphere, despite ours moving = forward in September... > > http://support.microsoft.com/gp/cp_dst > > But then, daylight saving's voodoo, anyway. You're saying there's a day a= year with an hour missing from it? Oh yes, and not only that, but there's = an hour once a year that repeats itself. "Yeah, right!" > > -- Carl Read. > -- > To unsubscribe from the list, just send an email to > lists at rebol.com with unsubscribe as the subject. > > -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
