Linked by Thom Holwerda on Sun 11th Mar 2007 20:14 UTC, submitted by jayson.knight
Microsoft The extension of daylight-saving time by a month in the United States is causing enormous grief for some IT administrators running Microsoft software, as many of the software programs running on their users' systems need to be individually patched to reflect the change. This year, daylight-saving time starts today - three weeks earlier than usual - and ends a week later than usual on Nov. 4.
Thread beginning with comment 220325
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Strange
by Jesuspower on Sun 11th Mar 2007 21:47 UTC in reply to "Strange"
Jesuspower
Member since:
2006-01-28

1. Yes, it should, but if it was, it probably would not be used.

2. Why is this not user configurable? Were people thinking, "Oh, DST is always on this day, itll never change... LETS HARD CODE IT!"

Reply Parent Score: 1

RE[2]: Strange
by PlatformAgnostic on Sun 11th Mar 2007 22:13 in reply to "RE: Strange"
PlatformAgnostic Member since:
2006-01-02

Most of these patches just change things in the registry, where TZ information is stored.

On the other hand, software like exchange which does calendaring might get screwed up when the time changes suddenly and not on a pre-defined DST change date... this is the sort of thing that's causing all the problems. Your time changes and suddenly all your appointments are a little bit off.

Reply Parent Score: 1

RE[3]: Strange
by stestagg on Mon 12th Mar 2007 02:51 in reply to "RE[2]: Strange"
stestagg Member since:
2006-06-03

Most of these patches just change things in the registry

So Microsoft must be able to find out the location of every set of TZ data that it places in the registry, for all its software, then issue one patch to change all of them in one go. Why TZ info is stored in more than one place in the registry beats me.

Reply Parent Score: 2