Klem: Regarding your 6 friends having a MBR failure in two days, by which magic they all got their Master Boot Record corrupted, that non-OS/non-partitioning softwares never write in (beside a few virus) ?
And how is that there is no trace of it online, on any forum ? (nice post on pcgamer.com btw) Maybe it means Steam has the power to censor all blogs, forums and websites on the Internet... Soon they'll be knocking at your door !
Red_Avatar: This was back in 2005 when Steam didn't have that many users
*only just a few hundreds of thousands, if not a million, of users playing Half-Life 1 mods (including CS)(since WON (RIP) was shutdown in mid-2004) and Half-Life 2* - all my friends played Counter Strike however, and so had Steam. No surprise you won't find much about it now - but despite your laughable defense (yet again), you still don't give a reason that makes sense except to make ridiculous guesses.
[snip]
You do really know nothing about MBR, do you? A MBR doesn't destroy ANYTHING on the drive itself and it is perfectly possible for software to cause the MBR to get corrupted. It's also easy to repair a MBR on NTFS drives with the chkdsk command. Please, if you're going to defend something, at least know how it works.
*snip*
Now, you know-it-all, still going to come up with sad excuses how it's not possible while you don't seem to even know what MBR does or means? And if you had any brains, you'd realise that, if within such a short period something so rare happens on so many different systems with only one piece of software in common that had just updated ... seriously? You make up excuses? And maybe you have an excuse why Steam deleted the topics as well, hmm?
Great, now you're providing additional informations regarding your grave accusations, now everyone can try to understand what happened.
Regarding the MBR, you can most of time fix it with chkdsk, but if it affects the partition table you're good for hours of recovering the data, and since most people don't know how to do it, they'll go to the next repair shop who'll format the HDDs and reinstall the OS. Technically it's just modifying boot and partition informations, but users are users and will destroy their own data while trying to "save" their computer, and if Steam caused that MBR corruption, Steam is responsible for the data loss because they can't expect their users to correctly deal with MBR issues.
You're saying that "it is perfectly possible for software to cause the MBR to get corrupted", it is indeed possible, any partitioning software does that (the partition table has to be modified some way). However, why the hell Steam would modify your partitions or modify your bootstrap code ? Steam never had a partitioning feature nor fiddled with boot, in 2005 there was no project of launching a Steam OS.
This is why I asked you to provide more details, because there quite a lot of other problems Steam could have caused and is likely to have caused in a faulty build of their client, but MBR corruption is probably the least probable.
Since you're bashing over Steam moderation without taking the time to understand how it works, I was afraid you wrongly attributed the responsibility for MBR problems to Steam, and this is why I asked for more details, like I asked for more details on your moderation-related issues.
and the Steam forum had several topics talking about their PC locking up after a reboot and then having drive problems so I then was sure it was Steam *I would love to see the details of these threads, it's really a shame you didn't made a backup*.
They rushed out a patch an hour or two later and then all topics were removed. Not locked, removed. If it hadn't been done during early afternoon European time on a week day, I'm sure a lot more people would have had it happen to them - but Americans were asleep and most Europeans were at work (and most of my friends were unemployed back then including me).
Then I guess "when 6 of my friends had a MBR failure in a span of
two days" was a typo, you meant 2 hours, now it's plausible that only a handful of users were affected: in 48h there would have been thousands of affected users and several threads on non-Steam forums.
Do you remember which part of the MBR Steam corrupting ? the boot part or the partition table ? If Steam is fiddling with such "intimate" part of our computer, users should be informed - especially now, they're "perhaps" planning on going on Linux (rumors of a Steam distro or a partnership with popular distros), so they're going to modify the MBR "again".
Now, you know-it-all, still going to come up with sad excuses how it's not possible while you don't seem to even know what MBR does or means? And if you had any brains, you'd realise that, if within such a short period something so rare happens on so many different systems with only one piece of software in common that had just updated ... seriously? You make up excuses? And maybe you have an excuse why Steam deleted the topics as well, hmm?
I prefer to call myself want-to-know.
I know what is a MBR, and if I missed something about it, I expect other users with a better knowledge of it to teach me what I got wrong, rather than calling me a fanboy and a retard. As far as I know, the MBR parts that could prevent a HDD from being recognized would the boot part or the partition table. They're only modified by the OS or partitioning software as far as I know. What is wrong there ?
"if within such a short period something so rare happens on so many different systems with only one piece of software in common" great, you're now bringing context to your accusation, this exactly what I was asking for in my previous post: explain and provide details. Like I said above, your misunderstanding of how the Steam platform works + very unlikeliness of such problem ("something so rare") lead me to believe you were pulling it out of your
hat.
Regarding your constant focus on "excuses", I need to repeat myself: I am no trying to determine who is guilty, I am trying to determine what really happened. Only once your accusation of a MBR corruption, something that could qualify Steam as a malware (according to some standards), we should proceed to judge Steam and see if:
- it was a complete mistake
- it was voluntary (who knows ?)
- it was the result of a lack of due care and testing
Remember the Myth II HDD-wiping fiasco: Bungie recalled as much faulty copies as they could (no matter the cost) => it seemed it was a genuine error, you couldn't blame Bungie of having that bug on purpose, or because they didn't care about their customers.
If Steam indeed caused MBR corruptions, were they guilty of a lack of due care or concern ? That question can only be answered once you fully proved Steam indeed caused such MBR corruptions.
Coincidence doesn't mean causality, and sadly you don't seem to be the most reliable person regarding the Steam platform when you call Steam forums moderators "Gestapo" and getting super-mad over a temp ban for writing f**k. This is why I am experiencing difficulty in believing you. If you were calm and were providing as much as details as you could on your accusations, I would be the first to thank you for giving us informations we couldn't get anywhere else.
Now regarding the assumed massive censorship on the Steam forum in 2005 over that bug, I find it strange that I can't find any trace of it anywhere else on the Internet - if my MBR was corrupted by Steam, and my threads were deleted on the SPUF, hell every major gaming forum would get my thread and every gaming news website would get an email - I don't understand how all the users who got their MBR corrupted walked away from it like if nothing had happened.
Now, assuming the MBR corruption did happened and was caused by Steam, if the Steam forum moderators deleted all the threads regarding that MBR corruption to "cover up" the fiasco, this is terribly wrong (for Steam) and I still don't get why it hasn't spawned a major "shitstorm" online.
In 2005 there was already quite a lot of people going on forums/news website on a daily basis and it wouldn't have required a gigantic effort to rally the flaming torches and pitch forks: everyone hated Steam because it was slow, it was crashing, it wasn't letting people play their game because the servers were frequently down. A MBR corruption would have been enough to start a month-long riot -at least-.
Finally, if the MBR-corruption-caused-by-Steam happened, if the forum "cleansing" happened, then we (me included) will immediately, now in September 2012, contact Steam for an answer, and if no answers are given within a week, publicly ask for that answer on every major gaming forums while sending all the details to news website. Why should we let a company get away with this and keep this precious information on a niche community forum like gog.com is baffling me.
Are you ready to take this public, to spread that information (MBR corruption + cleansing) and back it up in front of the whole world ?