On Thu, 5 Apr 2007 21:26:31 -0700, "Gary VanderMolen"
While beta testing Vista, we were repeatedly told by MS reps
that dual-booting was not a common scenario, and by implication
they wouldn't spend any time on it. That was also their reason
for turning down numerous requests for a GUI version of
BCDedit.
"Support your own feature set, Luke"
They definitely should have tested dual-booting with all existing MS
OSs at least, as well as Linuxen etc.
An OS does not "own" the PC; it is one of up to 4 possible guests on
the PC system, and it mustn't mess with the other guests.
That either means respecting other OSs partition type bytes and not
screwing around in their partitions, or if you share partition types
as you're "the same OS family", then the incest taboo should hold.
The Vista team should know very well what XP's behavior should be, and
thus take care to dance around it. And if XP was so badly behaved
that it dives into installations that are not "its own", then
hopefully the Vista team will have cleaned up that behavior in Vista.
I thought XP had got it right, after WinME's total cluelessness that
not all \_Restore belong to it (e.g. dual-booted WinME installs). XP
took trouble to subtree its SVI contents as identified by
installation, so that dual-booted XP wouldn't play with each other's
SR data. It's hard to see how a different OS, developed from the
ground up after XP was a known state of 5 years' standing, could
manage to throw itself under XP's wheels.
------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope