In case you were not aware of the Daylight Savings Time problem coming up:


Many systems and programs are set up to change time automatically for Daylight Savings Time.

BUT...

This year is actually earlier than programmed dates.  Actual change will be on 2am on March 11.  So you can make that happen yourself by going in and manually changing the time, changing from 2am to 3am.

BUT ....

A few weeks later the automated change is going to kick in, changing 2am to 3am.  So be prepared to go in again and set the times back to the already adjusted correct time of 2am.

You will have a similar problem in Oct and Nov. when the system will set the clocks back a few weeks early, you will need to make the manual correction, and then make the real change manually a few weeks later.

Also, if you are using SNAP External Server Drives, you should not make the changes manually.  You need to download a special utility to deal with those Server clocks.  I think you can use this link: http://now.eloqua.com/er.asp?s=563&lid=25&elq=3BBD9B6FF4424100B0E785996F0D57E4 to get the info needed from Adaptec for the Snap Servers.

I just added this link: http://apnews.myway.com/article/20070214/D8N96T1O0.html that provides some information about the problem, and the MS patches that Foster referenced.

But although this and other articles caution that time won't be set on the real day, none of them mention the problem that the programmed date will undo the manual changes that you make, so in fact there are two problems within a few weeks that may require manual adjustments, not just one.

For Windows users ... if you installed the MS patch to your system, make sure that it was the version that was issued in Feb 2007.  This version supercedes the earlier patch that they made available in November 2006. 

Info and patch downloads available here: http://support.microsoft.com/kb/931836/

And remember, this patch is only for XP/NT/2K and newer systems.  No patch available for 98/95/ME/SE/DOSx.  These systems will still need manual management.