True. But Microsoft has become quite adept at limiting (i.e. crippling) features between the various versions of Windows; so I'm not sure it would work the same on all versions despite the fact that the underlying code may be identical. "Vee haf vays..." as the saying goes.
Well, playing around in vmware, I just found out how the Pro version is crippled compared to the Server version: XP Pro only supports striped volumes, you need a server edition to set up mirror or raid5- bollocks! After seeing this limitation, I do recall reading about it previously - and yeah, you can gain ability to create mirrors and parity volumes if you hack some system files, but I don't really feel like doing that.
The thing is, I have 2x74gig raptor drives in my system. On drive#1 I have a 16gig system partition for XP64 + apps, a 4gig partition for source code, data files, etc (all the "important stuff"), and a 50gig "dump" partition (for games). On drive#2, I have a single big 70gig "dump" partition for downloads, messing around with ISO files, etc.
Considering that the two "dump" partitions are expendable, I'd like to stripe them. Both for the additional speed, as well as consolidating the drive space to one volume (I've often had situations where I had something like three gigabytes left on both volumes, but needed a single volume with ~4.3gig free space for manipulating an ISO file). Since I was planning this stripe business, I though I might as well set up a mirror for OS and data partitions, to avoid having a ~20gig partition on drive#2 (stripes take two identical-sized partitions).
I guess a workaround would be resizing the system partition to 6 gigabytes, thus ended up with the following layout:
[copy or print
disk#1: system (6GB) | data (4GB) | stripe-part1 (60GB)
disk#2: system2 (10GB) | stripe-part2 (60GB)
Then I could mount "system2" as a junction - problem is, apart from the windows folder, system consumption is split up between "c:\dev" (visual studio, eclipse, MSDN, DDK, SDK, ...), "c:\usr" (portable apps, minor tools, various libraries and header files, etc), and program files. I don't really feel like consolidation everything under "program files" :/
Then again, I've been considering giving Vista a spin on my workstation, and that would allow me to use symlinks instead of simply junctions... I wonder how easy it is to move "program files" to another volume on a running instance of windows, though