Fix/Workaround for 2016 Issue - Page 28

XwalkerX · #**271** (**permalink**) 01-10-2010, 08:52 PM

that .cab worked for my tp2.

thanks again!!!!

neudof · #**272** (**permalink**) 01-10-2010, 09:42 PM

Quote:

Originally Posted by psycho_maniac

WTF??? you have to pay 60 damn dollars to get this fix? thats BS its a problem with there OS we bought phones that are supposed to be in awesome working no 2016 bug condition and now we have to pay 60 dollars? THATS BULL!

Thats why I think everyone should call the same supervisor I spoke to and ask the same question! Tell them to acknowledge the issue/resolution on their weebsite!!

jpetrone · #**273** (**permalink**) 01-10-2010, 10:54 PM

Has anyone paid the $60?

Hell, this pisses me off but I would pay the $60 if it fixes it and gives me the time stamp from when the message is sent and not when my phone receives it.

trailmix · #**274** (**permalink**) 01-11-2010, 01:00 AM

Quote:

Originally Posted by jpetrone

Has anyone paid the $60?

Hell, this pisses me off but I would pay the $60 if it fixes it and gives me the time stamp from when the message is sent and not when my phone receives it.

I'm guessing the $60 is just the usual Microsoft pay-per-incident support fee, not the cost to obtain the CAB

almatic · #**275** (**permalink**) 01-11-2010, 02:45 AM

Quote:

Originally Posted by neudof

I called Microsoft today and spoke to Peter (emp#10916) a customer service supervisor. He told me that this issue has been resolved by Microsoft, but that they cannot connect me to a Windows Mobile tech to get the fix without paying 60$.

Everyone call Microsoft and ask to speak to Peter, maybe if enough people call they will give us the resolution!!

EDIT:
I spoke to Sprint and they of course will not confirm that a fix has been identified, or when the fix will be available....

What number did you call?

mjosephc · #**276** (**permalink**) 01-11-2010, 03:21 AM

Quote:

Originally Posted by a3rdeye

I had the same problem so I tried the following and it worked perfectly.

Copied XML from step one and opened it in NOTEPAD
Used Find/Replace to replace /2016 with /2010 and saved.
Then do the same as in Ziggy's instructions. I had over 1000 sms messages so it took a while but worked perfectly.

Just for info Ziggy's cab is all over the net and I'm glad that the forums and sites are giving him credit

This worked for me as well, so thanks.

Also, just as an FYI...I may be the only person who didn't think of this, but I figured I'd put it out there just in case. When you go to back up your texts for the purpose of correcting the dates, make sure that you back up ALL the messages - including your Sent messages, even though we know the dates are correct on the Sent messages. Reason being, when you tell PPCPimBackup to "Delete all existing messages from the Database", it actually does mean "ALL". I (stupidly) thought that if I just backed up my Inbox (and not Sent messages) that it would only delete/restore the Inbox. Turns out that while all of my incoming texts now have the corrected 2010 dates, I no longer have any of my Sent messages.

At the end of the day, it is what it is and I'll live.

But just in case this hadn't crossed your mind before backing up and correcting your text message dates, I hope it helps!

neudof · #**277** (**permalink**) 01-11-2010, 08:06 AM

Quote:

Originally Posted by almatic

What number did you call?

Good Point.,,,
Hard for you to call if I don't give you the number!
1-800-936-5700

Remember to ask for Peter (emp#10916) Customer Service Supervisor... Or maybe his supervisor!

He confirmed that Microsoft has a fix, but that they cannot connect me to a Windows Mobile tech to get the fix without paying 60$.

Everyone call Microsoft and ask to speak to Peter, maybe if enough people call they will give us the resolution!!

scarydok · #**278** (**permalink**) 01-11-2010, 01:42 PM

Ziggy,

Not sure if you noticed, but over on the sprint forums, all of your posts have been completely removed, yet your fix remains with the fake Ziggy still taking credit for it.

And I know you don't ask for donations, but I hope that you are recognized for your workaround. Seriously, MS has known about this for how long now and what have they done? Nothing.

I certainly hope that everyone will realize that you are responsible for helping us all out, and will publicly humiliate the fake Ziggy all over the news.

Thank you again.

**ziggy471** · #**279** (**permalink**) 01-11-2010, 03:08 PM

Quote:

Originally Posted by neudof

Good Point.,,,
Hard for you to call if I don't give you the number!
1-800-936-5700

Remember to ask for Peter (emp#10916) Customer Service Supervisor... Or maybe his supervisor!

He confirmed that Microsoft has a fix, but that they cannot connect me to a Windows Mobile tech to get the fix without paying 60$.

Everyone call Microsoft and ask to speak to Peter, maybe if enough people call they will give us the resolution!!

I just tried calling, and no one seemed to know what to do with the name Peter or his employee number. They even transfered me to the operator, but that is not an extension either. Oh well, I was hoping to use one of my support incidents to take care of this once and for all, guess that isn't going to work.

Quote:

Originally Posted by scarydok

Ziggy,

Not sure if you noticed, but over on the sprint forums, all of your posts have been completely removed, yet your fix remains with the fake Ziggy still taking credit for it.

And I know you don't ask for donations, but I hope that you are recognized for your workaround. Seriously, MS has known about this for how long now and what have they done? Nothing.

I certainly hope that everyone will realize that you are responsible for helping us all out, and will publicly humiliate the fake Ziggy all over the news.

Thank you again.

Yeah, I noticed that too. I got a few emails this morning saying that the content was not approved and removed, guess they think he's me. As for his fix, if you open it with WinRar, 7-Zip etc, you'll notice that it's the same as mine, with the same files inside and the same date/time on the files. I originally created the CAB 2249EST 1 Jan 2010, posted it to post #1 around 2250 or so, then posted later on in the thread at 2252 that I'd just uploaded a CAB file. It's interesting that he posts the date/time of the file as 25 Dec, but looking inside it's different, guess he doesn't realize what's in a CAB file after all.

I really don't care that he posted my fix, it's all over the web to include Chinese and Japanese sites, what I care about is not only has he claimed it is his, not a big deal, but he also stole my name, REALLY BIG DEAL. If you also read through his post, he claims to have Copyrighted the fix, which, even though I'm not a lawyer, I don't think he can copyright a registry setting from other companies already copyrighted material. Lastly, the second key I included, was a just in case, since I had just found it that day while attempting to fix the SMS issue for Sprint Users. Oh well, let him have his fun over there, I'll still support everyone over here as much as I can.

And for those of you that want to know, and of course now those that really don't care, I got the nickname of Ziggy in Basic Training back in '92, because that's supposedly what I look like without hair. He claimed to have gotten his from his girlfriends dog of the same name. I think mine has better roots, no pun intented, ok maybe a little. lol

Z

neudof · #**280** (**permalink**) 01-11-2010, 10:00 PM

Quote:

Originally Posted by ziggy471

I just tried calling, and no one seemed to know what to do with the name Peter or his employee number. They even transfered me to the operator, but that is not an extension either. Oh well, I was hoping to use one of my support incidents to take care of this once and for all, guess that isn't going to work.

Somehow this does not suprize me! No wonder Windows Mobile is losing to Android...

When will that CDMA port be complete........