VMware Communities
robegian
Contributor
Contributor

Accessing a BootCamp partition of a second drive with Fusion 5

Hi all,

I have a MacBook Pro 2008 (4,1) and recently I installed a Samsung 840 SSD in the SATA bay, moving the old 500GB hard drive to the PATA bay (thanks to an Opticaddy adapter), where the SuperDrive used to be (see picture below).

The moved hard drive has two partitions: an HFS+ (journaled, now empty) and a working BootCamp partition with Windows XP Pro.

I'm trying to use that BootCamp partition with Fusion 5, with no avail. Previously, when the hard drive was the primary drive (in the SATA bay), I was regularly using it with Fusion 4.

I searched the forum but I didn't find the solution to this problem. I tried the procedure explained here, but it didn't work:

http://communities.vmware.com/thread/337466

Looks like I need some help: is there anyone succesfully using a BootCamp partition on a second drive?

Thanks in advance,

Roberto

IMG_0950-1.jpg

0 Kudos
3 Replies
witchbutter303
Contributor
Contributor

Can you post the vmx file that the bootcamp setup creates?  It may be as simple as changing a relative path.

0 Kudos
robegian
Contributor
Contributor

Thanks for replying.

I'm attaching the requested file — that, and the vmdk.

0 Kudos
robegian
Contributor
Contributor

In the meantime I deleted all files in the Virtual Machines folder, let Fusion regenerate them, and the problem was nailed down to this error message, which showed whenever I tried to use that Windows partition, both in Fusion and by a «standard» boot:

Windows could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and disk hardware.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

So I read this page:

http://support.microsoft.com/kb/314477/en-us

And I opened the boot.in file, the content of which was:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(4)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

I noticed that partition(4) parameter, although on the disk there are only 3 partitions (picture below), so I replaced it with partition(3) — and it worked: finally Windows boots regularly in Fusion.

http://www.giannotta.eu/photolink/ssd/MBPPartitions.png

Now I really don't know what changed that parameter to (4) and why. I didn't for sure!

0 Kudos