Cheats and Walkthroughs
Generally, Time heals all wounds, but not computer bugs. The recent PlayStation 3 meltdown may be an exception to this rule, though. Sony has confirmed that the PS3 glitch relates to the internal clock of systems that were created before the release of the PlayStation Slim, and that the problem causes the PlayStation clock to reset to January 1, 2000. The error was first reported around midnight, last night, Greenwich Mean Time. So it looks like the date switching to March 1st, 2010 may have caused the PlayStation freak-outs.
It is a troublesome date. Not only is your rent due, it's also the "leap year" date. Every four years, it's February 29 and not March 1. This year isn't a leap year, and we don't have official word from Sony on this, but I wouldn't be surprised if the leap year date caused the problem anyway.
Perhaps, a theory goes, March 2, 2010 will bring redemption. Sony say, on its official blog, "We hope to resolve this problem within the next 24 hours" which could be taken to mean, "we're going to try to fix it, but if we can't, it'll be working tomorrow."
It's not unprecedented problem, and the solution of waiting a day has been tried before. Back in 2008, The Microsoft Zune had a similarly problem. The music player stopped working on January 31, only to come back online on the 1st. A glitch related to 2008's leap year was the culprit. At the time, Microsoft issued a statement saying "The issue should be resolved over the next 24 hours as the time change moves to Jan. 1, 2009," although, to be fair, Sony has not made that same statement. Check back at 4PM. We're going to know then whether the passage of Time fixes the glitch.
In any case, Sony is going to have a rough time until this problem is taken care of -- Battlefield: Bad Company 2 and MLB 10: The Show are going to be released tomorrow, and it'll be a crying shame if the PlayStation 3 isn't fixed by then.