here is the answer's to what had happened. and why:
Q. What caused this? Why?
A. The incorrect internal calendar date and time conflicting with the lack of such date built into the XMB™ (XrossMediaBar).
Q. Was this a firmware or hardware issue?
A. Both.
Q. Why were only older fat PS3s affected and not PS3 Slims?
A. Newer hardware with different firmware.
Q. If the issue was indeed related to the system time, why did it not also affect PS3 Slim?
A. See above.
Q. Was something changed in the system timer when they converted hardware from fat to Slim?
A. Yes. Many hardware components were changed or updated.
Q. If that was the case, did they know about this potential bug beforehand (since they "fixed" it for the Slim)?
A. No. The problem simply got overlooked.
Q. Or was it just blind coincidence that other hardware random changes made to the Slim allowed it to avoid this calamity?
A. Was just a simple error that got overlooked.
Q. Why was it able to "fix" itself with the passage of time?
A. When the internal clock hit 12:00:00 GMT February 29th, 2010, it conflicted with the XMB™ (XrossMediaBar) which does not see it as a valid date. After 24 hours, the internal clocked rolled over to March 1st, 2010, a valid date thus returning the PS3™ system back to normal operating functionality.
I AM BOLO
100% lover "nothing else matter's" after that...
ps:
Proud psOne/2/3/p owner. I survived Aplcalyps3 and all I got was this lousy Signature.
