Breast Cancer Teck Deck

GRUB multiboot

The aim of the project is to install on laptop three 64-bit operating systems: Windows 7
Pro x64, Mac OS X 10.6 and Ubuntu x64 10.10 where iATKOS v2 s3 guardian of Mac OS X. The handset is a
Fujitsu Siemens V3505 AmiloPRO with the following hardware:

• Intel Core 2 Duo T5500
• RAM 2 GB - DDR 2 160GB SATA HD
• VGA: Intel 950 IGP
• LAN Marvell
• WIFI Intel

The first attempt was to format the disk as specified GPT ;
Windows 7 supports GPT disks not only for primary (non-system). The disk is formatted
MBR and operating systems were installed in the order listed above.
A copy of the boot sector was carried out after each installation using the live version of Ubuntu running from USB stick (copied in the form of ISO along with GRUB2).
$ sudo dd if = / dev / sda of = / boot.bin bs = 512 count = 2
The second copy of the first kilobyte specification contains not only the MBR bootloader but also the partition table etc., if This suggests that if recovery through Forzatti dd, copy the entire industry would also involve changing the partition table!
The backup will be used later. The ends
last installation (Ubuntu) reports a start menu by the bootloader (GRUB ) that offers several choices including the loading of Windows, MacOSX, Ubuntu and more.
Windows and Ubuntu are chosen while running Mac OS X no.
The only way to start a new Snow Leopard is to further load the program contained in its boot sector.
The possibility is offered by the flexibility of GRUB that I'll never cease to praise. The boot sector
1K copied after installing Mac OS X preserved (asere.bin) I quote below the folder tree of linux / BOOT so that you can easily recover from GRUB.
The last step will be to instruct GRUB in order to launch the boot loader ASER as the following example:

menuentry "MAC OSX via ASER" {
insmod ext2 insmod part_msdos
September
root = '(hd0, msdos5)'
chainloader / boot / asere.bin

}
sequence ( chain loading ) if you choose Mac OS X:
BIOS -> GRUB -> ASERE.BIN -> MAC OS X

NB: Snow Leopard, due to problems of backwards compatibility hardware part only with the parameter boot-x .