What's with the 100 Mb partition that Windows 7 likes to create on installation? I've had this before, with XP, where the OS installs the boot partition on a drive other than the one on which I am installing Windows. The way I see it, the user should have absolute control over where Windows is putting its filthy boot code!!
I installed Windows 7 on a particular partition, but it decided to place its pointless 100 Mb partition on a *completely different drive*, with absolute disregard for the RAID data that used to be there. As it happens, I don't need that RAID data, but it's not the point. I also wanted to use that drive (and another identical drive) to form a new RAID 0, but of course I can't with that partition on one of the drives. Thus, I had to unplug the drives and REINSTALL Windows 7 all over again, withholding any places where it would otherwise place this 100 Mb partition.
I hope the developers responsible read this and are so overcome with guilt that they cannot stomache breakfast. And their children. And their children's children. For two weeks.
Don't get me wrong, Windows 7 is mostly supreme, but whichever developers are responsible for this monster fly in my ointment ought to have their own HDDs covered in unnecessary 100 Mb partitions. (I don't like reinstalling OSes/programs/settings).