I thought that updating my computers for this year's extended daylight savings time would be easy. It was, all except for the one I actually use to track my calendar. That was a little squirrely. Because I use about seven different email servers, I keep all of my appointments and most of my stored email on one Outlook 2003 instance running on a Windows XP desktop in my office. I have an iPaq that I thought that updating my computers for this year’s extended daylight savings time would be easy. It was, all except for the one I actually use to track my calendar. That was a little squirrely.Because I use about seven different email servers, I keep all of my appointments and most of my stored email on one Outlook 2003 instance running on a Windows XP desktop in my office. I have an iPaq that I keep synchronized to that Outlook instance so that I can take my calendar and task list home with me. Old stuff, I know, but it still works.A Microsoft patch last month automatically updated all of my Windows computers to the new DST schedule. Once it ran, three weeks of my appointments showed up shifted an hour: my 2 PM conference call at 3, and so on. I was under the impression that a later patch to Outlook would automatically correct this, but it never happened; my understanding now is that it was a manual patch. When the DST transition happened early Sunday morning, the Windows computers all updated their clocks properly, but the iPaq didn’t. I manually shifted the time an hour forward, and went about my business. When I put it in its cradle on Monday, however, it changed the time back when it synched. I changed it forward again, and went through my day. Outlook was still showing appointments an hour late, but the iPaq was showing them at the correct time, so I went by the iPaq.When I took the iPaq home, its time was again off by an hour. Once again, I manually corrected the time on the device.By Tuesday, I’d had enough. I manually corrected my three weeks of appointments in Outlook, and then went looking for a fix for the iPaq, which was now showing all its appointments an hour early as well as showing the time an hour early. Yes, indeed, there was a Windows Mobile patch for the extended DST period, and applying it and resetting the device fixed the problem. I’m just as happy I didn’t apply it earlier, however. Apparently, an earlier version of the Windows Mobile patch, issued in February, was defective, and was replaced early in March.What about the patch for Outlook? Given that I’ve manually corrected all the affected appointments, applying it now would screw them all up. I’ll pass.I really hope I don’t have to go through all of this again in the Fall. Software Development