Quad booting

From OSx86
Jump to: navigation, search

Written by: Quand

NOTE: This guide is for quad booting on a single hard drive while installing wireless internet access on all platforms and basic networking to access windows network shares.


[edit] Preface

This guide is a comprehensive guide for Quad Booting (windowsXP, WindowsVista, OSX86, Linux) on a single hard drive with wireless internet access on all platforms and introducing basic networking on all platforms to access network shares on other computers. It took me a bit of time to figure out so I decided to write a guide for others who were interested in going this route. This guide is based on specific hardware and it is uncertain if the procedure will work on other hardware. If you are going to attempt quad boot I would strongly recommend installing the operating systems separately first, so you make sure they all work by themselves. Also, it is very helpful to have a usb flash drive handy and a separate computer running windows so you can download stuff as needed and put it on the flash drive. That being said, lets continue. . .

[edit] Requirements

[edit] Hardware Requirements

  • 1) PC with SSE2 instruction set
You can use SSE3 but I have no experience with it
  • 2) Empty Hard drive
I strongly recommend that you start with a clean hard drive, no files on it at all. Backup all your data on another drive and put it off to the side for now. I'm using IDE. It's unclear if SATA works (either on board or an add in card). It's also unclear how well RAID is supported. If you have any experience with SATA or RAID, please contribute to the guide!
  • 3) D-link DWL-G122 Rev B1 wireless USB adapter
I had an old linksys PCI wireless card and it just would not work with osx and Linux. However, I had great luck with the D-link usb adapter. It works under all platforms with minimal hassle. Normally they run about $50 but got mine on sale for $25. These adapters are plentiful as well so you can find them at compusa, best buy, fry's, etc. etc.

[edit] Software Requirements

This is a great live cd that is pretty much specific for partitioning. It works with or without an operating system installed, partitions your drive straight forward.
  • 2) Windows XP with Service Pack 2
NOTE: You should have SP2 or SP1 on the install CD, if you wish to install on to a hard drive larger than 137 GB (128 GiB). The original version of Windows XP does not support 48-bit LBA, and therefore suffers from the "137 GB limit". For more information on 48-bit LBA issues in Windows XP: [1]
  • 3) Windows Vista
  • 4) OSx86 10.4.8 install disc
I use 10.4.7 with the full patch upgrade to 10.4.8. If you're not a developer then you shouldn't proceed.....it being against the law and all. I've heard some rumor that there is a JaS release floating around.... (as well as an additional "ppf" patch to bring it up to date)
You can use any flavor you want, I've had decent luck with Suse since I'm not a Linux master and I want as much driver support as possible. I recommend the DVD-ISO for easiest install. Also, we will be installing GRUB as the boot loader of choice. This is again, due to ease and convenience. There are some problems with Vista's boot loader and the Darwin boot loader that I'm not going to get into, just take my word for it. For those using SuSE 10.2, the bootloader configuration is different so we shall use windows xp's bootloader. It is explained later in the tutorial.

There is some other software needed to get internet to work; I won't mention it now as it is not pertinent for a straight quad boot. . .

[edit] Partitioning

[edit] Partitioning Demystified

After going through this project, I learned a ton about partitioning. There are 3 types of partitions which are Primary, Logical, and Extended. Think of it broken up into two seperate groups. Primary partitions and then Logical/Extended. A primary partition is the partition tables way of saying create a partition with a certain amount of space and separate it from other drives physically. You can have a max of 4 primary partitions on a disc (3 if you are using 1 extended partition) From my experience, most operating systems work best when installed on a primary partition which is what we will be doing. Logical/Extended is the other half of the spectrum. It's the partition tables way of saying "hey, I'm not a physical partition but I'm going to trick the computer into thinking it's a partition via software. So you can create 1 extended partition and then inside the extended partition you can create logical partitions. That way, if you are like me you can have 8 + partitions on one hard drive. It will make more sense when you boot up GParted LiveCD.

[edit] Partitioning Comments (not from original author of this article)

NOTE: I am not the original author of this article, so I could be wrong

Without realizing it, the original author of this article made a number of assumptions/decisions that ensured that the entire process would work. Here I try to explain what some of these are.

Most operating systems may work best from a primary partition, but this doesn't seem to be an issue with Linux. You can see from the SUSE Guide on Grub that Linux is just placed in a logical partition, as is done in this quad-booting article.

As for Mac OSx86, I assume based on this that it also requires a primary partition.

This article assumes that your PC's BIOS is new enough that it supports the LBA necessary to overcome the BIOS 1024-cylinder limit as explained in this dual-booting guide. This article also relies on Linux's GRUB boot manager which supports LBA out-of-the-box. If your BIOS didn't support LBA or if you didn't use a LBA-enabled boot manager, you would have to create a /boot partition near the beginning of your disk, which means you would most likely waste a primary partition on Linux. If you waste a primary partition on Linux, you will only have 2 primary partitions left for your other OS's (remember that we need an extended, which is always also primary, partition to hold the logical partitions for Linux's swap and optionally Linux's root and other data). This would have resulted in a paltry triple-boot rather than the intended quad-boot :)

All these restrictions on primary partitions can probably be rendered moot by using an advanced boot manager such as Acronis Boot Manager; see the forums.

NOTE ON PARTITION TABLES: Having attempted to use this tutorial myself, I found one of the assumptions made is that your partition table is already set up. Knowing next to nothing about partitions in anything other than Windows, I didn't know that I needed to create/set any particular type of partition table. I had just bought 2 500gig disks for use as RAID-1. Through various trials and tribulations, I found I had to create a new partition table on the non-working disk, with "gpt" ( = GUID Partition Table!) as the type. You could probably use "mac" also. Note -- these two types do not allow extended/logical partitions, as they do not need them. You can create more than 4 primary partitions, unlike when using an "msdos" partition table. . .

[edit] Getting Started

1) Boot into the GParted CD.

You should have a bunch of unallocated space.

2) Create partitions in the following order:

1 NTFS Primary Partition, (for WinXP)
1 NTFS Primary Partition, (for Vista)
1 FAT32 Primary Partition, (for OSx86)
1 Extended Partition (with the rest of the unallocated space on the drive),

The rest of the partitions will be within the Extended Partition

1 ReiserFS Logical Partition (for Linux install)

Then the rest of your partitions as logical partitions. I have one for games, one for programs, one for video, etc.

[edit] Installing XP

Install Windows XP with Service Pack 2 to your first NTFS Primary Partition.

After installation it is imperative you do the following so Vista's bootloader isn't installed:

1) Boot into Gparted CD

2) Right click on your first Primary NTFS partition (with xp installed on it) and select "Manage Flags" from the menu. Check "hidden"

3) Right click on your second Primary NTFS partition (with vista installed on it) and select "Manage Flags" again from the menu. Check "boot"

4) Restart the computer with the Vista CD in the CDrom drive

[edit] Installing Vista

Install this to the second NTFS Primary Partition. Should be a straightforward install. Plop in the disc and let r' rip!

NOTE: If you install Vista after another OS without doing the above steps, Vista will automatically install it's new boot loader which is a pain! You do not want Vista's boot loader installed for this tutorial!

After it's installed do the following:

1) Boot the Gparted CD again

2) Right click on your second NTFS Primary Partition and click on "manage flags". Uncheck "boot"

3) Right click on your first NTFS Primary Partition and click on "manage flags". Uncheck "hidden"

[edit] Installing OSx86

Plop in your OSx86 DVD and load it up. You will install this to the FAT32 Primary Partition. Once you are at the first install prompt follow these directions:

1) Go to Utilities > Disk Utility

2) Select your partition that you want to be OSX and go to the Erase tab

3) For Volume Format, select Mac OS Extended (Journaled)

4) Click Erase. Now the partition should not be grey, it should be black to indicate that it is active.

5) Close out of the Disk Utility and move onwards with installation.

After installation, your computer will automatically boot into OSx or you will get a "HFS+ Partition Error"

NOTE: After installation you might receive a "HFS+ Partition Error". I'm not 100% sure why this happens sometimes and why other times it doesn't appear at all. Regardless, you should be able to move ahead with the next steps and get everything to work. Don't worry if you see this error.

[edit] Configuring The Boot loader

Congrats if you've made it this far! So now you have Grub installed. If you're not familiar with grub it is a boot loader that comes with Suse. There are excellent in depth guides on it via the web, so I will not be going over specifics. When grub loads you should see Suse 10.1, windows 1, windows 2, failsafe and Suse 10.1 (safe mode). What you should do at this point is test the Suse 10.1 loads, and both windows loads to ensure they work and you boot up to the correct system.

[edit] Adding OSx86 to the GRUB menu

To add OSx86 to the GRUB menu do this:

1) Copy the folder "i386" from the OSx cd (which is located at /usr/standalone/i386)and put it in /boot/grub/ The i386 folder is hidden normally so ensure you can see all hidden files in whatever operating system you are currently in. What I did is copied the files over in windows to a flash drive and then copied them from the flash drive to my home space and then used the following command in the terminal: cp -r /home/i386 /boot/grub/i386

2) Go To Applications > System > YaST

3) Go To "System" and select "Boot Loader"

4) Click "Add"

5) Select "Other System (Chainloader)"

6) Type in OSx86 for your Section Name and for Device select browse.

7) Browse to where you saved your i386 folder and select the chain0 file. This means you should have /boot/grub/i386/chain0 in the field where it says device

8) Click OK and you're done.

NOTE: If you try editing the menu.list file straight, it will not show OSx as a choice. You must initially use Yast in order to get the option to show in GRUB then if you desire you can edit it manually. .

[edit] Adding OSx86 to the GRUB menu Ubuntu(not the original author)

Hi I was working my way through this "how to", but i was not using Suse, so I could not find any YaST! But it in the end it was easy anyway: I just added these following lines to the /boot/grub/menu.lst

title Mac OS X

rootnoverify (hd0,2)


chainloader +1

There was no need of copying any chain0 file or a specific folder somewhere. It just worked fine. But at the line "rootnoverify (hd0,2)" you have to replace the "(hd0,2)" with the location of your primary Mac OS X partition. Hope it helps somebody else who is not using Suse. I also did a complete reinstall of the OS X on the Mac OS X partition and gub still worked after reinstaling Mac OS X. . . . . . .

[edit] Adding OSx86 to the Windows XP bootloader (for those having trouble with grub)

Adding OSx86 to the boot loader is an easy task. The instuctions below may seem long but the process is basically adding chain0 to boot.ini and that's it. Whilst grub is more powerful, the extra features are not needed so XP's boot loader will do just fine.

1)Boot Windows XP

2)After Login, Insert the Mac OS X86 DVD and Copy chain0 to the root of the C: drive. You should then have the file C:\chain0. (Chain0 is found on the Mac CD in /user/standalone/i386 but Windows can't read Mac formatted Discs. It seems that this folder is formatted differently so you might find chain0 in the root of the DVD. If you can't find it, download the Mac OS X darwin 10.4 x86 binaries and copy /user/standalone/i386/chain0 from this. The darwin CD is found here: http://www.opensource.apple.com/darwinsource/)

3)In the explorer window, go to the "tools" menu and select folder options. Under the "View" tab, check "Show hidden files and folders" and deselect "Hide protected operating system files".

4)In the root of the C:\ drive, you should now be able to see boot.ini. Right click this file and click "Properties". In the window that appears, uncheck "Read Only".

5)Double click boot.ini so it opens in notepad (or some other text editor)

6)On the last line of boot.ini, add C:\chain0="OSx86"

[edit] Aquiring wireless internet in OSx86

Getting internet to work in OSx86 is pretty easy with the D-link DWL-G122 Rev B1 wireless USB adapter.

1) Download drivers from [2]

2) Install and restart computer.

3) When you plug in the adapter, the RaLink utility will pop up automatically. You'll have to wait a minute or two, but you should have internet. If for any reason you don't have internet, try unplugging the USB adapter and plugging it back in.

[edit] acquiring wireless internet in Linux

I could not for the life of me get the Ralink drivers to work properly. So I used NdisWrapper. If your not familiar with NdisWrapper, it is a software package that "wraps" around your windows wireless driver so it makes the driver believe it's in windows. It will suffice.

1) Select Applications > System > YaST

2) Click Software > Software Management

3) Type in "ndis" in the search field

4) Select ndiswrapper and all of it's counterparts and install

Now you need to locate and install the Windows-based drivers for your device. There are two files that you will need to find. One is an *.inf file that basically tells your machine how to setup the driver and the other is the actual driver itself which has a *.sys extension.

5) Locate your *.inf and *.sys driver files on your wireless adapter driver disc.

6) In a terminal window browse to where you copied the two files. Then type in the following:

ndiswrapper -i <drivername>.inf 

Where <drivername> is go figure, the name of your driver.

7) To ensure it installed correctly type:

ndiswrapper -l

It should say "driver installed"

8) Next load NdisWrapper by typing:

modprobe ndiswrapper

9) Check to make sure the driver is loaded properly by typing:


If you were successful, you will see an entry in wlan0 detailing wireless information

10) Go To Applications > System > Yast

11) Select Network Devices > Network Card

12) Select User Controlled with network manager

13) Click "Add"

14) For Device Type select "Wireless" and for Configuration Name type "0"

15) Click next, next again, and enter in your network information (SSID, encryption key, etc.)

16) We need to make sure NdisWrapper loads every time Suse loads, so go to Applications > System > YaST > System > /etc/sysconfig Editor

17) Go To System > Kernel > MODULES_LOADED_ON_BOOT

18) Type in:


[edit] Mounting a Windows Network Share in OSx86

From The Finder click Go->Connect To Server

Type in smb://<name or ip of the server>/<optional share name>

You can also click Browse and use the finder to try to find your server. This will only show servers within the same workgroup though...

[edit] Mounting a Windows Network Share in Linux

This section is geared towards people who have another computer with a network share.

1) Make a directory for the mountpoint by typing in the terminal:

mkdir /mnt/<name-of-mount-point>

2) Mount the share by typing in the terminal:

mount -t smbfs -o username=<username>,password=<password> //<win-box>/<share> /mnt/<name-of-mountpoint>

If you want to share a folder on your Linux computer with a windows computer, install Samba and edit your smb.conf. Many graphically oriented Linux distributions provide a GUI for this, but this would be distribution dependent. I believe gnome-system-tools provides a nice interface, as well as kde's kcontrol application.

In KDE open Konqueror type into the address bar:

smb://<name or ip of the server>/<optional share name>

There are also ways to connect via Gnome, other GUIs as well as the terminal

[edit] Conclusion

After heavy experimentation I have concluded that this is the best/easiest way to get a quad boot working. I've tried different partitioning methods and different orders of OS installs (putting Vista first, putting Linux first or in the middle, etc.) and nothing has worked well except for this method. Feel free to experiment though if you are brave.

After successfully quad booting with one hard drive you can get a bit more advanced and add a 2nd hard drive as a slave in your ide cable. If you do this after the installs you will break GRUB and will need to put in the Suse DVD and try to repair the boot loader or get to a command line where you can access the boot loader.

Why in the world would anyone want to Quad Boot? I have no freaking clue unless you are crazy! That or you are thirsty for knowledge and desire full command over the three main operating systems while having very limited resources.

If you are having ANY problems at all, please feel free to contact me and I will try to help in any way possible. [email protected] . . .

This page was last modified on 7 August 2013, at 10:37.
This page has been accessed 249,822 times.
Powered by MediaWiki © 2021 OSx86 Project  |   InsanelyMac  |   Forum  |   OSx86 Wiki   |   Privacy policy   |   About OSx86   |   Disclaimers