treble boot with snow windows7 and leo on guid partition

[robi62]

Incredible but true I managed to get the three os running on a guid partion I thought that windows7 would not as I have beeen reading but I managed it.

 

I created 3 partitions on my hdd in guid on my aspire one d250

 

1st one snow 2nd windows 3rd leo.

 

I installed my 2 osx os first then I put windows7 dvd in and it booted up and found my disk I format my partiton in ntfs then installed windows .Of course windows partition was in fat.

 

Of course I could only boot with windows so on a usb stick installed chameleon 2 boot loader.

 

Managed to boot in my leo partition then with osx86 tools not the latest build I run efi and installed chameleon to my leo partition then reinstalled chameleon 2 rc1 standard on my leo partition and that is is when I boot up I can choose which of my 3 os I want to go into.

 

 

here is a photo to show you

[srs5694]

A little Googling suggests that the Aspire One D250 has an EFI rather than a BIOS, although I have no way of positively verifying this. Windows 7 will (reportedly) boot from a GPT disk when a computer has an EFI. It will not do so on a stock BIOS-based computer. Very few computers today have EFI firmware; most still ship with a legacy BIOS. This is slowly changing.

 

It's also conceivable that you're running a hybrid MBR configuration and don't realize it. From Linux, type (as root) "fdisk -l /dev/sda" to figure this out. A pure GPT configuration will show just one partition, of type 0xEE, spanning the entire disk, as in:

 

$ sudo fdisk -l /dev/sda

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

  Device Boot	  Start		 End	  Blocks   Id  System
/dev/sda1			   1	   60802   488386583+  ee  EFI GPT

 

A disk with a hybrid MBR configuration will show multiple partitions, only one of which will be of type 0xEE. There are other ways to make this identification, such as with the OS X fdisk utility. (My OS X systems are shut down at the moment, so I can't present an example.)