They just announced that its back up now. Seems to be kinda like the Zune issue (wait for 24 hours it'll fix itself. PlayStation Network Service Restored – PlayStation.Blog I did have to reset my clock (it was stuck on 2/28) and I updated it through the internet (selected that).
I read the news, and didn't dare to turn on. But I did read that it was probably caused by the clock which will be back to normal on 2/3/2010, and it was.
Wonder if they plan on patching this issue or they just will let it go as it is "harmless" so we have something to look forward to in 2014.
I'm not sure every phat was affected, this list has been circulating, but it is not confirmed officially. CECHA0x – affected CECHC0x – affected CECHE0x – affected CECHG0x – affected CECHH0x – affected CECHK0x – affected CECHL0x – not affected CECHP0x – not affected
It's just because the fat PS3 does not know that this year is not a leap year. There's no Feb. 29 this year.
Then what about 2009? Didn't happen. What I'm trying to say is, the chip knows when there's a leap year in 2008, but 2010 is not a leap year, so it is most probably some other bug. If it can recognise 2008 as a leap year, which means it is not going to skip every leap year.
2008 is a leap year so it won't be affected. Edit : Probably someone programmed it to avoid odd years? But whatever it is, it's related to the February 29 date.
I don't think you guys understood what I really meant. PS3 is able to identify both leap and non-leap years properly prior to 2010 since 2006. It is only affecting 2010.
I forgot to mention all ps3 phat >_<"...slim of coz was not even affected..i actually though it was sony's evil scheme to have customer to switch to the slim models
well thats what i though off (waited 2 days before i switched on my ps3 Phat model ) i was thinking, what if they don't solve it? then all user must change to slim version
