Do you want to play a boardgame? Or do some coding? R/C cars? Lego? Choose your hobby!
Quote from: JackStrawsad 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.Quote from: berg0011I 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.
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.