This is a simple article detailing different methods of Arch/Windows coexistence.

This is a simple article detailing different methods of Arch/Windows coexistence.

−

==Windows and Arch Dual Booting==

+

== Using Grub2 ==

−

In this example, we will install Windows first, and subsequently install the GRUB bootloader along with Arch, allowing for dual boot.

+

See [[Grub#Dual-booting]].

−

Installation will be standard, but there are a few things to keep in mind:

+

==Using Windows boot-loader==

+

Another option is sort of the reverse of what is described at the beginning of this article where GRUB loads the Windows boot loader, which then loads Windows. Under this option, the Windows boot loader load GRUB, which then loads arch.

−

1. You may have to use logical partitions for some of our partitions, because there can only be up to 4 primary partitions per disk.

+

===Using Windows 7/8 Boot-Loader===

+

Excerpted from http://www.iceflatline.com/2009/09/how-to-dual-boot-windows-7-and-linux-using-bcdedit/

−

2. Remember to write down your partitions numbers: "sda1, sda2... sda8", noting which type of partitions belong to their relevant number. For example:

+

In order to have the Windows boot-loader see the linux partition, one of the linux partitions created needs to be FAT32 (in this case, /dev/sda3). The remainder of the setup is similar to a typical installation. Some documents state that the partition being loaded by the Win boot-loader must be a primary partition but I have used this without problem on an extended partition.

−

:; sda1 : Windows - 30GB should be enough. Many new games exceed 10GB each so bear this in mind.

+

*When installing the grub bootloader, install it on your '''/boot''' partition rather than the MBR. {{Note| For instance, my '''/boot''' partition is '''/dev/sda5'''. So I installed grub at '''/dev/sda5''' instead of '''/dev/sda''' <br> For help on doing this, see [[Grub#Install to Partition or Partitionless Disk]]}}

−

+

−

:; sda2 : /boot - 100MB is enough (optional)

+

−

+

−

:; sda3 : / - about 10GB is appropriate

+

−

+

−

:; sda4: swap - between 1024MB and 1512MB (optional)

+

−

+

−

:; sda5: /home - use rest of hard drive (optional)

+

−

It is important to note that there is a 1024 cylinder limit with some older BIOSs. This means that the BIOS cannot access things beyond the 1024th cylinder (about 8.5GB), so the /boot partition should be in the first 8.5GB (space before Windows partition). [http://gparted.sourceforge.net/livecd.php GParted LiveCD] or a partitioning tool in [http://www.sysresccd.org/Main_Page SystemRescueCd] are useful for moving and resizing partitions to accommodate this.

+

*Under linux make a copy of the boot info by typing the following at the command shell:

+

{{bc|1=

+

my_windows_part=/dev/sda3

+

my_boot_part=/dev/sda5

+

mkdir /media/win

+

mount $my_windows_part /media/win

+

dd if=$my_boot_part of=/media/win/linux.bin bs=512 count=1

+

}}

+

*Boot to windows and open up and you should be able to see the FAT32 partition. Copy the linux.bin file to C:\. Now run '''cmd''' with administrator privileges (navigate to Start->All Programs->Accessories, Right-click on Command Prompt and select “Run as administrator.”)

+

{{bc|

+

bcdedit /create /d “Linux” /application BOOTSECTOR

+

}}

+

*BCDEdit will return an alphanumeric identifier for this entry that I will refer to as {ID} in the remaining steps. You’ll need to replace {ID} by the actual returned identifier. An example of {ID} is {d7294d4e-9837-11de-99ac-f3f3a79e3e93}.

+

{{bc|1=

+

bcdedit /set {ID} device partition=c:

+

bcdedit /set {ID} path \linux.bin

+

bcdedit /displayorder {ID} /addlast

+

bcdedit /timeout 30

+

}}

−

3. When installing grub, you must configure /boot/grub/menu.lst), and make sure to install grub to /boot (or root (/) if you did not create a separate partition for /boot). There should be about three lines at the end of the file that speak about chainloading to boot other OSs, these can most generally be uncommented if you follow above convention, this would place windows boot point at hd0,0 or sda1. Thus you would have something akin to this:

+

Done! Reboot and enjoy. In my case I'm using the Win bootloader so that I can map my Dell Precision M4500's second power button to boot linux instead of windows.

−

# Windows XP

+

−

title Windows XP

+

−

rootnoverify (hd0,0)

+

−

chainloader +1

+

−

The parts of this entry break down as follows:

+

===Using Windows 2000/XP Bootloader===

+

For information on this method see http://www.geocities.com/epark/linux/grub-w2k-HOWTO.html. I do not believe there are any distinct advantages of this method over the Linux bootloader; you will still need a {{ic|/boot}} partition, and this one is arguably more difficult to set up.

−

:; title Windows XP : Can be anything you like, it will just be what is displayed in the grub bootup screen

:; rootnoverify (hd0,0) : Remember the partition numbers we wrote down, here you write in the partition number of your windows partition. This sets the windows boot at root, even though GRUB cannot read it.

+

−

+

−

:; chainloader +1 : What this does is call the Windows boot loader that is still in MBR in our case, since GRUB cannot boot Windows itself.

+

−

+

−

*The file is read from the top down, so the system listed first will be the one to auto boot, if no keys are pressed during the grub boot screen.

+

−

*GRUB uses a zero indexed system of numbering drives and partitions, which is a different convention than you may be used to seeing:

+

−

First disk, first partition=sda1=hd0,0

+

−

First disk, second partition=sda2=hd0,1

+

−

Second disk, first partition=sdb1=hd1,0

+

−

+

−

==Dual Booting from Multiple Hard Drives==

+

−

To dual boot from two separate hard drives (e.g., one dedicated Linux drive and one dedicated Windows drive) and Windows is not on the first hard drive, the Windows boot loader must be "tricked" into thinking Windows is on the first hard drive. Do this by adding the following lines to your menu.lst config file:

+

−

map (hd0) (hd1)

+

−

map (hd1) (hd0)

+

−

+

−

So the entry for Windows on second disk, first partition will look like this:

+

−

title Microsoft Windows XP Professional

+

−

root (hd1,0)

+

−

savedefault

+

−

makeactive

+

−

map (hd0) (hd1)

+

−

map (hd1) (hd0)

+

−

chainloader +1

+

−

+

−

More information on GRUB configuration can be found in [http://www.gnu.org/software/grub/manual/grub.html the GRUB manual].

+

−

+

−

==Other Layouts==

+

−

1. You could use:

+

−

:; sda1 : Windows XP

+

−

+

−

:; sda2 : swap

+

−

+

−

:; sda3 : root

+

−

+

−

:; sda4 : home

+

−

+

−

and not use an extended partition (as /boot will be in the / partition as well).

+

−

+

−

2. LVM (Linux Volume Management) is also a possibility to use. You could simply create a single LVM partition and let it create the other partitions inside it. This allows a single partition to hold all your needed GNU/Linux data, and allows to easily partitions when necessary.

+

−

+

−

==Notes on /home==

+

−

You may not wish to store you documents on this mountpoint, especially if you wish to share data between both Windows and Arch Linux. Historically, this was done on a FAT partition because writing to NTFS was still experimental. [http://www.ntfs-3g.org/ NTFS-3G] now offers stable writing to NTFS partitions, so you can just leave this as another partition that will be shared by both Windows and arch. Another option would be to use some of the tools in Windows, such as [http://www.fs-driver.org/ fs-driver] and use an ext3 or ext2 partition to store documents (fs-driver will mount ext3 partitions as ext2, so you will not be able to take advantage of journaling while in Windows).

+

−

+

−

==Using Windows boot-loader==

+

−

Another option is sort of the reverse of what is described at the beginning of this article where GRUB loads the Windows boot loader, which then loads Windows. Under this option, the Windows boot loader load GRUB, which then loads arch. For information on this method see http://www.geocities.com/epark/linux/grub-w2k-HOWTO.html. I do not believe there are any distinct advantages of this method over the previous one, you will still need a /boot partition, and this one is arguably more difficult to setup.

+

Revision as of 05:39, 16 April 2013

This is a simple article detailing different methods of Arch/Windows coexistence.

Contents

Using Grub2

Using Windows boot-loader

Another option is sort of the reverse of what is described at the beginning of this article where GRUB loads the Windows boot loader, which then loads Windows. Under this option, the Windows boot loader load GRUB, which then loads arch.

Using Windows 7/8 Boot-Loader

In order to have the Windows boot-loader see the linux partition, one of the linux partitions created needs to be FAT32 (in this case, /dev/sda3). The remainder of the setup is similar to a typical installation. Some documents state that the partition being loaded by the Win boot-loader must be a primary partition but I have used this without problem on an extended partition.

When installing the grub bootloader, install it on your /boot partition rather than the MBR.

Boot to windows and open up and you should be able to see the FAT32 partition. Copy the linux.bin file to C:\. Now run cmd with administrator privileges (navigate to Start->All Programs->Accessories, Right-click on Command Prompt and select “Run as administrator.”)

bcdedit /create /d “Linux” /application BOOTSECTOR

BCDEdit will return an alphanumeric identifier for this entry that I will refer to as {ID} in the remaining steps. You’ll need to replace {ID} by the actual returned identifier. An example of {ID} is {d7294d4e-9837-11de-99ac-f3f3a79e3e93}.