

|
By: Evren On: 04:38 Jul 8th, 2008 Offline |
Lets hope this doesnt end badly. It sucks that it happened in the first place really. |
|||
|
By: SwitchxA On: 04:49 Jul 8th, 2008 Offline |
Definitely. I was surprised Sony announced and released this big update so fast. They really aren't known for being so speedy. None the less it's nice to see they are on the ball on this one. | |||
|
By: Dragonfly On: 04:54 Jul 8th, 2008 Offline |
What perplexes me is how they failed to miss the problem in the first place. Poor testing is poor. Good to see its finally out though. |
|||
|
By: Snake Plissken On: 10:54 Jul 8th, 2008 Offline |
Problems? Seriously I noticed nothing XD well I have .1 now so I won't be seeing any I hope. |
|||
|
By: ManicGamer On: 04:47 Jul 8th, 2008 Offline |
The official statement claims that the errors occured on systems with specific "administrative data" saved on them. They don't go into detail on what that is... or what that means. There is speculation however. The section of the statement reads as follows: "prevented a limited number of PS3s from activating properly after updating to version 2.40, when certain system administrative data were contained on the HDD." That seems to be of some journalistic misunderstanding as well. The term "bricked" refers to a piece of hardware that requires at the very least a REPLACEMENT of a part of its hardware. The PS3 stores the admin data on the HDD. The FIRMWARE is on a separate memory assigned to be used for firmware only. This is why the people testing it claim they didn't catch it before the release. To forsee the issue, they would have had to have matching corrupted admin data on the test PS3's Hard Disks. This sort of thing happens with almost ALL firmware on all systems. NVIDA has had simmilar issues with PC's in the past. |
|||
|
By: Evren On: 06:04 Jul 8th, 2008 Offline |
yes, but at least a PC can be formatted and things can be reinstalled. BRICKING a PS3 is NOT on. Sony can kiss my ass. |
|||
|
By: Glorin On: 10:25 Jul 8th, 2008 Offline |
Luckily, I didn't download 2.40 so I didn't experience any problems. So that's a plus for me. I am glad I can now update to 2.41 worry free. ![]() |
|||
|
By: SwitchxA On: 11:33 Jul 8th, 2008 Offline |
Manic is right. PS3's were not bricked. They were only made unusable. If you formated the HDD and reverted back to a previous update you would be fine. That was a massive misunderstanding with this issue. Thanks Manic for explaining it in further detail. | |||
|
By: ManicGamer On: 07:51 Jul 9th, 2008 Offline |
EVEREN: yes, but at least a PC can be formatted and things can be reinstalled. BRICKING a PS3 is NOT on. Sony can kiss my ass. SWITCHXA: Manic is right. PS3's were not bricked. They were only made unusable. If you formated the HDD and reverted back to a previous update you would be fine. That was a massive misunderstanding with this issue. Thanks Manic for explaining it in further detail. .. No switch, thank YOU! I must have thought I explained what bricking was better than I did. |
|||
|
By: Evren On: 09:01 Jul 10th, 2008 Offline |
Well, Seeing as bricking generally means having to format, reinstall and lose everything...And actually, SONY themselves used the term for what happened. Im not going to argue anymore though. There's no need. |
|||
|
By: ManicGamer On: 08:17 Jul 10th, 2008 Offline |
Haha who's arguing? I was making fun of myself for not completing the thought on what "bricking" was. I meant to put wikipedias definition which basically says we are both right. For me: In the strictest sense of the term, bricking must imply that the device is completely unrecoverable without some hardware replacement. If the device can be repaired through software or firmware changes, it's not a brick. And for you: When used in reference to electronics, "brick" describes a device that cannot function in any capacity (such as a machine with damaged firmware). So now we don't even have to argue. ;) ... Love you Evren |
|||
