when a fix is not really a fix…but you have to use it anyway
regulars to the funcave might remember the recent post on daylight savings time.
as in, how the changes to it are set to put a hurtin’ on all of us in north america this year.
well, one thing i didn’t mention was how atrociously atrocious the fix for windows mobile devices is/was.
as in, the dst codefix is out there & readily available…
but guess what?
you get to build your own cab file to deploy it. wheeee!
luckily for us, someone else has already prepped that code into an actually executable form.
obviously…
use it at your own peril! if you mangle your device…don’t come crying to me.
but, i wouldn’t hold your breath for an official fix showing up on devices any time soon, let alone before the new dst comes along and…well, kicks your butt!
heck, i still see brand-new devices coming out of the box that don’t even have an msfp-capable build of windows mobile 5.0 on them.
logistical issues of the typical approval process that a new rom update has to go through for just carriers/operators alone means it’s very unlikely we’ll get one before march.
|| posted by chris under mobility, thumbs down || comments (0) || ||
