Daylight Savings Time/Summer Time this year has been extended a week in the eastern states that do that sort of thing, so that we can all watch the Commonwealth Games at the same time. The trouble is no one has told Windows this and computers all over the South East will dutifully put the clocks back one hour, making everyone an hour late. Never Fear! Microsoft to the rescue! They have issued a patch to correct this problem. All Windows users in NSW, Victoria and Tasmania should patch their systems, or follow the official Microsoft advice "Do not create appointments during the overlap period until after the operating system time zone has been updated."
But don't forget: after April 2 you have to unapply the patch so your system clock will automatically update to the correct time.
Since I'm a bit techy and not afraid of doing things myself, I'll be double-clicking on the clock at the bottom right of the screen and manually advancing the time. I feel confident that I can do this without help, or at least without too much help, and I'm sure there won't be too many problems.
james_b and
makovette, if something does go wrong can I call?
But don't forget: after April 2 you have to unapply the patch so your system clock will automatically update to the correct time.
Since I'm a bit techy and not afraid of doing things myself, I'll be double-clicking on the clock at the bottom right of the screen and manually advancing the time. I feel confident that I can do this without help, or at least without too much help, and I'm sure there won't be too many problems.
no subject
Date: 27 Jan 2006 03:21 (UTC)no subject
Date: 27 Jan 2006 03:22 (UTC)You may be sent to your room with a time-out...
===|==============/ Level Head
no subject
Date: 27 Jan 2006 03:23 (UTC)no subject
Date: 27 Jan 2006 03:24 (UTC)no subject
Date: 27 Jan 2006 03:26 (UTC)The great and powerful Bob will be angry!
no subject
Date: 27 Jan 2006 03:35 (UTC)no subject
Date: 27 Jan 2006 03:40 (UTC)no subject
Date: 27 Jan 2006 06:07 (UTC)no subject
Date: 27 Jan 2006 07:15 (UTC)no subject
Date: 27 Jan 2006 07:27 (UTC)no subject
Date: 27 Jan 2006 07:41 (UTC)no subject
Date: 27 Jan 2006 07:56 (UTC)no subject
Date: 27 Jan 2006 10:12 (UTC):-D
CYa!
Mako
Timely Zzyzxian
no subject
Date: 27 Jan 2006 22:07 (UTC)Seriously, it probably doesn't matter unless you run servers. But computers these days like to know the 'real' time (number of milliseconds since Jan 1 1970 00:00 GMT) as well as whatever time it is where you are. That's why there is a difference between just setting your clock (which will change the 'real' time) and a patch that alters the dates on which time zones apply (which will change the timezone offset it uses for those particular dates).
I'm kind of surprised you have to unapply the patch afterwards - it should really apply 'for ever more', so that if (say next year) you ask it to convert a 'real' GMT-based time to local time, and if the real time is within the affected week *this* year, it would still know about the different time zone for that week. But perhaps they've done a mickey mouse patch rather than a proper one that applies specifically to this year.
Incidentally it certainly doesn't just affect MS. Time zone things are supposed to be decided years in advance, so it's a little bit unhelpful if a local government changes it on a random whim! Expect a lot of clocks to be wrong during that week. Time's important, and can get hideously complicated, so it would really be better if nobody changed time zones without at least several years' notice. That way software manufacturers could correct their systems properly, not with a hurried patch.
no subject
Date: 28 Jan 2006 00:04 (UTC)Remember which company we're taking about here... have they ever done anything else?
no subject
Date: 28 Jan 2006 01:47 (UTC)no subject
Date: 28 Jan 2006 20:46 (UTC)no subject
Date: 28 Jan 2006 23:00 (UTC)I guess it may be due to a limitation in their overall system, i.e. it can't be configured to have different times for DST in different years without making more fundamental changes. So that'd be an excuse, kind of... but still, nasty. (And still deserves a good kicking for the authority that decided to change it with no notice!)
no subject
Date: 8 Feb 2006 01:41 (UTC)(there are also plenty of problems with GMT/UTC/etc as it is, so an hour isn't really that much)