Mobility Site - View Single Post

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?

01-10-07, 03:48 PM	#12 (permalink)
johnalexander Aximsite Rookie Join Date: Nov 2003 Posts: 22 Thanked 0 Times in 0 Posts	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?