To view parent comment, click here.
To read all comments associated with this story, please click here.
Why are you defending Microsoft's stance that they control the MBR and can tell everyone what to put on it, and how to?
I am surprised they have not been sued over it yet, and I wish they would for how annoying it is to fix it every time that messy windows guy comes back to my house.
Nice classic strawman argument there, "You dislike item A so I'm incorrect for pointing out issues with statement B." The two items are in no way related. I'm not defending Microsoft, I'm pointing out that the author's statement of that functionality being a bug is incorrect. Regardless of who makes the software or how many people dislike the way it behaves the feature being discussed is, within the bounds of its design, not incorrectly implemented. Whether the design is flawed or not is an entirely different argument.







Member since:
2006-02-01
Your claim of a bug in the Windows installer is based on the usage case of you forcibly removing a version of Windows from your computer and then expecting that now nox-existent operating system be able to clean up after itself? That's absurd. If you, external to the OS, used a tool to repartition your HD then you need to be responsible for cleaning up the MBR records. After all, like you said, it's your HD that you have the power to grant permission to. If you exert that level of ownership than you need to exert an equal level of responsibility for the actions you take on that HD.
Expecting WindowsXYZ+1 to be able to fix your computer after it is gone or for WindowsXYZ to maintain a holistic view of everything that happens on your HD, even items external to itself, and clean it all up for you is pretty wishful thinking.
The way Windows treats the MBR currently is not a bug. What you want is clearly new functionality, therefore it is a feature request.