-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Windows Mobile Bug Dates Messages from 2016
http://www.wired.com/gadgetlab/2010/01/windows-mobile-bug-dates-messages-from-2016/
Why does Windows Mobile think it is 2016?
http://www.daniweb.com/news/story250427.html
Windows Mobile phones suffer Y2K+10 bug
http://www.techradar.com/news/world-of-tech/windows-mobile-phones-suffer-y2k-10-bug-661062
Windows Mobile Phones Receive Greetings from the Future
http://www.blog.best-mobile-contracts.co.uk/2010/01/mobile-phone-industry-news/windows-mobile-phones-receive-greetings-from-the-future.html
The 2016 hit-list is getting longer
http://www.itwire.com/content/view/30322/53/
Microsoft responds to 2016 SMS bug; not just cell phones affected
,----[ Quote ]
| The saga of the Year 2016 text message bug
| continues. While there's not an official
| fix as of yet we, do have a workaround
| (download here). And we just received an
| official statement from a Microsoft
| spokesperson:
|
| âMicrosoft is aware of reports that
| phone messages received after 1/1/2010
| may be dated 2016. These reports have
| not yet resulted in widespread customer
| inquiries; however, we are working
| closely with our manufacturing and
| mobile operator partners to investigate
| the cause and correct the issue as
| appropriate.â
`----
http://www.wmexperts.com/microsoft-responds-2016-sms-bug-not-just-cell-phones-affected
Recent:
2016 bug hits Windows phones
,----[ Quote ]
| The date bug which is interfering with Aussie
| point of sale transactions has spread to some
| Windows mobile phones.
|
| The glitch means that text messages received
| since New Year's Eve will appear with a 2016
| date. Card scanners in thousands of Australian
| shops have also been hit, as we reported
| yesterday. Bank of Queensland systems, believing
| it was 2016, rejected most payment cards because
| they'd passed their expiry date.
`----
http://www.theregister.co.uk/2010/01/05/windows_mobe_bug/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAktKrjoACgkQU4xAY3RXLo4MCwCfYwU3JSsUl6PlB7I0yEkNRE/J
SiYAn3TwhHl99irMqdWrdJ3XxDsm23RR
=wzXy
-----END PGP SIGNATURE-----
|
|
