Difference between revisions of "Dual boot with Windows"

From ArchWiki
Jump to: navigation, search
(Link to Grub2 instead of leaving out of date info here.)
(48 intermediate revisions by 28 users not shown)
Line 1: Line 1:
[[Category:Boot process (English)]]
+
[[Category:Boot process]]
[[Category:HOWTOs (English)]]
+
[[ru:Windows and Arch Dual Boot]]
 +
[[sk:Windows and Arch Dual Boot]]
 +
This is a simple article detailing different methods of Arch/Windows coexistence.
  
{{i18n_links_start}}
+
== Using Grub2 ==
{{i18n_entry|English|Windows_and_Arch_Dual_Boot}}
+
See [[Grub#Dual-booting]].
{{i18n_entry|Русский|Windows_and_Arch_Dual_Boot (russian)}}
+
{{i18n_links_end}}
+
  
== Windows and Arch Dual Booting: ==
+
==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.
  
To start off, you will need to install Windows.  The reason to start with windows, is because it will mess with the MBR (Master Boot Record) if it is installed after installing Arch.
+
===Using Windows 7/8 Boot-Loader===
You then boot up the arch installer. You pretty much do a standard installation, but there are a few things to keep in mind:
+
Excerpted from http://www.iceflatline.com/2009/09/how-to-dual-boot-windows-7-and-linux-using-bcdedit/
  
1. You will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.
+
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.
  
2. '''Very Important''', remember to note down your partitions numbers, for IDE drives it is: "hda1, hda2... hda8", SCSI drives: "sda1, sda2... sda8".  So note down which type of partitions belong to which partition number. For example:
+
*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]]}}
hda1: Windows (30GB is enough for some games)
+
+
hda2: /boot (100MB is plenty)
+
+
hda3: /root (about 8GB is good)
+
+
hda4: swap (between 512MB and 1024MB)
+
+
hda5: /home (use rest of hard drive)
+
  
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 (in 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 have to alter the config file that pops up (/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 simply uncommented if you follow above convention, this would place windows boot point at hd0,0 or sd0,0. 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
+
===Using Windows 2000/XP Bootloader===
title Windows XP
+
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.
rootnoverify (hd0,0)
+
chainloader +1
+
  
The parts of this entry break down as follows:
+
== See also ==
 
+
[https://bbs.archlinux.org/viewtopic.php?id=140049 Booting Windows from a desktop shortcut]
'''''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.
+
 
+
'''REMEMBER:''' The file is read from the top and down, so the system listed first, will be the one to auto boot, if no keys are pressed during the grub boot screen.
+
 
+
'''NOTE:'''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 = hda1 = hd0,0
+
First disk, second partition = hda2 = hd0,1
+
Second disk, first partition = hdb1 =hd1,0
+
 
+
More information on GRUB configuration can be found in [http://www.gnu.org/software/grub/manual/grub.html the GRUB manual].
+
 
+
==Other Layouts ==
+
1. Actually you could just use:
+
hda1 <-WinXP
+
+
hda2 <-swap
+
+
hda3 <-/root (Arch)
+
+
hda4 <-/home (optional)
+
 
+
and not use an extended(logical) partition (as /boot will be in the /root portion as well).
+
 
+
2. LVM (Linux Volume Management) is also a possibility to use, it works fine with arch, you 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 stuff, also allows you to easily resize any of them if it becomes necessary.
+
 
+
==Notes on /home ==
+
You may wish to not store you documents in this mountpoint, especially if you wish to share data between both Windows and Archlinux.  Traditionally this was done in 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).
+
 
+
==Other Options ==
+
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 the 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.

Using Grub2

See Grub#Dual-booting.

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

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

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.
    Note: For instance, my /boot partition is /dev/sda5. So I installed grub at /dev/sda5 instead of /dev/sda
    For help on doing this, see Grub#Install to Partition or Partitionless Disk
  • Under linux make a copy of the boot info by typing the following at the command shell:
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.”)
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}.
bcdedit /set {ID} device partition=c:
bcdedit /set {ID}  path \linux.bin
bcdedit /displayorder {ID} /addlast
bcdedit /timeout 30

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.

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 /boot partition, and this one is arguably more difficult to set up.

See also

Booting Windows from a desktop shortcut