Dragons Hobbies Forum
Gaming => Video Games => Topic started by: Dragon on March 02, 2010, 11:01:42
-
My brother called me up yesterday saying that he couldn't get onto Modern Warfare 2. Apparently there was a problem that affected many older PS3 systems. A "24-hour bug" that seems to have been brought to light because of a Leap Year problem came to light yesterday because it wasn't a leap year. Sony advised that PS3 owners leave their game systems off for the day. Some interesting comments came up on PCWorld about this.
sad that such a "new", sophisticated piece of [hard/soft/firm]ware still has y2k bugs. what makes this funnier and more embarrassing for the developers is that it's not even a leap year.
I wish this year was a leap year, we wouldn't be having this issue if it was...
Bios clock thinks a leap year is every two years, front end knows that it's every four. Front end gets a wrong date and blows up reverting to zero or in bios time 0 = 1/1/2000 @ 12:00:00am. This causes everything in the system with a time stamp after that to go corrupt and no connection to network due to invalid time issues.
Just going to wait another 2 and a half hours until GMT hits 00:00 to flip to March second.
Note: bios time chip was selected by Sony, not programmed by Sony.
-
glad I didn't log on yesterday,
It's fixed now, or so they say.
-
Ditto! Busy season has helped me!! Woo Hoo!@