Alright so heres the deal... Thousands of the 'old-style' models are currently down with this error. >:(
Slims arent affected apparently, but for some daft reason the 40, 60 and 80gb PS3 models are rejecting the fact that this is a leapyear and are showing either the YLOD (like mine yesterday) and/or coming up with the error 8001050F. :^_^':
If you get this problem like me then I believe it'll take a few days for sony to fix it... Hopefully they'll just upgrade us all to slims for free ;)
Any thoughts?
That's odd I just used my phat ps3 Friday and I didn't get any error. I haven't used it since as I only use it to watch movies on because it has like a 250 GB hard drive in it, but I'll test this out after school and see if I get any errors.
(I use my Slim when playing games and the phat for movies)
Yup mine 'overheated' and yellow lighted after about 10 minutes of gameplay yesterday MORNING, my friend was on his ALL DAY with no error until this morning.
BUT I've had mine on for half an hour easy and no yellow light... I dont know wether to assume that it was the leapyear thing or wether its still buggered :)
But yes mines also spitting out the error, even when I try to game ¬_¬
2010 isn't a leap year... O.o
Quote from: Elite Four Aqua on March 01, 2010, 02:46:38 pm
2010 isn't a leap year... O.o
Jup. Leap years skip decades, centuries and milleniums. Basically everything ending with a 0, as far as I know.
leap years are multiples of 4. meaning 2008 was the last one, and 2012 is the next one.
which also means that 2020 would be a leap year (just like 2000). just to clear that up.
Yes but the PS3 THINKS its a leap year, theres a glitch in the programming that doesnt handle leap years correctly. Hence why it buggers up when it tries to connect, it has the wrong date, and kills itself in its humiliation :D
Quote from: Shiny Magikarp on March 01, 2010, 03:42:41 pm
Quote from: Elite Four Aqua on March 01, 2010, 02:46:38 pm
2010 isn't a leap year... O.o
Jup. Leap years skip decades, centuries and milleniums. Basically everything ending with a 0, as far as I know.
Quote from: Arceus on March 01, 2010, 03:52:38 pm
which also means that 2020 would be a leap year (just like 2000). just to clear that up.
Meh, then school teached me something wrong again. Those bastards.
(No, really, a math teacher told us this in class.)
Leap years are skipped every 4th century... I think
Edit:
Or was it every 4th millennium...
skip leap years in years ending in 00 except when they can be evenly divided by 400
so 1600 and 2000 were leap years, but 1700, 1800, and 1900 were not.
Quote from: Arceus on March 01, 2010, 05:20:30 pm
so 1600 and 2000 were leap years, but 1700, 1800, and 1900 were not.
Actually, I'm fairly certain that's not entirely true. After all, 1700, 1800, and 1900 can be evenly divided by 4. (as can any multiple of 100.)
Ok so a technological thread is turning into a debate on leapyears XD
a year is 365.2425 days, so the leap century thing I said is correct.
if year % 400 == 0
then is_leap_year
else if year % 100 == 0
then not_leap_year
else if year % 4 == 0
then is_leap_year
else
not_leap_year
^ code to determine if its a leap year
Ah, I read a year was 365.25 days, not 365.2425 days, and because of that, I figured every 4 years is a leap year because of that. If you're right about the number of days, then yes, you would be correct about the leap century thing.
EDIT: According to Google, one year is 365.242199 days. That's... very precise. Just thought it would be worth mentioning.
Score. I wrote that particular code in university for C++... was amusing to see people struggle :D