text messages from the future Y2KX issue - Page 33

PPCFreak · #**321** (**permalink**) 01-07-2010, 03:22 PM

Did this only affect SMS?
I got a MMS from my wifes phone (Blackberry on verizon) and it had the correct date (1/1/10).
I am on stock vzw wm6.1 rom.

Telek · #**322** (**permalink**) 01-07-2010, 05:12 PM

it's interesting that several different companies have had the same flaw around the world - there's a bank in Australia and a company in the UK as well. I'm betting that it's more likely to be an SMS gateway fix not a MS/HTC issue.

**psycho_maniac** · #**323** (**permalink**) 01-07-2010, 11:35 PM

Quote:

Originally Posted by PPCFreak

Did this only affect SMS?
I got a MMS from my wifes phone (Blackberry on verizon) and it had the correct date (1/1/10).
I am on stock vzw wm6.1 rom.

it does NOT effect mms. only sms

mikel81 · #**324** (**permalink**) 01-12-2010, 08:56 PM

Ok, so if this doesn't get fixed real soon I am jumping onto the droidwagon.
Seriously, someone needs to at least let us know there is an actual fix in the works. I will not be running ziggy's cab. I appreciate the effort he put in but I want my phone to run as it was intended. I bet this is the final push that will take me away from windows mobile. Sad...

I had just been setting my phone's date to 2016. (The days of the week line up until 2-29)
Unfortunately, that gives certificate errors in Opera mini and I have to change it back to browse. Grrrr.... Waiting until tax time and will be getting a new phone, what will it be?

Telek · #**325** (**permalink**) 01-12-2010, 09:06 PM

There was an article posted on CNET about Microsoft admitting that this was a problem of theirs, however the article also said that it was limited to the US Sprint Network and a "small subset" of users.

Here's another article:

http://www.wmexperts.com/microsoft-r...hones-affected

So they've acknowledged the problem and are working on it. So much for a quick and quiet fix...

If you're having problems why not just use the workaround? At least it takes care of it for now.

**psycho_maniac** · #**326** (**permalink**) 01-12-2010, 09:59 PM

Quote:

Originally Posted by Telek

There was an article posted on CNET about Microsoft admitting that this was a problem of theirs, however the article also said that it was limited to the US Sprint Network and a "small subset" of users.

Here's another article:

http://www.wmexperts.com/microsoft-r...hones-affected

So they've acknowledged the problem and are working on it. So much for a quick and quiet fix...

If you're having problems why not just use the workaround? At least it takes care of it for now.

i agree. im using the workaround and its fine for now. il just deal with it until we can get the real fix.

marinemissez · #**327** (**permalink**) 01-12-2010, 10:05 PM

So if it's been recognized as a binary/HEX code error, why doesn't Microsoft/HTC just fix it and release the fix?? Hopefully not having to create a completely new ROM

Telek · #**328** (**permalink**) 01-12-2010, 10:09 PM

Quote:

Originally Posted by marinemissez

So if it's been recognized as a binary/HEX code error, why doesn't Microsoft/HTC just fix it and release the fix?? Hopefully not having to create a completely new ROM

We don't know that it's a binary/hex error -- that's just supposition.

Windows Mobile does hypothetically support hotfixes but I don't think that I have ever seen one. Considering how many users it's affecting and the difficulty (i.e. impossibility) for the majority of users to update the ROM I would think that they'd go with a hotfix if possible - but that may be exactly where the delay is coming from. The problem may have been easily identified and fixed but requires a ROM update.

**BlackDynamite** · #**329** (**permalink**) 01-12-2010, 10:13 PM

Quote:

Originally Posted by Telek

We don't know that it's a binary/hex error -- that's just supposition.

Windows Mobile does hypothetically support hotfixes but I don't think that I have ever seen one. Considering how many users it's affecting and the difficulty (i.e. impossibility) for the majority of users to update the ROM I would think that they'd go with a hotfix if possible - but that may be exactly where the delay is coming from. The problem may have been easily identified and fixed but requires a ROM update.

I don't see why it would be any different than when they issued the daylight savings time fix a few years ago when daylight savings time changed (as far as how they issue it)...

Telek · #**330** (**permalink**) 01-12-2010, 10:15 PM

Quote:

Originally Posted by SaltyDawg

I don't see why it would be any different than when they issued the daylight savings time fix a few years ago when daylight savings time changed (as far as how they issue it)...

That fix was likely a registry key change - this fix is likely a core DLL or system component binary file change.