Linked by Thom Holwerda on Sun 4th Jan 2009 21:47 UTC
Reviewing the first beta of an important release like Windows 7 is never an easy job to do. A confouding factor is that many people have already made up their mind about Windows 7; not because they have tried it, but because it's a Microsoft product, and therefore it sucks. At OSNews we try to judge products by their own merits, not by the parent company that created it. Read on for a set of impressions regarding the Windows 7 beta.
Permalink for comment 342313
To read all comments associated with this story, please click here.
No, it isn't. The way Windows handles the MBR during an installation does not cause errors, conflicts, or instabilities within Windows
Besides the point, but yes, it actually does. It always renders the first-to-be-installed Windows version in a Windows multiboot setup unbootable. Steps to reproduce:
Install Windows Xyz
Install Windows Xyz+1
Remove Windows Xyz+1
Windows Xyz will not boot.
100% reproducible. I'll let you figure out on your own why this is the case.
By your logic any piece of software that doesn't work well with an OS other than the one for which it was written is flawed
Nonsense.
When I install Windows, or any other OS, I give it permission to use a certain part of the disk, partition Abc. The MBR is NOT part of that permission, and as such, I never granted Windows the permission to put its filthy paws all over the MBR. The MBR should not be touched by anything unless I specifically grant something permission to do so.
Member since:
2005-06-29
Besides the point, but yes, it actually does. It always renders the first-to-be-installed Windows version in a Windows multiboot setup unbootable. Steps to reproduce:
Install Windows Xyz
Install Windows Xyz+1
Remove Windows Xyz+1
Windows Xyz will not boot.
100% reproducible. I'll let you figure out on your own why this is the case.
Nonsense.
When I install Windows, or any other OS, I give it permission to use a certain part of the disk, partition Abc. The MBR is NOT part of that permission, and as such, I never granted Windows the permission to put its filthy paws all over the MBR. The MBR should not be touched by anything unless I specifically grant something permission to do so.
So yes, this is a bug.
Edited 2009-01-04 22:53 UTC