It appears that Windows did not shut down cleanly the last time it was used." I followed the instructions : "To shut down Windows cleanly, go to System Preferences > Startup Disk and set Windows as the startup operating system. It processed for a few minutes and then the following error message appeared: "The Boot Camp partition is not prepared to run as a virtual machine. After entering my password and waiting while it said "VMware Fusion is preparing your Boot Camp partition to run as a virtual machine. I downloaded the trial Fusion (1.1.1) and selected the "Boot Camp Partition" to be my Virtual Machine. I get this impression from the fact that after Windows was installed, the Windows partition did not appear on the desktop (the GPT hadn't been updated accordingly yet), and Disk Utility also showed me the partition layout from the GPT, not from the MBR.The college IT guy just installed Boot Camp and XP professional on my office iMac (running Leopard). Once OS X is up, it seems to only look at the GPT infos, though. I am not 100% sure on this yet, though - it may well be that the boot loader can find a bootable OS X system also in the GUID partitions list even if the MBR has been modified for Windows booting. Therefore, the MBR may need to contain, apart from the Windows partition(s), an EFI and a HFS+ partition in case this drive should also boot into OS X. I have the impression that the Mac's boot loader (invoked by holding the Alt or Option key at startup) looks at the MBR, not the GPT, for bootable partitions. ![]() This raises the question of which overrules which, and what it means if both differ from each other. With the Windows install, the disk will have two separate partitioning schemes (with the GPT scheme rules being violated, because a GPT scheme shall only have one $EE type partition entry in block 0). I found that I also needed to update the boot code in block 0 sometimes, with the command " bootsect /nt60 c: /mbr" (the program can be found inside the Win7 Installer's Boot folder). Before this happens, Windows can't boot and will show messages such as "BOOTMGR is missing" or the error code 0xc000000e. ![]() enter: " \Windows\System32\bcdboot c:\Windows /s c:". This will open a command interface window, in which one can use the "bcdboot" command to update the BCD file to make the system bootable again (e.g. ![]() As the BCD contents become rather complex, the best way to get them updated when a bootable Windows volume is moved to a new disk is to start up from the Windows Installer DVD, press Shift-F10 as soon as the first dialog appears. That means that the BCD file can also refer to another volume that's becoming the actual startup volume. This will be used to boot (and decrypt) the main C: volume then. And if the volume is even encrypted, then there'll be another small (100MB) partition that becomes the active partition, containing a small NTFS volume with just the BCD file and a few other items. Since Vista, Windows seems to use a new, more complex, boot system, which records particulars about the volumes in a special Registry file (inside "\Boot\BCD", on the active partition).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |