Re: software raid0/striping on C: ?
From: Peter Wieland [MSFT] (peterwie_at_online.microsoft.com)
Date: 05/03/04
- Next message: Alex: "Re: Ndis names"
- Previous message: Stephan Wolf: "Re: Ndis names"
- In reply to: Alex: "Re: software raid0/striping on C: ?"
- Next in thread: Alex: "Re: software raid0/striping on C: ?"
- Reply: Alex: "Re: software raid0/striping on C: ?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 11:07:43 -0700
Sure it's possible - just about anything is possible. But you make it sound
like a trivial piece of work to take a big chunk of the WDM storage stack
and compile it into a real-mode component that can replace the bios
functionality.
It would be a lot of work, and it would require a lot of testing to make
sure it worked right in all scenarios and with a significant set of system
BIOSs (which have all sorts of interesting behaviors). And changing the
boot loader risks introducing new bugs in a component that must work right
on every Windows box in order for anything else to run.
I'm not commenting on the rightness or wrongness of Windows not supporting
RAID-0 system disks ... that's a question the storage team needs to evaluate
based on customer demand, development cost and overall risk. I'm just
trying to point out that features aren't always as simple to add as one
might think.
-p
-- This posting is provided "AS IS" with no warranties, and confers no rights. "Alex" <AlX@a> wrote in message news:OGxzkbTMEHA.1468@TK2MSFTNGP12.phx.gbl... > What if you combine the stripping driver for windows, with a boot time > BIOS > hook. The BIOS hook can be implemented with a replacement for the MBR > loader. > > "andrea catto'" <acatto@dataflight.com> wrote in message > news:%23dfeyzGMEHA.2792@TK2MSFTNGP10.phx.gbl... >> My topic here is to discuss why microsoft does not implement the ability > to >> utilize at OS-Setup two disks as raid0/striping. >> >> Yes I know, raid0 is not safe, or at least is just as safe a a 1-disk > which >> is the most popular solution for 99% of the users in the desktop > computing. >> >> So why after all not allowing this ??? >> >> I think users should be allowed doing this, assuming the risks on their > own. >> >> the fact of the matter is that nowadays everybody may afford a couple of >> hard drives and if put on different IDE channels/perhaps controllers they >> could 'fly' with raid0. >> >> This limitation indeed exixts within the Redhat/Fedora implementations >> too >> as well as others, but just because of 'lack of care' for those > requirements >> that many users would appreciate instead if given the chance. >> >> Slackware Linux on the other hand SHOWS that it is possible to in fact > have >> two separate devices paired as raid0 mounted on / (equivalent to c:) >> >> This raid0/striping on boot/root is way possible, I am a linux guru too, >> although I love and prefer Microsoft, and since it's possible because I > made >> it and used it, I am wondering if this limitation is made perhaps because >> the microsoft's disk structure/software could not handle this at all > unlike >> linux. >> >> > >
- Next message: Alex: "Re: Ndis names"
- Previous message: Stephan Wolf: "Re: Ndis names"
- In reply to: Alex: "Re: software raid0/striping on C: ?"
- Next in thread: Alex: "Re: software raid0/striping on C: ?"
- Reply: Alex: "Re: software raid0/striping on C: ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
