Microsoft's comprehensive DST Patch for Pocket PCs
On Sunday all of my Pocket PCs, except for my rx1950, adjusted for DST. I think the problem could have been caused by the Real Time Clock update that I installed to the rx1950 a few days prior to the DST time change.
I fixed the problem by uninstalling the DST patch on the rx1950 that I'd installed last year and installing the newest Microsoft DST Patch. This patch incorporates all the DST fixes for all the countries that have changed the way they handle DST. If you have already installed a DST patch to your Pocket PC and everything is working well, there is no reason to install this latest patch unless you travel internationally and want to ensure that DST is properly addressed for every time zone you transverse.
To learn more about this comprehensive patch see A February 2008 cumulative daylight saving time (DST) update is available for Windows Mobile-based devices.
See related blog entries to learn more about how to install the DST patch to your Pocket PC:
Did you enjoy this Post? Subscribe to From My Pocket
THANK YOU, THANK YOU, THANK YOU!!!
Very timely as my update did not work until this email sent me in the right direction.
Zieg
Reply to this
Once again, Prof Julie saved me! What would we do without you?
This fixed my 5915 Travel Companion, which I only use as a GPS in my car.
My hw6925, managed by my company IT, did NOT set itself to the right time until this morning - 2 days late! IT asleep at the stick?
New issue, on my HP 5915, it will NEVER let me set the time locally. I ALWAYS have to Activesync it to set the time. It just hangs after I adjust the time with Start->Settings->system->clock&Alarms->Time->Home. Ever happen to you? Know a fix?
Thanks a lot!
Rick
Reply to this
I have a pocket pc e330. Am I out of luck? I've tried to download the patch above, and can get the downloads on my computer desktop, move them into my Active Sync Device folder, but then nothing happens. Am I doing something wrong? Do I need to place them within a specific subfolder? THANKS!!
Reply to this
You'll install the update just like any other software you'd install to the pocket pc. If you downloaded the .exe file to your computer, you'll select it on your computer, an installation wizard will open up and prompt you through the installation; if you downloaded the .cab file, you'll copy the file directly to your pocket pc, navigate to it, tap the file and an installation wizard will open up and install it to your pocket pc.
You can review this article for more information about installing software to your Pocket PC.
Reply to this
I have an rx3115 and these instructions did not work for me. I have the .cab file but it won't open on my iPaq. I can't get the DST patch from HP to download at all -- it keeps saying that the page doesn't exist. I finally gave up and switched the time zone on my iPaq to reflect the current time (not my correct time zone). Is there anything else I can do?
Reply to this
The HP page wouldn't open? I just tried it on my computer and it opened fine....perhaps you could try using a different computer/browser. Here's a more direct link to the HP DST fix for the rx3115....perhaps it will help:
HP DST Fix for the rx3115 (sp34881)
HP DST Fix Documentation (sp34881)
Reply to this
When I extract and copy the files over to the PDA it still fails to install
Toshiba e330
Microsoft PocketPC Version 3.0.11171
What am I missing?
Reply to this
Which file are you attempting to install? What happens when you install it? Do you receive any kind of message? Are you using an .exe file or a .cab file?
Reply to this
This update to Windows Mobile 6 Classic on my iPAQ 111 did NOT fix the DST problem. What do I do now? I have never seen the message that is shown above on this page about "the clock has been updated to daylight savings time..."
Reply to this
These DST updates are needed for older pocket pcs that were released well before these DST changes were even conceived, but since the IPAQ 111 is one of HP's newest pocket pcs, I'm surprised to hear that you need to update your pocket pc to accommodate these changes.
Nonetheless, if you installed the update to your IPAQ 111, did you then change the time zone on the pocket pc to a different time zone and then change it back to your time zone?
Reply to this
I was able to get to that page, it was after I clicked on “download” that it said the page didn’t exist. I sync my iPaq at work, so the IT support person here has tried this as well and it isn’t working for her either…I am stumped!
Reply to this
I think you'll need to try to downloadfrom a computer at a different place (like from you home computer).
Reply to this
I started with the WMDST2008-1.cab file which would not run on the e330, error was no application associated.
Based on a MS knowledge base article I then extracted the 4 files _setup.xml, 000setup.999, settim~1.001 and WMDST2~1.000 and transferred them to the e330. the .xml opens an web browser and basically gives a listing of the file, the remaining files error with no application associated.
Reply to this
Have you ever been able to install any other .CAB files to your pocket pc? Did you try installing the DST patch from the .msi file (posted on the same page as the .CAB file).
Reply to this
I do not believe I have installed any .CAB files on this pocket pc.
I have installed the .MSI file on the desk PC that I synchronize my calendar, contacts, and notes with into Outlook 2007.
I copied the .MSI file to the e330 and ended up with “No application associated with Setup.msi” error
Reply to this
You should not copy the .msi file to your pocket pc. Select the file on your computer and then an installation wizard will open up and install it to your pocket pc.
See this article for more information about installing software to pocket pcs:
I bought a piece of software, now what do I do?
Reply to this
I saved the .MSI to the desk PC, then ran it from there. the Install wizard started and ran, no options other than to accept the license. I let it install to the default directory C:\program files\Windows Mobile Feb. 2008 DST Updates\
Thsi is while the e330 is connected to the desk PC by the cradle and ActiveSync is running.
I have sync'd up the e330 several time but still do not have the correct DST.
Reply to this
Roland,
I looked at your situation a bit closer. Your pocket pc is running Windows Mobile 2002. The 2008 DST update is not compatible with this old operating system. In fact, there is no formal DST update for Windows Mobile 2002 (or earlier) devices. Some users have had success installing the DST update that was provided for the Windows Mobile 2003 update. Try downloading the Windows Mobile 2003 DST fix .CAB file and see if you can get it installed on your Pocket PC.
BTW, upon I just now tried to install the Windows Mobile Feb 2008 DST Update MSI file, and it seems that this MSI file is nothing more than a zip file that includes the Windows Feb 2008 DST CAB file and a license agreement. When I "installed" it on my computer nothing happened in regards to installing it to my Pocket PC through ActiveSync; selecting the .MSI file simply unzipped the .CAB file and the license agreement into a folder on my computer. Microsoft must have forgotten to include the installation scripts.
Reply to this
No such luck.
Error: The file "\temp\WM2K23DST_signed.cab" is not a valid Windows CE setup files.
Reply to this
Roland - I've about run out of ideas. Here's a link where you can download another file (I'm not sure that it will work, but it references windows mobile 2002, so might be worth a shot):
http://www.microsoft.com/windowsmobile/downloads/eula_daylightsavings_1033.mspx
And here's another link to a different file that someone created that may work:
http://www.edgeblog.net/downloads/DST2007WM5.cab
If you can't install either of these files to your pocket pc then I'm afraid you are out of luck. I'm sorry I could not help you resolve this issue.
Reply to this
The first links back to Windows Mobile 2003 DST fix .CAB file.
The second did work.
Thank you for your effort in finding these and sharing you efforts.
Reply to this
Oh Roland!
I am so glad to hear you got this worked out. Glad to know which file finally did the job. Hopefully your experience will benefit the next user that comes along looking for a fix.
Reply to this