Windows Mobile Dvice vs DST
Crazy AL
I have a MIO GPS 168 RS
It is showing 1 hour off for time because it already adjusted my time to
fall back prematurely. No doubt based on the standard time before SOMEONE
decided to screw around with what was working fine since 1990. Nevertheless,
this is the situation.
I have tried numerous MS patches (August 2007,February 2008, August 2009m etc)
Patches: WindowsMobile-KB975353.msi package, windowsmobile-kb949168.msi,
windowsmobile-kb958729 and i'm sure some others. NONE OF THEM FIX THE
PROBLEM!!!
The August 2009 patch told me I have something relating to 4.21 (aku 0.0.0).
Whatever that means.
Can SOMEONE PLEEEEEEEEEEEEASE tell me WHICH patch will correct my time on my
GPS pocket PC?
MIO is useless. Called Microsoft and they want $35 for support for which
there is NO GUARANTEE that they can fix the issue.
BTW I have Vista Home Premium on my pc if that makes any difference.
HELP
thank you
AL
Todd Allcock
fixes designed for WM5+ devices are likely to work.
If you're in the US, one of the old DST patches for 2003 should be fine if
you can track one down, however it doesn't have the recent Australia
changes.
If you're in the US, desperate, and have nothing but time on your hands, you
can manually fix the zones by editing the registry with the values shown
here:
http://support.microsoft.com/kb/923953/
(I actually did this for an old WM2003 smartphone I still have as a backup-
I only modified my "home" zone because it's a PITA tapping the entire
billion-digit registry key on a phone with no touchscreen.)
Lastly, as Bev Howard pointed out in a similar thread in the
microsoft.public.pocketpc group a day or two ago (where this post really
belongs- "Handheld PC" refers to an obsolete Windows CE-based clamshell
device form factor discontinued in 2001 or so,) , you could simply choose an
adjacent time zone on the device temporarily until the real DST change date
comes up, then switch back to your usual time zone. This will keep your
appointment times, etc. in sync.
"Crazy AL" <Cra...@discussions.microsoft.com> wrote in message
news:234A6AAF-5D16-4FED...@microsoft.com...