|
From: Byron Followell on 29 Feb 2008 05:06 Todd, The main reason I ran the patches to begin with were that some of my appointments were messed up to begin with, taking place a day earlier. Mother's Day was on a Saturday. Memorial Day was on a Sunday. That sort of thing. It seemed to impact mostly annual recurring events but there were others too. Several readers steered me towards this being DST issues. Also, since, Microsoft has released patches for WM6 and Outlook 2007, I'm assuming there must be something wrong or incomplete with the their default DST implementation. Otherwise, why would they have wasted their time to developing the patches and the amount of help information on their website related to them for these products. So, that's why. Most of my issues have corrected themselves once I reset the time on my computer and my pda. The patches changed my current time and my time zone on both. Also, my all day events were all changed to 24 hour events running from midnight one day to midnight the next. I had to manually convert all of those back to all day events. I think everything is back to normal now though. It is VERY frustrating to have to spend hours to repair years of calendar history after something like this though. There really should be a file somewhere detailing exactly what these patches are going to do to your events so we'll know before we actually run them. - Byron "Todd Allcock" wrote: > At 26 Feb 2008 04:50:02 -0800 Byron Followell wrote: > > OK, here's a little more information. As I stated, the time on my AT&T > Tilt > > was set forward by two hours and ALL of my appointments were set back by > two > > hours. I double-checked and DST was on and my time zone was correct. I > > correctly set the time on my PDA and most, not quite all, but most of my > > appointments seem to have gone back to their correct times. > > Not to kick you when you're down, but hopefully to save the next person; > why did you run the patches? AFAIK, neither Outlook 2007 nor WM6 require > them. Both were released after the DST change was decided upon and already > had the new DST rules coded in. > > >
From: Todd Allcock on 2 Mar 2008 04:13 At 29 Feb 2008 02:06:01 -0800 Byron Followell wrote: > The main reason I ran the patches to begin with were that some of my > appointments were messed up to begin with, taking place a day earlier. > Mother's Day was on a Saturday. Memorial Day was on a Sunday. That sort of > thing. It seemed to impact mostly annual recurring events but there were > others too. I'm having the same issues, however, after running the patches last year on Outlook and my WM5 device made an even bigger clusterf--k of everything, I'm waiting until the time change to see if everything sorts itself out first! > Several readers steered me towards this being DST issues. Also, > since, Microsoft has released patches for WM6 and Outlook 2007, I'm assuming > there must be something wrong or incomplete with the their default DST > implementation. Otherwise, why would they have wasted their time to > developing the patches and the amount of help information on their website > related to them for these products. So, that's why. Sorry, I just assumed they repackaged last year's patches with a new date. > Most of my issues have corrected themselves once I reset the time on my > computer and my pda. The patches changed my current time and my time zone on > both. Also, my all day events were all changed to 24 hour events running from > midnight one day to midnight the next. I had to manually convert all of those > back to all day events. I think everything is back to normal now though. It > is VERY frustrating to have to spend hours to repair years of calendar > history after something like this though. There really should be a file > somewhere detailing exactly what these patches are going to do to your events > so we'll know before we actually run them. Agreed!
|
Pages: 1 Prev: WM5 Voice Recorder- Change Default file Locations Next: O2 Graphite with 8 GB MicroSD ? |