Hi!
I've recently bought a MacBook Pro with the 160GB/5400RPM hard disk upgrade. Soon after I got it (two weeks ago), I installed Boot Camp, used the assistant to repartition my disk and, albeit some minor problems, I was able to dualboot OS X and Win XP Pro.
However, as the disk is damn slow, I want to reorganize it to keep the system files in faster areas of the disk and prevent "fragmentation" due to my hard disk usage patterns (tens of thousands of tiny files). So I booted OS X installation, wiped out the full disk and created three partitions:
- 30GB HFS+ for Mac OS X's root.
- 30GB FAT32 for Win XP Pro.
- The rest for Mac OS X's /Users directory, also HFS+.
Then I went throught the OS X setup and, when finished, I tried to install Windows. I put the CD in, booted from it, and the installation started. It properly detected the C: partition, which it formatted as FAT32 and proceeded to the initial file copy. But soon after the first reboot (when the installer boots from the files copied to disk to enter the graphical installer), Windows failed.
As soon as I select Windows from the original Mac boot loader, it says that %WindowsRoot%/system32/hal.dll is missing (even before it shows the logo). Googling a bit, it turns out that this problem is probably caused by a broken boot.ini. As I had used FAT32 for Windows, I was able to mess with this file from OS X. It originally had the following entry:
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
And OS X's fdisk reports:
Disk: /dev/rdisk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>
2: AF 25 127 15 - 1023 110 1 [ 409640 - 62652416] HFS+
*3: 07 1023 191 3 - 1023 254 53 [ 63324200 - 62914560] HPFS/QNX/AUX
4: AF 1023 254 54 - 1023 254 22 [ 126238760 - 186080864] HFS+
(Well, this does not match the real output because partition 3 should be FAT32. But this is the last installation attempt I made, using NTFS. Same problem though.)
Note that boot.ini says partition(3) and fdisk says Windows' partition is the 3rd one, so it looks correct. Well, being convinced that the problem was there, I tried different values for partition(x) in boot.ini; and it turns out that by using partition(2) it worked "fine".
But not really. The installation proceeded by showing the Windows logo and seemed to boot fine, but, soon after, it crashed with a blue screen and the UNMOUNTABLE_BOOT_VOLUME error.
I have already lost a full day trying to get this to work, and I don't know what else to try. (Of course I'd go back to the original setup, but I'd not rather to if at all possible.) BTW, I've also installed rEFIt, but no luck with it either.
To me, it *seems* as if the Windows' initial boot loader (the one that uses BIOS services, I think) saw something on disk but later on, when it uses its own drivers, it sees something different. As I am almost EFI/GPT clueless this deduction seems plausible to me, but might be completely wrong.
Now I've just found some "weird" values in "nvram -p"; e.g. the BootCampHD variable. Should those have some special value?
Oh, and something else I tried: I manually modified the MBR and changed the first partition type from 0xEE to 0xEF. That is obviously wrong and in fact it broke my OS X system (to the point where I was unable to restore it without a full reinstall), but, for some strange reason, XP was able to finish its installation procedure.
Any clue? Has anybody been successful at installing a Windows system with manual partitioning rather than the one made by BootCamp?
Thank you.
I've recently bought a MacBook Pro with the 160GB/5400RPM hard disk upgrade. Soon after I got it (two weeks ago), I installed Boot Camp, used the assistant to repartition my disk and, albeit some minor problems, I was able to dualboot OS X and Win XP Pro.
However, as the disk is damn slow, I want to reorganize it to keep the system files in faster areas of the disk and prevent "fragmentation" due to my hard disk usage patterns (tens of thousands of tiny files). So I booted OS X installation, wiped out the full disk and created three partitions:
- 30GB HFS+ for Mac OS X's root.
- 30GB FAT32 for Win XP Pro.
- The rest for Mac OS X's /Users directory, also HFS+.
Then I went throught the OS X setup and, when finished, I tried to install Windows. I put the CD in, booted from it, and the installation started. It properly detected the C: partition, which it formatted as FAT32 and proceeded to the initial file copy. But soon after the first reboot (when the installer boots from the files copied to disk to enter the graphical installer), Windows failed.
As soon as I select Windows from the original Mac boot loader, it says that %WindowsRoot%/system32/hal.dll is missing (even before it shows the logo). Googling a bit, it turns out that this problem is probably caused by a broken boot.ini. As I had used FAT32 for Windows, I was able to mess with this file from OS X. It originally had the following entry:
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
And OS X's fdisk reports:
Disk: /dev/rdisk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>
2: AF 25 127 15 - 1023 110 1 [ 409640 - 62652416] HFS+
*3: 07 1023 191 3 - 1023 254 53 [ 63324200 - 62914560] HPFS/QNX/AUX
4: AF 1023 254 54 - 1023 254 22 [ 126238760 - 186080864] HFS+
(Well, this does not match the real output because partition 3 should be FAT32. But this is the last installation attempt I made, using NTFS. Same problem though.)
Note that boot.ini says partition(3) and fdisk says Windows' partition is the 3rd one, so it looks correct. Well, being convinced that the problem was there, I tried different values for partition(x) in boot.ini; and it turns out that by using partition(2) it worked "fine".
But not really. The installation proceeded by showing the Windows logo and seemed to boot fine, but, soon after, it crashed with a blue screen and the UNMOUNTABLE_BOOT_VOLUME error.
I have already lost a full day trying to get this to work, and I don't know what else to try. (Of course I'd go back to the original setup, but I'd not rather to if at all possible.) BTW, I've also installed rEFIt, but no luck with it either.
To me, it *seems* as if the Windows' initial boot loader (the one that uses BIOS services, I think) saw something on disk but later on, when it uses its own drivers, it sees something different. As I am almost EFI/GPT clueless this deduction seems plausible to me, but might be completely wrong.
Now I've just found some "weird" values in "nvram -p"; e.g. the BootCampHD variable. Should those have some special value?
Oh, and something else I tried: I manually modified the MBR and changed the first partition type from 0xEE to 0xEF. That is obviously wrong and in fact it broke my OS X system (to the point where I was unable to restore it without a full reinstall), but, for some strange reason, XP was able to finish its installation procedure.
Any clue? Has anybody been successful at installing a Windows system with manual partitioning rather than the one made by BootCamp?
Thank you.