Bootcamp on new ß4 installation

[lasombra666]

Hello guys and girls,

I just installed ß4 and didn't find a way to use my BootCamp partition with Windows XP SP2 installed and don't know where to start. Parallels works flawlessly.

I have a C2D MBP, 15", 2.16GHz, 2GB RAM and a 120GB HDD.

FDISK result:

Disk: /dev/rdisk0 geometry: 14593/255/63 \[234441648 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----

---

1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 201 49 \[ 409640 - 190840832] HFS+

*3: 0C 1023 27 51 - 1023 80 23 \[ 191512616 - 42928992] Win95 FAT32L

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Any help?

Thank you!

LaSombra

[admin]

So what happens when you tried? You installed Fusion, run it, and you don't see "Boot Camp partition" in the list of VMs in the VM library?

[lasombra666]

Magi, that's precisely it.

[admin]

Strange. Until beta 4, we didn't support FAT32 boot camp partitions, but they should work now. Does that partition contain a \BOOT.INI file?

[lasombra666]

Sure. I can boot Parallels and Boot Camp without any single problem.

[lasombra666]

I even unloaded fuse and ntfs extensions and nothing.

[lasombra666]

Another information.

The partition shows up on Windows and Disk Utility as NTFS, just fdisk shows it up as FAT32.

[incognegro]

Parallels, VMware Fusion and Bootcamp never all quite worked for me. VMware Fusion refused to load the boot camp partition, which is different from not being able to even see the partition. I think there is some conflict between Parallels and VMware, at least there was for me.

Try uninstalling Parallels, rebooting, and then loading up VMware Fusion to see whether anything changes ?

[incognegro · Accepted solution]

Another information.

The partition shows up on Windows and Disk Utility as

NTFS, just fdisk shows it up as FAT32.

Doesn't sound right. Sounds like your partition table has the wrong file system type.

Try doing (assuming your partition is #3):

sudo fdisk -e /dev/rdisk0

setpid 3

Choose 07 as the partition type

write

You may want to backup your partition if you aren't feeling very lucky ... or just dump it first using

sudo fdisk -d /dev/rdisk0 > ~/partition_table.dat

And you should be able to restore it from that if things don't go as planned.

[lasombra666]

IW-Note:~ root# fdisk /dev/rdisk0

Disk: /dev/rdisk0 geometry: 14593/255/63 \[234441648 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----

---

1: EE 0 0 2 - 25 127 14 \[ 1 - 409639] setpid 3

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----

---

*3: 0C 1023 27 51 - 1023 80 23 \[ 191512616 - 42928992] Win95 FAT32L

Partition id ('0' to disable) \[0 - FF]: (? for help) 07

fdisk:*1> write

Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? y

Writing MBR at offset 0.

fdisk: 1> exit

[lasombra666]

Hurray! It worked!

Thank you very much man!

[incognegro]

Hurray! It worked!

Thank you very much man!

Excellent news. You've saved me from being publicly humiliated on this forum by supplying a non-working answer

[dsch]

Thank you very much for providing this information. It helped me a lot.

[rockinsage]

Was having the same problem - this worked for me as well, thanks!