So, I played with it. Noticed that as MD2 was installing, it created a 1.4GB NTFS partition at the end of the HDD. It assigns it the drive letter X: as it's copying the files over. You can inspect the files while it's copying: http://www.hkss.com/temp/pics/md2-reinstall.gif
After it's done installing, it removes the drive letter and renders the partition as unreadable by Windows afterwards. You can't even assign it a drive letter later. See here: http://www.hkss.com/temp/pics/md2-reinstall2.gif
. I also noticed that if you don't exit out of the partition by the time MD2 is done copying the files over, it MAY have corrupted something to prevent you from booting into MD2 using the MD key. Am not sure if that's what caused it. Re-installing MD2 from within Windows XP fixed the issue.
Looked at the boot.ini file of the MD2 partition, and here's the content:
multi(0)disk(0)rdisk(0)partition(2)\\WINDOWS="Microsoft Windows XP Embedded" /fastdetect /KERNEL=NTOSBOOT.EXE /maxmem=256
Strange thing is, Partition 2 would indicate that it's the 2nd partition on the drive. On my hard drive, I have the following partitions (again, see here: See here: http://www.hkss.com/temp/pics/md2-reinstall2.gif
Partition 1: C: (WXP Pro)
Partition 2: D: (Data drive)
Partition ?: Dell's MD2
So, I modified C:\\boot.ini to add the following entry to the [Operating Systems] section:
|multi(0)disk(0)rdisk(0)partition(4)\\WINDOWS="Microsoft Windows XP Embedded" /fastdetect /KERNEL=NTOSBOOT.EXE /maxmem=256
I figured that Partion 4 would be MD2.
Upon booting up, it reports that HAL.DLL is missing. You can Google that around for some suggested fixes, but I didn't bother.
Changed the above code to use Partition 3 instead (I figured that "Unpartitioned space" would not be counted as a partition.) That didn't work at all. Windows reported a totally different error. So, yes, "Unpartitioned space" *IS* counted as a partition number (in my case, Partition #3).
So, I leave the rest for you guys to figure out if you have the time (I currently don't.) An idea I have is to do something that Windows 2000 (boot.ini) did with Windows 98 dual boots: boot.ini instructed the computer to load Windows 98's boot record (bootsect.dos) when the entry is selected. This will make more sense if you understand how W98 or MS-DOS boot up:
PC turns on -> MBR -> looks for IO.SYS -> MSDOS.SYS -> COMMAND.COM
Boot.ini in Windows 2000 (probably the same in WXP) does something like this:
multi(0)disk(0)rdisk(0)partition(1)\\WINDOWS="Microsoft Windows XP Professional" /fastdetect
I don't remember what the exact entry is for the ?????... It's been a while since I've used W98 as the primary gaming OS
So, again, in the above scenario, it appears that Windows 2000 booted up with boot.ini and when you made the W98 selection, it'd pass it on to the W98 boot process. I think it did that by copying the original MBR (that called up W98) as bootsect.dos, which then continues to W98 as normal (bootsect.dos -> io.sys -> msdos.sys -> command.com)
If that is true, does somebody know then how to modify boot.ini to pass control over to the boot sector (like W98's bootsect.dos file) that's located on the MD2 partition? In Linux lingo, that would be considered "chain loading". I don't think boot.ini can do chain loading. A 3rd party alternative (ie. Linux's LILO or GRUB) could, in theory, make the MD2 partition available for any laptop/PC that don't have the MediaDirect button.
I hope this explanation makes sense.