Sony CEO: "Ted, this new system is brilliant, and you've fully tested and approved it?" Ted: "Yeah, it'll work like a dream!"
Fast forward to 01.03.2010
Sony CEO: "so Ted, the bloody thing breaks due to an error with leap years?" Ted: "Umn, yeah, we didn't think it was a problem, I mean how often do they come round? Once in a blue moon?" Sony CEO: "...Four years Ted, it's every four years..." Ted: "I'll clear my desk!"
Not to try to gloat or anything, but I assume if I was online yesterday, playing WKC (I wasn't online questing via GeoNet, but I was signed in to my PSN), and never got any errors, that I should be fine, right?
I looked at my friends list last night and was shocked that no one had signed on in several hours cause I have at least 5 people who picked up Heavy Rain and weren't playing it. Thought that was a bit odd.
Man I'm scared to turn mine on. And throw me on the list of people who want a software fix.
I sold my PS2 to help pay for the PS3 specifically because of the BC. Which at the time was being touted as an always thing.
Now I'm dreading the day my PS3 bites the dust. Dreading.
[edit]
Also, fuck. Throw me on the list of affected. I was wondering why I didn't pick up a single trophy in the second half of heavy rain, too. Not even the ending one.
I thought I was just doing really poorly.
Not to try to gloat or anything, but I assume if I was online yesterday, playing WKC (I wasn't online questing via GeoNet, but I was signed in to my PSN), and never got any errors, that I should be fine, right?
I looked at my friends list last night and was shocked that no one had signed on in several hours cause I have at least 5 people who picked up Heavy Rain and weren't playing it. Thought that was a bit odd.
I thought the problems didn't really start til today. Because if it started yesterday I should be fine, as I was online without problems, but I thought all PS3s with hardware BC were effected.
It isn't a hardware problem, as previously suggested. If I read that post right, they said the seconds wouldn't tick any more. Reset my clock by hand, and while I still can't hit up PSN, my clock is ticking just fine. FWIW
Ah, I see what you're saying. My clock hadn't technically tried to roll over to March 1st yet. I had some people on my facebook messaging about this issue almost 14 hours ago, so I just assumed the issue started yesterday night, which it did, for people several hours ahead of me.
Guess I'll check my serial number when I get home from work and see what's what. My PS3 is a little over a year old (picked it up for Christmas 2008) so I might be affected. Pity.
Not to try to gloat or anything, but I assume if I was online yesterday, playing WKC (I wasn't online questing via GeoNet, but I was signed in to my PSN), and never got any errors, that I should be fine, right?
I looked at my friends list last night and was shocked that no one had signed on in several hours cause I have at least 5 people who picked up Heavy Rain and weren't playing it. Thought that was a bit odd.
I thought the problems didn't really start til today. Because if it started yesterday I should be fine, as I was online without problems, but I thought all PS3s with hardware BC were effected.
It seems that the models before and including CECHK have problems and models CECHL and on are OK. More info would be helpful though because its not a sure thing, just from observation.
And Xaviar, what do you mean "the list of people who want a software fix?" There's a list of people who want to have to send their PS3 in, and lose features that they bought their PS3's early specifically to have?
In all seriousness, I understand that everyone is shitting their pants because PS3s are expensive, but I'd like us all to take some time before dropping our loads in our trousers. This is less than halfway into the day, and underwear isn't that cheap either. I'm not the biggest fan of how Sony manages things half the time, but staying calm is going to serve us all better than commencing the poo-cannon firing.
Not to try to gloat or anything, but I assume if I was online yesterday, playing WKC (I wasn't online questing via GeoNet, but I was signed in to my PSN), and never got any errors, that I should be fine, right?
I looked at my friends list last night and was shocked that no one had signed on in several hours cause I have at least 5 people who picked up Heavy Rain and weren't playing it. Thought that was a bit odd.
The error only kicked in at midnight last night, so you may still get the error. I hope not though!
Having a tough time imagining the actual hardware RTC in the PS3 deciding to shit the bed badly enough that it can't be corrected or masked with firmware.
Here's your fix in GhettoCode.
if instr(listofleapyears,str(year))
{
month = 2;
day = 29;
}
else
{
month = 3;
day = 1;
}
It's even simpler than that! No need to maintain a string list of leap years when the math is right there. I mean, the math is so simple it's tragic if this is the problem. Here's the dead-easy, posted-on-wikipedia fix to properly determine a leap year:
if (year modulo 4 is 0) and (year modulo 100 is not 0) or (year modulo 400 is 0)
then is_leap_year
else
not_leap_year
I've written stuff like this into my own code when determining leap years. Whoever wrote the code for the low-level clock better get their walkin' papers stat! :P
I know as of ~8PM Eastern Time last night my PS3 was affected. Even if it was based on GMT (-5 hours) it doesn't make sense to me how rolling over into March 1 was the problem. Of course playing with GMT/time zones always gives me headaches so I'm not doubting that I'm missing something obvious.
Owners of the original version Sony's flagship gaming console, the PS3 fat model, have been locked out of the Playstation Network because of a so-called 8001050F error.
This is not the first time that this error has arisen with the first instances reported as early as June 2007. It apparently relates to the fact that the inner timing system of the PS3 was reset to 1st January 2000 on the last day of February 2010.
Hex number 8001050F translates into 2147550479 in decimal, which is the number of seconds since the first second of the last millennium. The bug does not affect the newer Slim PS3 systems that have been sold since last year.
It is also unknown how many consoles have been hit by this issue but they are likely to be in the tens of millions. Sony has confirmed on their Twitter accounts that they will be releasing updates or firmware for the systems as soon as possible.
In the meantime though, users of the old PS3 consoles have been advised not to switch on or connect their gaming device to the PSN or they could not only lose their Trophy data but also be denied access to PS3 originals or Premium Themes.
Anyone else remember getting the error in 2007? I got my PS3 pretty much on day of release and cannot remember that? If it's happened before though, it does give hope that a fix is imminent.
*sigh* even with a working clock games still don't work. I'll probably get off my ass and dig out the old ratchet and see if non-trophy ps3 games work.
Xaviar on
0
Options
Waka LakaRiding the stuffed UnicornIf ya know what I mean.Registered Userregular
*sigh* even with a working clock games still don't work. I'll probably get off my ass and dig out the old ratchet and see if non-trophy ps3 games work.
It only affects games with "dynamic" trophies. I haven't verified but I think Fallout is affected because it tries to download trophy information before the game starts. For example, Uncharted 2 single player seems to run fine (better-half is playing as I type).
So yeah, I was all set to get back into some PS3ing since I was getting a bit burnt out on MW2 but this looks like a good reason to dig into the STEAM backlog a little more.
PeregrineFalcon on
Looking for a DX:HR OnLive code for my kid brother.
Can trade TF2 items or whatever else you're interested in. PM me.
Owners of the original version Sony's flagship gaming console, the PS3 fat model, have been locked out of the Playstation Network because of a so-called 8001050F error.
This is not the first time that this error has arisen with the first instances reported as early as June 2007. It apparently relates to the fact that the inner timing system of the PS3 was reset to 1st January 2000 on the last day of February 2010.
Hex number 8001050F translates into 2147550479 in decimal, which is the number of seconds since the first second of the last millennium. The bug does not affect the newer Slim PS3 systems that have been sold since last year.
It is also unknown how many consoles have been hit by this issue but they are likely to be in the tens of millions. Sony has confirmed on their Twitter accounts that they will be releasing updates or firmware for the systems as soon as possible.
In the meantime though, users of the old PS3 consoles have been advised not to switch on or connect their gaming device to the PSN or they could not only lose their Trophy data but also be denied access to PS3 originals or Premium Themes.
Anyone else remember getting the error in 2007? I got my PS3 pretty much on day of release and cannot remember that? If it's happened before though, it does give hope that a fix is imminent.
I don't remember even hearing about it happening then, but I guess I wasn't exactly looking either.
The part I bolded in the quote is complete rubbish, though. People are obviously going to be turning on their consoles, very few PS3 owners will have heard about it before experiencing the problem first hand.
Out of curiosity, why would this problem affect DLC data? I installed a Borderlands DLC pack yesterday and played a bit in a new area, but when I tried today (post the great PS3 apocalypse of '10 - insert rolling eyes smiley here) I was booted back to a non DLC area with a message that my character was in a DLC area, but that the DLC in question wasn't installed on my PS3.
Owners of the original version Sony's flagship gaming console, the PS3 fat model, have been locked out of the Playstation Network because of a so-called 8001050F error.
This is not the first time that this error has arisen with the first instances reported as early as June 2007. It apparently relates to the fact that the inner timing system of the PS3 was reset to 1st January 2000 on the last day of February 2010.
Hex number 8001050F translates into 2147550479 in decimal, which is the number of seconds since the first second of the last millennium. The bug does not affect the newer Slim PS3 systems that have been sold since last year.
It is also unknown how many consoles have been hit by this issue but they are likely to be in the tens of millions. Sony has confirmed on their Twitter accounts that they will be releasing updates or firmware for the systems as soon as possible.
In the meantime though, users of the old PS3 consoles have been advised not to switch on or connect their gaming device to the PSN or they could not only lose their Trophy data but also be denied access to PS3 originals or Premium Themes.
Anyone else remember getting the error in 2007? I got my PS3 pretty much on day of release and cannot remember that? If it's happened before though, it does give hope that a fix is imminent.
I don't remember even hearing about it happening then, but I guess I wasn't exactly looking either.
The part I bolded in the quote is complete rubbish, though. People are obviously going to be turning on their consoles, very few PS3 owners will have heard about it before experiencing the problem first hand.
Out of curiosity, why would this problem affect DLC data? I installed a Borderlands DLC pack yesterday and played a bit in a new area, but when I tried today (post the great PS3 apocalypse of '10 - insert rolling eyes smiley here) I was booted back to a non DLC area with a message that my character was in a DLC area, but that the DLC in question wasn't installed on my PS3.
Copyright checks. Bullshit basically. Sounds like the Borderlands DLC is as bad as that Oblivion stuff.
DarkWarrior on
0
Options
Mostlyjoe13Evil, Evil, Jump for joy!Registered Userregular
edited March 2010
We didn't hear about it as much in 2007 because there were fewer units sold back then. If I remeber correctly now wasn't it people who had older version of the firmware avoided the problem but the updated patch was the cause of it. (Trophy support was buggy back then.) They've had a few versions relesed since then. The real sucker punch about this is that older/first time adopters are getting hit the worse. Or people who bought used systems.
Overall I still think Sony's hardware this generation is the best, but it's still rather sad for the older units.
How would a firmware update even be possible on a global scale, since it, you know... requires PSN access? No doubt it will possible to just transfer the files, but... how will they even get that information out to people who aren't tech-savvy?
This is going to be an epic PR nightmare.
Cherrn on
All creature will die and all the things will be broken. That's the law of samurai.
Well, when an update is due, you actually physically cannot log on until you get the update. The update occurs before you even attampt to log on, so maybe the network will inform the system of the update before any connection to PSN is established?
Seanron on
PSN: Seanron - XBL: Seanron - Steam: Seanron
0
Options
Mostlyjoe13Evil, Evil, Jump for joy!Registered Userregular
How would a firmware update even be possible on a global scale, since it, you know... requires PSN access? No doubt it will possible to just transfer the files, but... how will they even get that information out to people who aren't tech-savvy?
This is going to be an epic PR nightmare.
Could they turn off the date check on the PSN side to allow the folks to log in, force install the firmware update, then reconnect normally? Doesn't Sony have overrides in place for stuff like this?
Posts
Sony CEO: "Ted, this new system is brilliant, and you've fully tested and approved it?"
Ted: "Yeah, it'll work like a dream!"
Fast forward to 01.03.2010
Sony CEO: "so Ted, the bloody thing breaks due to an error with leap years?"
Ted: "Umn, yeah, we didn't think it was a problem, I mean how often do they come round? Once in a blue moon?"
Sony CEO: "...Four years Ted, it's every four years..."
Ted: "I'll clear my desk!"
I looked at my friends list last night and was shocked that no one had signed on in several hours cause I have at least 5 people who picked up Heavy Rain and weren't playing it. Thought that was a bit odd.
Steam: TheArcadeBear
I sold my PS2 to help pay for the PS3 specifically because of the BC. Which at the time was being touted as an always thing.
Now I'm dreading the day my PS3 bites the dust. Dreading.
[edit]
Also, fuck. Throw me on the list of affected. I was wondering why I didn't pick up a single trophy in the second half of heavy rain, too. Not even the ending one.
I thought I was just doing really poorly.
I thought the problems didn't really start til today. Because if it started yesterday I should be fine, as I was online without problems, but I thought all PS3s with hardware BC were effected.
Guess I'll check my serial number when I get home from work and see what's what. My PS3 is a little over a year old (picked it up for Christmas 2008) so I might be affected. Pity.
Steam: TheArcadeBear
PSN: SirGrinchX
Oculus Rift: Sir_Grinch
No...
And Xaviar, what do you mean "the list of people who want a software fix?" There's a list of people who want to have to send their PS3 in, and lose features that they bought their PS3's early specifically to have?
In all seriousness, I understand that everyone is shitting their pants because PS3s are expensive, but I'd like us all to take some time before dropping our loads in our trousers. This is less than halfway into the day, and underwear isn't that cheap either. I'm not the biggest fan of how Sony manages things half the time, but staying calm is going to serve us all better than commencing the poo-cannon firing.
The error only kicked in at midnight last night, so you may still get the error. I hope not though!
3DS Friend Code: 2165-6448-8348 www.Twitch.TV/cooljammer00
Battle.Net: JohnDarc#1203 Origin/UPlay: CoolJammer00
It's even simpler than that! No need to maintain a string list of leap years when the math is right there. I mean, the math is so simple it's tragic if this is the problem. Here's the dead-easy, posted-on-wikipedia fix to properly determine a leap year:
if (year modulo 4 is 0) and (year modulo 100 is not 0) or (year modulo 400 is 0)
then is_leap_year
else
not_leap_year
I've written stuff like this into my own code when determining leap years. Whoever wrote the code for the low-level clock better get their walkin' papers stat! :P
For me thats at 10am. 9 hours away.
Anyone else remember getting the error in 2007? I got my PS3 pretty much on day of release and cannot remember that? If it's happened before though, it does give hope that a fix is imminent.
On the bright side UK Resistance always get all over this like nuns on a box of cucumbers
Half of me is laughing, the other half is crying.
Tumblr
I actually didn't turn on my console all weekend, due to normal family stuff. Guess I dodged a bullet so far. Will be waiting to see what happens now.
1) e4
PSN: SirGrinchX
Oculus Rift: Sir_Grinch
Sony
why you gotta hurt me like this.
I've been so paranoid and cautious about my 60 gig and now...
Do... Re... Mi... So... Fa.... Do... Re.... Do...
Forget it...
1) c5
Can trade TF2 items or whatever else you're interested in. PM me.
PSN: SirGrinchX
Oculus Rift: Sir_Grinch
Unfortunate.
Well, I guess I'll wait then and see what happens. Too bad, I was looking forward to some BC2. Oh well.
2) ExplosiveSheepe1
So yeah, I was all set to get back into some PS3ing since I was getting a bit burnt out on MW2 but this looks like a good reason to dig into the STEAM backlog a little more.
Can trade TF2 items or whatever else you're interested in. PM me.
My question is - How will users download a firmware update if they can't even connect to PSN?
Luckily I finished Heavy Rain last night.
Download on PC, transfer using memory stick
I don't remember even hearing about it happening then, but I guess I wasn't exactly looking either.
The part I bolded in the quote is complete rubbish, though. People are obviously going to be turning on their consoles, very few PS3 owners will have heard about it before experiencing the problem first hand.
Out of curiosity, why would this problem affect DLC data? I installed a Borderlands DLC pack yesterday and played a bit in a new area, but when I tried today (post the great PS3 apocalypse of '10 - insert rolling eyes smiley here) I was booted back to a non DLC area with a message that my character was in a DLC area, but that the DLC in question wasn't installed on my PS3.
Copyright checks. Bullshit basically. Sounds like the Borderlands DLC is as bad as that Oblivion stuff.
Overall I still think Sony's hardware this generation is the best, but it's still rather sad for the older units.
This is going to be an epic PR nightmare.
Could they turn off the date check on the PSN side to allow the folks to log in, force install the firmware update, then reconnect normally? Doesn't Sony have overrides in place for stuff like this?