Windows Mobile users in New Zealand, Australia and some other countries have reported appointments are moved to and from the device with an one hour difference from the actual time. This happens only during the week immediately before or after the start of Daylight Saving Time in those countries.
I have raised this issue with Microsoft before because we had reports of this in our Geekzone forums.
We read some horror stories here, such as the CEO (or Chairman?) of a large telco who missed a flight because the Pocket PC appointment was one hour off. And this is just one example.
The answer was always something along the lines of "the timezone information on a Pocket PC is stored/managed on a dll file and an update would require the deployment of a new signed dll to millions of devices, and OEMs would need to update older devices, etc, etc".
In short the answer was "sorry, this is a fault, but there's no immediate fix". The only fix for this was to (inappropriately) change the timezone on the device, which would cause more problems if you actually created a new appointment directly on the device during that week.
Interestingly enough things have changed. You see, the Energy Policy Act 2005 is going to be inforced and according to the Wikipedia entry:
The bill amends the Uniform Time Act of 1966 by changing the start and end dates of daylight saving time starting in 2007. Clocks will be set ahead one hour on the second Sunday of March instead of the current first Sunday of April. Clocks will be set back one hour on the first Sunday in November, rather than the last Sunday of October. This will affect accuracy of electronic clocks that had pre-programmed dates for adjusting to daylight saving time. The date for the end of daylight saving time has the effect of increasing evening light on Halloween (October 31).
Now it seems the DST problem will affect the U.S. consumers and organisations as well...
And guess what? Microsoft came out with a registry fix for this, applicable to old Windows Mobile devices from Windows Mobile 2003 and newer.
But isn't this against to what they kept telling us before?
So, go ahead with your conspiracy theories, but to be safe, you need to work with these Knowledge Base articles (only if applicable).
First make sure you check the Knowledge Base article 928388 2007 time zone update for Microsoft Windows operating systems:
The update that this article describes changes the time zone data to account for the United States DST change. This time zone update will also include changes for other related DST changes, time zone behavior, and settings. Some of these changes will occur in 2007, and some have occurred since these versions of Windows were originally released. The update that this article describes also includes some changes that have previously been released as individual hotfixes. An example of this is the Sri Lanka change in time zone offset. This update will also include some changes that have been individually documented in Microsoft Knowledge Base articles
Next, read the Knowledge Base article 923953 How to configure daylight saving time for the United States and Canada in 2007 and in subsequent years on Windows Mobile-based devices. Note that it mentions some .inf files converted to .cab files to be loaded on your device. Why is Microsoft not releasing the files? It only makes things harder for end users. But fear nothing, visit pdaphonehome and dowload a installer from there.
By the way, good luck trying to load something that changes your registry on a Smartphone. Pocket PC phone users are lucky though.
Also note this impacts Microsoft Exchange Server 2003 SP2. According to Microsoft a patch will be available in January 2007 for these servers:
A test version of this update is now available to businesses that wish to test the impact of the upcoming time zone changes. A copy of the update can be downloaded from the Microsoft Download Center. For more information please refer to Knowledge Base article 926666.
The test version of this update is only intended for use in testing environments. A final version of this update for production deployment will be released in January 2007 through Microsoft Customer Support Services (CSS), Microsoft Download Center, and Microsoft Update.
For a wealthy of information on this topic, visit Microsoft's page Preparing for daylight saving time changes in 2007.
In that article I explained what new features are coming to Microsoft Exchange Server 2007, and how those features will interact with Windows Mobile devices, and other devices running the licensed Exchange ActiveSync client platform.
If you want even more information on this, you should head to Paul Mah's Technology At Play, and read the post Examining Exchange 2007: The Future of Direct Push.
Now that Microsoft have finally announced that Exchange 2007 is being slated for release at the end of November 2006, it is a good time as any for us to perform a detailed appraisal of the Direct Push-related components in this new version of Microsoft Exchange.
Perhaps you have already heard or even read-up on it. But in case you are not aware yet, Exchange 2007 is a radically different beast altogether from Exchange 2003. Rather than being a purely evolutionary upgrade, this latest version of Exchange is set to bring several features never before found in the e-mail server scene – such as built-in voice (Think in terms of voice PABX) and fax capabilities, onto the playing field.
MagicButton is a very small task switcher, and free, while MemMaid is a great memory management software - perfect for cleaning up the Pocket Internet Explorer cache after a soft reset, or remove some unwanted stuff from your Pocket PC.
I've just noticed DinarSoft has updated their logo and webite. Worth a visit to check their range of software - TapText is a really cool tool to automate the process of entering text and strings into your e-mails and documents and HandySwitcher is an interesting task manager with lots more functions than MagicButton.
After the event I had a meeting with Vodafone New Zealand and Palm. Dion Knill (Vodafone, Business Terminals) and Geoff Anson (Palm, Sales Director) gave me details on some of the work the companies are doing together. All will be revealed soon, but until then, here are some interesting facts I gathered from the meeting:
- Vodafone New Zealand is bringing 16 new "Handheld Business Devices" (HBD) soon, 8 of these being Windows Mobile devices, the rest are Symbian devices. All come with Microsoft Exchange ActiveSync capabilities.
- Palm commisioned a study which showed the uptake of some common activities, before and after users moved to a Treo smartphone: 93% of users browse the Internet on the handheld device, against only 20% who used to do it with their previous device. SMS usage also increased from 52% to 87% and e-mail utilisation grew from 15% to 93%.
- Vodafone New Zealand is offering an one hour "Mobile Mentor" session when companies purchase any of the HBD with a business plan. Dion told me this helped improve the understanding on how these devices work, why use them and how to do it better.
- Vodafone New Zealand is running a "try and buy" programme for qualified customers. You use one of the HBD for a few weeks and then decide to keep it or return it. Apparently the "keep" rates are as high as 85%. How do you know if you are a "qualified" customer? Your account manager will let you know.
There you go. Some interesting mobility facts. More on this later.
I just got a press release from Palm annoucing the launch of its Palm Treo 700wx Windows Mobile device in Canada, through Bell Canada. This is just a few hours before our local announcement.
The Treo 700wx provides the same great world-class Treo experience and ease of use that customers expect, as well as the following key features:
Additional Treo 700wx Features and Benefits
Let's see when this device is available here in New Zealand. I didn't get any other information from Palm, Telecom or Microsoft about this device, so I am still waiting for some data to work with.
The service went down for a while due to traffic, but it's back, and the guys at instinct.co.nz tell me they will be moving it to a bigger server to support the traffic.
I am pretty sure this will be the first Palm Treo CDMA EVDO being released outside the U.S. where it is available now as Treo 700w (Verizon Wireless) and Pam Treo 700wx (Sprint).
Knowing of the close relationship between Telecom New Zealand and Sprint, I'd guess the version being released here is either the Palm Treo 700wx (pictured below) or a similar one.
- receive a hands on demonstration of the first Windows Treo in New Zealand and see what it has to offer users
- understand how Palm has further developed the Palm user experience on Windows mobile operating system and combined with ready access to Microsoft’s world-class email solutions
- find out how Palm’s latest Treo lets users take advantage of Telecom’s high speed, EV-DO Mobile Broadband network to get them faster access to email, desktop and server information.
Note that this will be an introduction to the media. There's no word yet of availability dates. But one thing is for sure: people have been reporting in the Geekzone forums that Telecom New Zealand has pulled out the webpages for the Palm Treo 650...
But down in its press release, Telstra also promised a device from Palm joining the network next month. I know Vodafone New Zealand is launching the Treo 750v 1st November. I wonder if Vodafone Australia will be behind Telstra on this one?
It looks great on a Windows Mobile Pocket PC:
This year we have not only seen a whole variety of Windows Mobile 5 devices hit the market, we have also seen the first UMPC devices being released. With the launch of Vista just around the corner (are you “ready for a new day“?) we will see operating system convergence such that Tablet PCs, laptops, UMPCs and desktop machines will all be running the same OS.
With coming versions of Windows Mobile we are also likely to see a further convergence between the smartphone and pocketPC operating systems. In this show Jeff Arnett joins me to talk about how we can optimise our development process for building applications that work across different mobile platforms.