Dst 2007

CodeBubba · 12-27-06, 03:48 PM

If anyone from Dell is monitoring Aximsite - we have a question.

Will WM2003 be patched soon to accomodate the new Daylight Savings Time that has gone into effect for 2007? If so, when can we expect this patch? It is my understanding that a registry hack is floating around out there - however I and others here would prefer not go through that. If said patch is available could you please provide it on the Dell website? As of right now I can find no mention of this on dell.com.

By the way - a reload of the ROM is not what I would consider an adequate solution to this problem. DST should not be a hard-coded algorithm in the O/S code. I'm stable with A02 and really don't want to reload all 3 dozen of my applications and re-tweak this thing for a minor fix like this.

Thanks-in-advance.

-CB :)

griffin2k3 · 12-28-06, 01:11 PM

I emailed Dell's support via their website and I didn't hear anything from them. I thought it would help by providing the service tag, but didn't work. I start to wonder if it's their policy not to provide support to those not in warranty anymore?

Kenster · 12-28-06, 06:50 PM

It's not a Dell issue, it's a Microsoft issue. Here is the link to the knowledgebase article that explains the fix:

http://support.microsoft.com/kb/923953

(found easily with http://www.google.com/search?hl=en&q...t+savings+time)

12-28-06, 07:07 PM

Do you think Microsoft will come out with a patch or will they expect everyone to be tech savy enough to edit/modify their own registry???

griffin2k3 · 12-29-06, 10:58 AM

Originally Posted by Kenster

It's not a Dell issue, it's a Microsoft issue. Here is the link to the knowledgebase article that explains the fix:

http://support.microsoft.com/kb/923953

(found easily with http://www.google.com/search?hl=en&q...t+savings+time)

Although the OS was written by Microsoft, it's Dell's responsibility to publish the patch. If we update the registry using the unofficial patch, Dell could easily say "you're screwed because of that patch, goodbye.".

And if it's not a Dell issue, we should be free to upgrade from 2003SE to any Pocket PC OS at our own wish and shouldn't be restricted by Dell.

CodeBubba · 12-29-06, 12:20 PM

Originally Posted by Kenster

It's not a Dell issue, it's a Microsoft issue. Here is the link to the knowledgebase article that explains the fix:

http://support.microsoft.com/kb/923953

(found easily with http://www.google.com/search?hl=en&q...+savings+time)

Yeah, I was aware of that KB article - just wondered if a CAB had been built to deal with this yet.

I just built one with CABWIZ myself using this file - I'll deploy it to my machine and see if it works. If it does I'll make it available for everybody.

-CB

CodeBubba · 12-29-06, 12:52 PM

Good news folks ... the patch that M$ released that Kenster mentioned works perfectly.

I have taken the .INF file detailed and created the appropriate CAB file. I placed this on my Axim and loaded it. The patch loaded without incident.

I then set the date/time to 3/11/07 @ 01:59. Upon switch to 02:00 the device correctly sensed that DST was now in-effect and rolled the clock forward to 3am with appropriate message box.

If anyone would like me to mail this CAB file for your use just drop me a PM with your e-mail address and I'll send it to you. This fix is for WM2003SE devices.

I'll also try to place the file on my website for download and provide the link to it when I accomplish that.

-CB :)

DoDoubleGeo · 12-29-06, 01:00 PM

Dogfood already posted a CAB file for the fix in this thread

jelindley · 12-31-06, 12:53 AM

That's a real good question. Microsoft has info on changing the registry, but that's not really a good option. They also say to get updates from our OEMs. In other words, from Dell.

mirskym · 12-31-06, 03:21 PM

Have a look at this

It makes some mods in the registry based on info provided by Microsoft.

Michael

griffin2k3 · 01-02-07, 12:37 PM

Thanks CodeBubba... just want to make sure the patch works on all 2003SE, regardless whether it means X50 or X30!

johnalexander · 01-10-07, 03:48 PM

In regards to the registry info posted by Microsoft, they say very specifically:

"OEM device manufacturers can use the following listing to create an .inf file that is contained in a .cab file. The .cab file can then be installed in Windows Mobile-based devices."

I did not read this as "tech-savvy users can use this information to edit their own registry."

Unfortunately, Dell has left us out to dry once more. They could compile this .CAB file in a relatively short period of time and make their customers happy, but they don't. Great support, guys.

Many thanks to the folks here in this forum who have made the .CABs themselves and posted. I will be trying one of them (there seem to be a couple). I wonder how many old Dell Axim's will be auctioned off on eBay on March 12 when they are perceived as useless by folks who didn't think to search Aximsite?

Any speculation on what happens on March 12 if your PC is patched (there are patches for Windows client, Windows server, Outlook, AND Exchange -- all 4 of which must be patched). I imagine if all of these are patched and your Axim is not, you may end up with duplicate appointments.

From the MS site - if you do not patch Outlook properly, your events will shift by an hour. Worse yet, your "all day" appointments will shift by a day and span 2 days. This is because "all day" appointments are actually midnight-to-midnight. When it shifts, it ends up being 11pm-11pm (spanning two days), but still being marked as an all-day event, so it looks like a 2-day event. My guess is an unpatched Axim would experience similar characteristics (particularly when syncing with a properly-patched PC), but I could be off base. Anyone tested yet?

Thanks again to those of you who posted fixes for this. I look forward to trying one of them. I have WM2003 (not SE) -- is the .CAB the same?

AKAJohnDoe · 01-10-07, 04:03 PM

It is clearly Dell's responsibility to package and distribute this to all registered devices, WM2003, WM2003SE, and WM5. A responsibility that Dell has apparently abdicated.

There is a checkbox in ActiveSync to "Synchronize mobile device clock upon connection". Works for me.

**Rishad** · 01-11-07, 11:24 PM

Originally Posted by DoDoubleGeo

Dogfood already posted a CAB file for the fix in this thread

Seems like that CAB has some missing info, made a post on that thread.

CodeBubba · 01-12-07, 09:44 AM

Originally Posted by griffin2k3

Thanks CodeBubba... just want to make sure the patch works on all 2003SE, regardless whether it means X50 or X30!

It should - it's not a device-specific patch. If you read the registry entries you can see clearly that it's a software fix.

-CB :)