0
So, I guess I screwed up.
I have a RAID +0 array on 2x200gb SATA drives. I originally just had XP Pro 32 as my OS on it. I decided to dual boot with x64 pro and the original XP Pro 32. So, I used Partition Magic to resize my XP 32 partition and put x64 on a new partition, making the two partitions about equal in size.
Well, my XP 32 had to be reformatted, (long story), and while I was going about it I resized the 32 bit XP partition, making it 50gb or so and making a new, third partition in between it and the x64 partition. So, the RAID array now looks like this:
-----------------------------------------------------
32 bit XP |new non-bootable partition |x64 Pro
Anyhow, the 32 bit XP is working fine, the new non-bootable partition is formatted and fine, etc.
However, I noticed I no longer had the option of booting into x64 during boot up. (It just boots straight into 32 bit XP as if it's the only operating system). I checked the boot.ini file and there was no mention of a 2nd operating system. It just read like this:
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
So, what I thought I needed to do was add the x64 option to the boot.ini, so I added a line to make it look like this:
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Windows XP Professional x64 Edition" /noexecute=optin /fastdetect
After doing this, it does show the option to boot into x64 during boot up, but when I choose the option it gives me an error
"Windows could not start because the following file is missing or corrupt:<Windows root>\system32\hal.dll"
After using some of my uber-cyber-ninja-googling powers, I researched a bit and tried a few things. I tried to use the 32 bit XP disk to go into the recovery console and fix the MBR, fix the boot (FIXBOOT), and tried just about every command available in the console. Nothing worked.
I then tried the x64 bit CD and had the same amount of luck.
If I don't put the RAID drivers in while using the CDs it doesn't even see the hard drives. If I do put the RAID drivers in it seems to just skip the ability to use the recovery console and take me start to the partition screen where you can setup Windows.
Anyhow, this seems to be a common problem when screwing around with dual booting, so I thought someone might know a fix for it.
However, it's not the end of the world regardless, because I can just take what I need off the x64 partition and redo it, no harm no foul. I just wanted to see if anyone was familiar with the problem and knew a quick fix or anything.
For the record, the x64 install doesn't seem to have a boot.ini file anymore.
TIA, fellers.
On edit, I checked and the Hal.dll on the x64 bit partition is exactly where it should be "F:\WINDOWS\system32". Am I just not putting what I need to into the boot.ini?
Edited by eniparadoxgma, 13 January 2008 - 02:35 AM.
