Reading through the comments, the decision to remain at 2.80 seems to be a decidedly tough but necessary choice to avoid any possible chance of bricking the system or losing the Blu-ray drive to 3.01.
Granted, 2.80 no longer gives the user access to PSN, doesn’t run games that require 3.00 or higher, doesn't allow the user to download patches/updates for games that might need them, and doesn't allow access to online gaming or internet browsing, but the risk of upgrading to 3.01 has left others, and could leave this user with even less.
The ability to continually enjoy currently owned PS3 titles, Blu-ray discs, currently installed PSN media purchased, photos uploaded via the Flash memory reader, and pre-3.00 games sitting on store shelves, seems to be a better option than forking over even more money if 3.01 bricks the console or deep-sixes the Blu-ray drive.
Tough still was the decision to maroon $35 in credit on the PSN store, being that 2.80 no longer allows PSN users to spend money. Realistically this amount can be viewed as a small severance fee forked over to hopefully secure a continually functional home media console, and doesn't warrant as much fuss as the $150 required for repair, or the $300-$350 to purchase a Slim.
Cutting the losses at this point might seem to some like a drastic decision, but functionality is the main reason the console was purchased, and hopefully preserving this functionality by sticking with 2.80 will only sting when games like Gran Turismo 5, Dead Rising 2, or Criterion's Need for Speed are released later on.
Ultimately firmware 3.01 is by no means mandatory, as staying with 2.80 is 100% possible. The only thing mandatory about 3.01 is the thought you should give to whether or not you have an extra $150-$350 to get back on board in the event of a problem, or whether or not you can live without certain features, games, or content if you decide to stay with 2.80. #ps3
@FiveSpeed: I can understand wanting to be cautious like that, but personally I held off for a while to see how widespread it was, and because I always lag behind for updates on any system just to be safe. Then I installed the update, and it's been smooth sailing since.
I really think this is probably more like a 1 in 100,000 thing as opposed to say, RRoD which is like 4 in 5 historically. Clearly there is some amount of correlation with the updates, but the vast majority seem to be alright.
Of course, it's not like I'd step up and reimburse you if you updated and it bricked, but I'd put my own system through it again and again. I think the odds are probably much higher that you'd get into a crash driving your car on any given day than bricking a PS3 with a software update, and while you'd stand to lose a lot more from it, you'd still drive, right? #ps3
I've had six PS2's crap out on me. Six. When I'd look in them with a flashlight, they were all choked with dust. The fans, by the way, PULL air through the system, which means putting a filter on the fan was impossible.
And when I called Sony about the first one, I asked if I could use a CD cleaner? Would void the warranty. Vacuum cleaner? Void the warranty. Filters? Compressed air? All void the warranty.
Finally, I asked how the hell I was supposed to get the dust OUT. I was told that the PS2 does not collect dust. I said, "I can see it". I was told I was mistaken.
I've also gone through over a dozen controllers, all first-party, and at least that many memory cards. In fact, there's no way to re-format the memory card without using third party software. Pathetic.
I have no doubt this is Sony's fault, and Sony has been a colossal jackass about acknowledging their own bad designs for years. And it's not like 3.0 was fool-proof, there were a lot of glitches. If they can't even properly test their firmware for basic functionality, how can anyone assume they tested for hardware compatibility or real-life operation? I guarantee they tested this only on brand-fucking-new systems and that was it.
Fuck 'em, they should either fix their screwups or pay a penalty. Welcome to real life, Sony. This is what it feels like to be dicked. We call that irony. #ps3
Sign me up, my 60gb bd drive bricked right after 3.1 without ever having problems before, and I treated that thing like a freakin newborn. If Sony doesn't want to admit it and just call it a coincidence that they're repairing mine for free, that's fine with me. It just pisses me off when I can search online and find out there are quite a few people experiencing the exact same problem at the exact same time without knowing for sure if mine just crapped out or it was killed by a firmware update. I had next to no hours on that drive either. :( #ps3
Wow. Now that I think about it, I'm on my second PS3 now.
My first PS3 (a original 80 GB model, backwards compatible) stopped reading discs completely after a system update.
Upon some research I found out this was a pretty common issue with these models, so I thought that the blu ray lens dying right after a system update was just a coincidence.
Here's the point: I don't live in the U.S, so I couldn't send it to sony for repairs. And I paid almost $800 for that system. Yeah, shit is expensive in my country.
So, I sold it to someone for about $300, and bought a brand new PS3 at almost $600. And no backwards compatibility at all this time.
If my current PS3 broke after a firmware update, I'd be incredibly pissed, too, and I would try to sue Sony for that. Anyway, I couldn't do it, because I don't live in the U.S.
To add insult to injury, the Sony store were I purchased my new PS3 has closed, and I haven't seen any other Sony stores where I live, so if my PS3 breaks, I don't know if I'll be able to apply the warranty, because where could I do it? :(
The worst part is, that I would completely buy ANOTHER PS3 if my current one stopped working and hadn't any way to repair it or to apply the warranty, so I'm part of the problem. Consumism really sucks. #ps3
@gurfinki: You don't need to go to the store you purchased your PS3; most likely your in-store warranty is void by now, but sony offers a warranty for 1 yr i think, you just have to call the number on the warranty that is provided inside the box of the PS3, they have repair centers pretty much anywhere, the worst that could happen is that you would have to ship it, and most of the times sony pays for it. #ps3
@queso_plas: Yeah, I know. My second PS3's warranty is still up to date. But Sony will only cover shippings inside the U.S, and I don't live in the US. So, I'd have to pay for the shipping to U.S myself, and pay for the shipping back as well. That's more expensive than buying a new PS3 here. #ps3
I've heard that there's a reason why so many 360s and PS3s die during firmware updates... Its supposedly to do with rarely used files within the hardware, or even rarely used parts of the hardware itself becoming corrupted/damaged. On a day-to-day basis these parts aren't being used so its unlikely they'll cause a problem, but when it comes to updating the firmware the console will look for the files and be like "WTF!? BOOM!" and die on its arse.
So Sony is most likely in the right on these court cases... whilst technically the firmware does make the problems manifest themselves, they aren't their initial cause! #ps3
@exion: Then I think Sony and Microsoft need some sort of fail-safe in place so either the user can fix a borked update on their own or fix it for free. With the iPhone there are a few ways you can recover your phone if anything were to happen during a firmware update. Firmware updates are great and all but it has the potential to screw up your system if everything doesn't go smoothly. #ps3
@ichiban1081: This I agree with, whereas I don't think lawsuits are the way forward, they might at least make Sony/MS reconsider implementing a rollback feature... You can unofficially do this on the PSP with a pandora's battery (a bricked PSP can be revived and reverted to an earlier firmware by using a combination of special/modified battery and memory stick) which is awesome, but for the very same reason it's unlikely to occur for the PS3/360 due to it opening up earlier firmwares that are more prone to firmware exploits and potentially opening up the floodgates to piracy without hardware mods.
As for it being entirely Sony's fault, that I disagree with... if it's a bug directly caused by the firmware, fair enough, that's their fault, but if the firmware merely bugs out due to bits of hardware being inaccessible because of damage caused by dust, moisture or nesting cockroaches within the hardware, which is what I was really getting at in my initial post, then sony/microsoft shouldn't be held accountable. #ps3
@exion: Nesting cockroaches... I can just imagine a Sony/MS employee opening your console to fix a problem and seeing a cockroach melted next to the GPU. Embarrassing, but I do agree with you about those points as well. #ps3
@ichiban1081: it's more common than you'd imagine... Apparently its a common problem that console repair shops experience, especially in the more humid marts of North America...
Though according to a friend of mine who used to work repairing and modding consoles, they used to get at least 5 consoles a week which had stopped working because they were crammed with cockroaches who were presumably trying to keep warm, nestled in the belly of a playstation. gross, eh? #ps3
@exion: LOL, gross and embarrassing. Thanks for that information though, didn't think that would be such a common problem but it does make sense and if that is the case with people's game consoles dieing then you are right, the manufacturer shouldn't have to pay. Maybe they need to work something out after you already send in your console. #ps3
While that does sound like a rage-inducing situation, the default response of "pay me lots of money" whenever someone feels they've been slighted always repels my feelings of empathy. #ps3
It's blatantly obvious what's going on here. SCEA is knowingly releasing corrupt firmware updates that are bricking otherwise perfectly working PS3 consoles. They've been able to get away with it up until now because there hasn't been a solid pattern with relation to which models are failing. It's been kind of random. A few instances here and there, but not an epidemic. Basically what happens is the firmware acts as a Trojan horse for a line of code that corrupts the system software upon installation rendering the console useless. Since owners are unable to revert back to a previous version of the PS3 system software (thanks a lot SCEA), they have no other option but to send it in SCEA's repair facility in Texas. I know this because I actually had to pay the $150.00 service fee for out of manufacturer warranty service when my Ps3 stopped working after I was forced to install a crappy firmware update to play Fallout 3. I mean I love Sony, but this experience left me with an extremely bitter taste in my mouth. All I can say now is that I'm glad someone finally filed a lawsuit. Since this is class action, and presuming that the courts side with consumers, which they should, I will be one of the first in line to get my $161.67 (after tax) back. PS3 owners shouldn't have to fork over $150.00 to repair a console that Sony broke.
@sporozoa: Ridiculous and completely false statements, why was this promoted? You are angry at Sony we get it, but suggesting Sony knowingly corrupts systems? Seriously?
This is speculation and nothing more, you offer no solid proof. There may be issues with firmware upgrade but to even consider the notion that Sony, Microsoft or Nintendo knowingly corrupts a very small percentage of users systems by it's own hand is just an ignorant statement to make on it's own.
What next, Sony is responsible for 9/11? Microsoft threw votes away for McCain? C'mon. #ps3
@-Thunder-: The proof is in the comment sections of forums across the web that detail the the fraudulent business practices of SCEA. This has been going on for how many years now? For to acknowledge that they are not putting their firmware through a rigorous beta test before its release would be to acknowledge that they are culpable. Sony has received a lot of negative feedback about their console slaying deus ex machina firmware updates, and all we get back in response is denial. The only ignorant statements being made are from SCEA customer service representatives when they make duplicitous statements about how they've never heard of PS3 bricking after a firmware installation.
How can I get in on this? My PS3 bricked after 3.01 too.
Seriously, this is a pretty big issue. I've read of numerous threads on several sites as well as articles in engadget and others that have been claiming 3.01 bricked the system by overpowering the BR drive and causing it to fail.
I guarantee this was not just a coincidence. Too many people have been complaining of this exact same problem at the exact same time frame. #ps3
"SCE AND ITS AFFILIATED COMPANIES EXCLUDE ALL LIABILITY FOR ANY LOSS OF DATA, LOSS OF PROFIT, OR ANY OTHER LOSS OR DAMAGE SUFFERED BY YOU OR ANY THIRD PARTY, WHETHER DIRECT, INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL HOWEVER ARISING, AS A RESULT OF ACCESSING TO OR USING THE SYSTEM SOFTWARE OR ANY OF THE CONTENTS, PROGRAMS, FEATURES OR SERVICES ON OR PROVIDED THROUGH THE SYSTEM SOFTWARE. SO LONG AS THIS PROVISION IS ENFORCEABLE IN YOUR JURISDICTION, THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE."
I guess they didn't read the click-through-licence... #ps3
@Vylen: "SO LONG AS THIS PROVISION IS ENFORCEABLE IN YOUR JURISDICTION, THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW"
ie: if you live in a jurisdiction with any form of consumer rights, this entire sections means jack shit.
@Vylen: "SO LONG AS THIS PROVISION IS ENFORCEABLE IN YOUR JURISDICTION, THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE."
As far as I'm aware, a lot of jurisdictions have evoked laws against blanket exclusion of liability statements.
@GoonerVance: ahem.. nothing constructive to say? be less of a prick, thanks.
In any case, assuming they're in a jurisdiction that provides consumer protection laws, wouldn't it be better to go to the consumer protection group rather than risk losing money on a civil action?
Unfortunately the article doesn't shed light as to what jurisdiction this is in or what state the papers have been served. #ps3
@GoonerVance: In the case of a class action lawsuit, where consumers range from many different jurisdictions, they won't pick and choose who wins. If its not enforceable in one, its not enforceable in all. By listing "all PS3 owners" they screwed themselves. #ps3
@sbongard15: Huh? Where did you get this from? The case and the subsequent payout from the case is dependent upon where the claim is filed, not necessarily where the plaintiffs are actually from. Unless you're citing something that I haven't thought of... #ps3
@NeVeRMoRe666: It's not necessarily that they've evoked laws against such blanket statements, but more that they've allowed legal actions to proceed in order to determine whether or not such statements or agreements should stand in light of major violations to consumer rights. #ps3
@NeVeRMoRe666: It's true that cases are typically dependent on the location of the filing; however, cases are also dependent on which region has the greatest vested interest. In other words, it is possible for the courts to look at the case, and look at "all PS3 owners" and move the case and apply the law as it stands for the region where the majority of such owners exists (generally with the exception of moving the case outside of the country of origin unless otherwise specifically demanded by the majority of the plaintiffs, but still, in those cases often multiple claims in different countries could occur).
@NeVeRMoRe666: Ah crap read that wrong, thought it said they filed 2 different lawsuits, one from Iowa and Texas. Had they filed separate suits they would be screwed, but if its within a single jurisdiction you are correct. My fault on that one. I need to get some sleep. Damn DJ Hero... #ps3
@illiniphase4: Right. It really depends on whether they can sufficiently prove to the court that the court in question has jurisdiction over the subject matter of the litigation.
To everyone defending these idiots and claiming "Sony should do it because MS has a 3yr Warranty and fixed my X360 5 times already". Please STFU... The reason MS has a 3yr RROD Warranty is because their failure rate is insanely high, I doubt the PS3's is even in the double digits.
MS did it to avoid a class action lawsuit, simple as that. Their console is known for its failures... the PS3 is not. I am a 60gb owner and have not had any issue with my console. #ps3
@EGBTMagus: I agree. I have owned each console since launch and my 60gb PS3 is the only console that didn't fail. I am really quite impressed with that with how much it is used. #ps3
@EGBTMagus:
So, just because Sony has a lower failure rate, they should not be responsible for those failures?
People buy a product on the basis that it works, if it stops working because of something the manufacturer did (ie, release faulty firmware), then it should be the manufacturer's responsibility to cover the cost of fixing the problem.
To use an example from the last time this issue came up, Sony charging people to repair consoles bricked by the firmware is like someone driving into your house and breaking a wall, then charging you to fix it.
If Sony is at fault (which is for the courts to decide), then they should be liable for the cost of repairs.
Consumers have rights, we should be applauding those who fight for them, not cheering for the company abusing them. #ps3
@Your_Neighborhood_Spaceman: @Akihiko: @EGBTMagus: I would laugh my ass off if, in an ironic twist, you log out of kotaku and turn on your machine to play a little Uncharted 2 and it gives you the YLOD fuck off sign.
Don't lie. I know your type. Right now, you're full of bravado yet as soon as you have a problem you'll be up there front and centered trying to cash in on their lawsuit. No question. #ps3
@NeVeRMoRe666: To be honest, no, I wouldn't. It would give me justification to buy a PS3 slim. There are far better things to get upset over than an appliance taking a dive. As a side note, I can easily simulate the experience of being bricked when I try to connect to Home™. #ps3
Don't think it is, but I doubt it's a coincidence. Since BD drives were affected by the update, it's likely certain versions of the drive were at fault and not the firmware. #ps3
Why don't people just sue for the money it costs to repair their console? NO, PAIN AND SUFFERING. I NEED $9,000,000. Sony would probably just give them free repairs to get out of the hassle of going to court. o0 #ps3
@NeVeRMoRe666: So... shady legal practices are better than shady business practices? Not to mention that with this system you end up getting both anyways... #ps3
@MtlAngelus: I disagree. While admittedly, there are a ton of shady lawyers, particularly in the states with tier four degrees, punitive damages serve a very important function in the legal system.
If you want a thorough examination of the issue, I would recommend this article- it's long but worth the read:
But to summarize, in short: If there wasn't any punitive damages- a larger company like Sony for instance, can continue to do whatever best helps their profit motive without consequence- say not repairing consoles they accidentally bricked- simply because it's in their best interest to do so. If someone is to say, sue for $150- Sony can afford the legal resources to stall- subsequently leading to a dismissal and deterring all future lawsuits because the plaintiff pursuing it would find the legal cost to pursue it would be more expensive than the initial $150 they were seeking in the first place. Others seeing this would expect the same result and thus would not seek compensation because Sony has demonstrated the avenue to do so is impractical and expensive even when the company or Sony here, is in the wrong.
Furthermore, without punitive damages, Sony and other companies could continue carrying out whatever it is they are doing without any major consequences. For example, they might find that rolling out a comprehensive repair program would be more costly than settling the odd lawsuit here and there.
In this case, for a gaming system, the cost of not having punitive damages maybe inconsequential as it's only a gaming system made for entertainment but when it comes to something with more gravity, like say the Ford Pinto case, punitive damages are absolutely necessary. Companies have to be held accountable for their products.
During the 1970s (?), Ford had released a car model that would literally blow up if the car was rear ended. Upon realizing this, the Ford Co. had figured out that the cost of dealing with potential lawsuits would be far less than having a nationwide recall program (at a measly $11 a pop to fix the manufactures defect- some retaining clip or something- can't remember+ bad publicity) so they kept the issue mum.
Sufficient to say, a lot of people got hurt and/or killed because of that decision. This is why punitive damages are so important. It is to punish companies from doing it again. A $10M lawsuit against Ford co. would hardly be a blip on their day to day earnings but a $100M judgement would make them think twice next time they realize their product could potentially harm the lives of their customers.
I have no idea why people here and in the states so often take the side of the big companies (my analysis is probably because the mass media and most news outlets are run by "big business"- spinning cases with a few lines and quotes taken out of context is notoriously easy when you have the billions to back it up). A lot of these cases which while prima facie, seem frivolous actually hold a lot of merit when you have the chance to read the actual court documents. These laws are here to protect the customers, the consumers, the little guys. Sad to say, the companies, the tort reformist and their brands have you eating out of their hands.
@Adhominem: 99% of statistics are made up right on the spot....
So what are you saying? My friend had his PS3 bricked from a firmware update- all he did was turn it on and downloaded the new update and the system froze and then stopped turning on. How is it his fault? And why should he be required to pay $150? #ps3
11/05/09
Granted, 2.80 no longer gives the user access to PSN, doesn’t run games that require 3.00 or higher, doesn't allow the user to download patches/updates for games that might need them, and doesn't allow access to online gaming or internet browsing, but the risk of upgrading to 3.01 has left others, and could leave this user with even less.
The ability to continually enjoy currently owned PS3 titles, Blu-ray discs, currently installed PSN media purchased, photos uploaded via the Flash memory reader, and pre-3.00 games sitting on store shelves, seems to be a better option than forking over even more money if 3.01 bricks the console or deep-sixes the Blu-ray drive.
Tough still was the decision to maroon $35 in credit on the PSN store, being that 2.80 no longer allows PSN users to spend money. Realistically this amount can be viewed as a small severance fee forked over to hopefully secure a continually functional home media console, and doesn't warrant as much fuss as the $150 required for repair, or the $300-$350 to purchase a Slim.
Cutting the losses at this point might seem to some like a drastic decision, but functionality is the main reason the console was purchased, and hopefully preserving this functionality by sticking with 2.80 will only sting when games like Gran Turismo 5, Dead Rising 2, or Criterion's Need for Speed are released later on.
Ultimately firmware 3.01 is by no means mandatory, as staying with 2.80 is 100% possible. The only thing mandatory about 3.01 is the thought you should give to whether or not you have an extra $150-$350 to get back on board in the event of a problem, or whether or not you can live without certain features, games, or content if you decide to stay with 2.80. #ps3
11/05/09
I really think this is probably more like a 1 in 100,000 thing as opposed to say, RRoD which is like 4 in 5 historically. Clearly there is some amount of correlation with the updates, but the vast majority seem to be alright.
Of course, it's not like I'd step up and reimburse you if you updated and it bricked, but I'd put my own system through it again and again. I think the odds are probably much higher that you'd get into a crash driving your car on any given day than bricking a PS3 with a software update, and while you'd stand to lose a lot more from it, you'd still drive, right? #ps3
11/05/09
And when I called Sony about the first one, I asked if I could use a CD cleaner? Would void the warranty. Vacuum cleaner? Void the warranty. Filters? Compressed air? All void the warranty.
Finally, I asked how the hell I was supposed to get the dust OUT. I was told that the PS2 does not collect dust. I said, "I can see it". I was told I was mistaken.
I've also gone through over a dozen controllers, all first-party, and at least that many memory cards. In fact, there's no way to re-format the memory card without using third party software. Pathetic.
I have no doubt this is Sony's fault, and Sony has been a colossal jackass about acknowledging their own bad designs for years. And it's not like 3.0 was fool-proof, there were a lot of glitches. If they can't even properly test their firmware for basic functionality, how can anyone assume they tested for hardware compatibility or real-life operation? I guarantee they tested this only on brand-fucking-new systems and that was it.
Fuck 'em, they should either fix their screwups or pay a penalty. Welcome to real life, Sony. This is what it feels like to be dicked. We call that irony. #ps3
11/05/09
11/05/09
My first PS3 (a original 80 GB model, backwards compatible) stopped reading discs completely after a system update.
Upon some research I found out this was a pretty common issue with these models, so I thought that the blu ray lens dying right after a system update was just a coincidence.
Here's the point: I don't live in the U.S, so I couldn't send it to sony for repairs. And I paid almost $800 for that system. Yeah, shit is expensive in my country.
So, I sold it to someone for about $300, and bought a brand new PS3 at almost $600. And no backwards compatibility at all this time.
If my current PS3 broke after a firmware update, I'd be incredibly pissed, too, and I would try to sue Sony for that. Anyway, I couldn't do it, because I don't live in the U.S.
To add insult to injury, the Sony store were I purchased my new PS3 has closed, and I haven't seen any other Sony stores where I live, so if my PS3 breaks, I don't know if I'll be able to apply the warranty, because where could I do it? :(
The worst part is, that I would completely buy ANOTHER PS3 if my current one stopped working and hadn't any way to repair it or to apply the warranty, so I'm part of the problem. Consumism really sucks. #ps3
11/05/09
11/05/09
11/06/09
11/05/09
So Sony is most likely in the right on these court cases... whilst technically the firmware does make the problems manifest themselves, they aren't their initial cause! #ps3
11/05/09
11/05/09
As for it being entirely Sony's fault, that I disagree with... if it's a bug directly caused by the firmware, fair enough, that's their fault, but if the firmware merely bugs out due to bits of hardware being inaccessible because of damage caused by dust, moisture or nesting cockroaches within the hardware, which is what I was really getting at in my initial post, then sony/microsoft shouldn't be held accountable. #ps3
11/05/09
11/05/09
Here's a commonly mentioned story:
[www.destructoid.com]
Though according to a friend of mine who used to work repairing and modding consoles, they used to get at least 5 consoles a week which had stopped working because they were crammed with cockroaches who were presumably trying to keep warm, nestled in the belly of a playstation. gross, eh? #ps3
11/05/09
11/05/09
11/05/09
11/05/09
This is speculation and nothing more, you offer no solid proof. There may be issues with firmware upgrade but to even consider the notion that Sony, Microsoft or Nintendo knowingly corrupts a very small percentage of users systems by it's own hand is just an ignorant statement to make on it's own.
What next, Sony is responsible for 9/11? Microsoft threw votes away for McCain? C'mon. #ps3
11/05/09
11/04/09
Seriously, this is a pretty big issue. I've read of numerous threads on several sites as well as articles in engadget and others that have been claiming 3.01 bricked the system by overpowering the BR drive and causing it to fail.
I guarantee this was not just a coincidence. Too many people have been complaining of this exact same problem at the exact same time frame. #ps3
11/04/09
"SCE AND ITS AFFILIATED COMPANIES EXCLUDE ALL LIABILITY FOR ANY LOSS OF DATA, LOSS OF PROFIT, OR ANY OTHER LOSS OR DAMAGE SUFFERED BY YOU OR ANY THIRD PARTY, WHETHER DIRECT, INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL HOWEVER ARISING, AS A RESULT OF ACCESSING TO OR USING THE SYSTEM SOFTWARE OR ANY OF THE CONTENTS, PROGRAMS, FEATURES OR SERVICES ON OR PROVIDED THROUGH THE SYSTEM SOFTWARE. SO LONG AS THIS PROVISION IS ENFORCEABLE IN YOUR JURISDICTION, THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE."
I guess they didn't read the click-through-licence... #ps3
11/04/09
"SO LONG AS THIS PROVISION IS ENFORCEABLE IN YOUR JURISDICTION, THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW"
ie: if you live in a jurisdiction with any form of consumer rights, this entire sections means jack shit.
11/04/09
As far as I'm aware, a lot of jurisdictions have evoked laws against blanket exclusion of liability statements.
11/04/09
11/04/09
You just got pwned and you provided your own whoopin' stick. #ps3
11/04/09
11/04/09
In any case, assuming they're in a jurisdiction that provides consumer protection laws, wouldn't it be better to go to the consumer protection group rather than risk losing money on a civil action?
Unfortunately the article doesn't shed light as to what jurisdiction this is in or what state the papers have been served. #ps3
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09
You're just way more elegant than I.
;)
11/04/09
The way I see it, if Sony won't fix their mistake and have to be taken to court, they should fix it and cover legal charges.
That's just ridiculous to expect the consumer to pay out of pocket for a technical issue caused by the manufacturer. #ps3
11/04/09
PS: I can say that, I play a doctor on TV. #ps3
11/04/09
11/04/09
I received my medical training from Trauma Center, my legal training from Phoenix Wright and my combat training from Call of Duty.
Any subject you have, I can act as an expert on. #ps3
11/04/09
11/04/09
;) #ps3
11/05/09
11/04/09
MS did it to avoid a class action lawsuit, simple as that. Their console is known for its failures... the PS3 is not. I am a 60gb owner and have not had any issue with my console. #ps3
11/04/09
11/04/09
So, just because Sony has a lower failure rate, they should not be responsible for those failures?
People buy a product on the basis that it works, if it stops working because of something the manufacturer did (ie, release faulty firmware), then it should be the manufacturer's responsibility to cover the cost of fixing the problem.
To use an example from the last time this issue came up, Sony charging people to repair consoles bricked by the firmware is like someone driving into your house and breaking a wall, then charging you to fix it.
If Sony is at fault (which is for the courts to decide), then they should be liable for the cost of repairs.
Consumers have rights, we should be applauding those who fight for them, not cheering for the company abusing them. #ps3
11/04/09
Don't lie. I know your type. Right now, you're full of bravado yet as soon as you have a problem you'll be up there front and centered trying to cash in on their lawsuit. No question. #ps3
11/04/09
11/04/09
11/04/09
11/04/09
Joke? #ps3
11/04/09
Don't think it is, but I doubt it's a coincidence. Since BD drives were affected by the update, it's likely certain versions of the drive were at fault and not the firmware. #ps3
11/05/09
11/04/09
11/04/09
It's to deter shady business practices! #ps3
11/04/09
11/04/09
If you want a thorough examination of the issue, I would recommend this article- it's long but worth the read:
[marcgalanter.net]
But to summarize, in short: If there wasn't any punitive damages- a larger company like Sony for instance, can continue to do whatever best helps their profit motive without consequence- say not repairing consoles they accidentally bricked- simply because it's in their best interest to do so. If someone is to say, sue for $150- Sony can afford the legal resources to stall- subsequently leading to a dismissal and deterring all future lawsuits because the plaintiff pursuing it would find the legal cost to pursue it would be more expensive than the initial $150 they were seeking in the first place. Others seeing this would expect the same result and thus would not seek compensation because Sony has demonstrated the avenue to do so is impractical and expensive even when the company or Sony here, is in the wrong.
Furthermore, without punitive damages, Sony and other companies could continue carrying out whatever it is they are doing without any major consequences. For example, they might find that rolling out a comprehensive repair program would be more costly than settling the odd lawsuit here and there.
In this case, for a gaming system, the cost of not having punitive damages maybe inconsequential as it's only a gaming system made for entertainment but when it comes to something with more gravity, like say the Ford Pinto case, punitive damages are absolutely necessary. Companies have to be held accountable for their products.
During the 1970s (?), Ford had released a car model that would literally blow up if the car was rear ended. Upon realizing this, the Ford Co. had figured out that the cost of dealing with potential lawsuits would be far less than having a nationwide recall program (at a measly $11 a pop to fix the manufactures defect- some retaining clip or something- can't remember+ bad publicity) so they kept the issue mum.
Sufficient to say, a lot of people got hurt and/or killed because of that decision. This is why punitive damages are so important. It is to punish companies from doing it again. A $10M lawsuit against Ford co. would hardly be a blip on their day to day earnings but a $100M judgement would make them think twice next time they realize their product could potentially harm the lives of their customers.
I have no idea why people here and in the states so often take the side of the big companies (my analysis is probably because the mass media and most news outlets are run by "big business"- spinning cases with a few lines and quotes taken out of context is notoriously easy when you have the billions to back it up). A lot of these cases which while prima facie, seem frivolous actually hold a lot of merit when you have the chance to read the actual court documents. These laws are here to protect the customers, the consumers, the little guys. Sad to say, the companies, the tort reformist and their brands have you eating out of their hands.
11/04/09
11/04/09
You must really hate politicians then #ps3
11/04/09
11/04/09
11/04/09
So what are you saying? My friend had his PS3 bricked from a firmware update- all he did was turn it on and downloaded the new update and the system froze and then stopped turning on. How is it his fault? And why should he be required to pay $150? #ps3