https://wiki.archlinux.org/api.php?action=feedcontributions&user=Kbutcher5&feedformat=atomArchWiki - User contributions [en]2018-12-19T10:21:37ZUser contributionsMediaWiki 1.31.1https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=327371Dual boot with Windows2014-07-28T16:16:19Z<p>Kbutcher5: /* See also */</p>
<hr />
<div>[[Category:Boot process]]<br />
[[Category:Getting and installing Arch]]<br />
[[ja:Windows and Arch Dual Boot]]<br />
[[ru:Windows and Arch Dual Boot]]<br />
[[sk:Windows and Arch Dual Boot]]<br />
[[zh-cn:Windows and Arch Dual Boot]]<br />
This is a simple article detailing different methods of Arch/Windows coexistence.<br />
<br />
== Important information ==<br />
<br />
=== Windows UEFI vs BIOS limitations ===<br />
<br />
Microsoft imposes limitations on which firmware boot mode and partitioning style can be supported based on the version of Windows used:<br />
<br />
* '''Windows XP''' both '''x86 32-bit''' and '''x86_64''' (also called x64) (RTM and all Service Packs) versions do not support booting in UEFI mode (IA32 or x86_64) from any disk (MBR or GPT) OR in BIOS mode from GPT disk. They support only BIOS boot and only from MBR/msdos disk.<br />
* '''Windows Vista''' or '''7''' '''x86 32-bit''' (RTM and all Service Packs) versions support booting in BIOS mode from MBR/msdos disks only, not from GPT disks. They do not support x86_64 UEFI or IA32 (x86 32-bit) UEFI boot. They support only BIOS boot and only from MBR/msdos disk.<br />
* '''Windows Vista RTM x86_64''' (only RTM) version support booting in BIOS mode from MBR/msdos disks only, not from GPT disks. It does not support x86_64 UEFI or IA32 (x86 32-bit) UEFI boot. It supports only BIOS boot and only from MBR/msdos disk.<br />
* '''Windows Vista''' (SP1 and above, not RTM) and '''Windows 7''' '''x86_64''' versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 (x86 32-bit) UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.<br />
* '''Windows 8/8.1 x86 32-bit''' support booting in IA32 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support x86_64 UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk. On market, the only systems known to ship with IA32 (U)EFI are some old Intel Macs (pre-2010 models?) and Intel Atom System-on-Chip (Clover trail and Bay Trail) Windows Tablets. in which it boots ONLY in IA32 UEFI mode and ONLY from GPT disk.<br />
* '''Windows 8/8.1''' '''x86_64''' versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 UEFI boot, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.<br />
<br />
In case of pre-installed Systems:<br />
<br />
* All systems pre-installed with Windows XP, Vista or 7 32-bit, irrespective of Service Pack level, bitness, edition (SKU)or presence of UEFI support in firmware, boot in BIOS-MBR mode by default.<br />
* MOST of the systems pre-installed with Windows 7 x86_64, irrespective of Service Pack level, bitness or edition (SKU), boot in BIOS-MBR mode by default. Very few recent systems pre-installed with Windows 7 are known to boot in x86_64 UEFI-GPT mode by default.<br />
* ALL systems pre-installed with Windows 8/8.1 boot in UEFI-GPT mode. The firmware bitness matches the bitness of Windows, ie. x86_64 Windows 8/8.1 boot in x86_64 UEFI mode and 32-bit Windows 8/8.1 boot in IA32 UEFI mode.<br />
<br />
The best way to detect the boot mode of Windows is to do the following (info from [http://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-legacy-mode.html here]):<br />
<br />
* Boot into Windows<br />
* Press Win key and 'R' to start the Run dialog<br />
* In the Run dialog type &quot;msinfo32&quot; and press Enter<br />
* In the '''System Information''' windows, select '''System Summary''' on the left and check the value of '''BIOS mode''' item on the right<br />
* If the value is '''UEFI''', Windows boots in UEFI-GPT mode. If the value is '''Legacy''', Windows boots in BIOS-MBR mode.<br />
<br />
In general, Windows forces type of partitioning depending on the firmware mode used, i.e. if Windows is booted in UEFI mode, it can be installed only to a GPT disk. If the Windows is booted in Legacy BIOS mode, it can be installed only to a MBR (also called '''msdos''' style partitioning) disk. This is a limitation enforced by Windows installer, and as of April 2014 there is no officially (Microsoft) supported way of installing Windows in UEFI-MBR or BIOS-GPT configuration Thus Windows only supports either UEFI-GPT boot or BIOS-MBR configuration.<br />
<br />
Such a limitation is not enforced by the Linux kernel, but can depend on which bootloader is used and/or how the bootloader is configured. The Windows limitation should be considered if the user wishes to boot Windows and Linux from the same disk, since installation procedure of bootloader depends on the firmware type and disk partitioning configuration. In case where Windows and Linux dual boot from the same disk, it is advisable to follow the method used by Windows, ie. either go for UEFI-GPT boot or BIOS-MBR boot. See http://support.microsoft.com/kb/2581408 for more info.<br />
<br />
=== Install media limitations ===<br />
<br />
Intel Atom System-on-Chip Tablets (Clover trail and Bay Trail) provide only IA32 UEFI firmware WITHOUT Legacy BIOS (CSM) support (unlike most of the x86_64 UEFI systems), due to Microsoft Connected Standby Guidelines for OEMs. Due to lack of Legacy BIOS support in these systems, and the lack of 32-bit UEFI boot in Arch Official Install ISO or the Archboot iso (as of April 2014), these install media cannot boot in Atom SoC tablets pre-installed with Windows 8/8.1 32-bit.<br />
<br />
=== Bootloader UEFI vs BIOS limitations ===<br />
<br />
Most of the linux bootloaders installed for one firmware type cannot launch or chainload bootloaders of other firmware type. That is, if Arch is installed in UEFI-GPT or UEFI-MBR mode in one disk and Windows is installed in BIOS-MBR mode in another disk, the UEFI bootloader used by Arch cannot chainload the BIOS installed Windows in the other disk. Similarly if Arch is installed in BIOS-MBR or BIOS-GPT mode in one disk and Windows is installed in UEFI-GPT in another disk , the BIOS bootloader used by Arch cannot chainload UEFI installed Windows in the other disk. <br />
<br />
The only exceptions to this are grub(2) in Apple Macs in which EFI installed grub(2) can boot BIOS installed OS via '''appleloader''' command (does not work in non-Apple systems), and rEFInd which technically supports booting legacy BIOS OS from UEFI systems, but [http://rodsbooks.com/refind/using.html#legacy does not always work in non-Apple UEFI systems] as per its author Rod Smith. <br />
<br />
However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk, then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk. <br />
<br />
{{Note|If Arch and Windows are dual-booting from same disk, then Arch SHOULD follow the same firmware boot mode and partitioning combination used by the installed Windows in the disk.}}<br />
<br />
=== UEFI Secure Boot ===<br />
<br />
All pre-installed Windows 8/8.1 systems by default boot in UEFI-GPT mode and have UEFI Secure Boot enabled by default (which can be manually disabled by the user) and Legacy BIOS support (CSM) disabled by default (which can be manually enabled by the user, if the firmware supports it) in the firmware. This is mandated by Microsoft for all OEM pre-installed systems.<br />
<br />
Arch Linux install media currently supports Secure Boot but it requires some manual steps by the user to [[UEFI#Secure_Boot|setup the HashTool while booting]]. There it is advisable to disable UEFI Secure Boot in the firmware setup before attempting to boot Arch Linux. Windows 8/8.1 SHOULD continue to boot fine even if Secure boot is disabled. <br />
<br />
The only issue with regards to disabling UEFI Secure Boot support is that it requires physical access to the system to disable secure boot option in the firmware setup, as Microsoft has explicitly forbidden presence of any method to remotely or programmatically (from within OS) disable secure boot in all Windows 8/8.1 pre-installed systems<br />
<br />
=== Fast Start-Up ===<br />
<br />
Fast Start-Up is a feature in Windows 8 that hibernates the computer rather than actually shutting it down to speed up boot times. Your system can lose data if Windows hibernates and you dual boot into another OS and make changes to files. Even if you don't intend to share filesystems, the EFI System Partition is likely to be damaged on an EFI system. Therefore, you should disable Fast Startup, as described [http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html here], before you install Linux on any computer that uses Windows 8.<br />
<br />
{{Pkg|ntfs-3g}} added a [http://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/559270a8f67c77a7ce51246c23d2b2837bcff0c9/ safe-guard] to prevent read-write mounting of hibernated disks, but the NTFS driver within the Linux kernel has no such safeguard.<br />
<br />
=== Windows filenames limitations ===<br />
<br />
Windows is limited to filepaths being shorter than [http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx 260 characters].<br />
<br />
Windows also puts [http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#naming_conventions certain characters off limits] in filenames for reasons that run all the way back to DOS:<br />
<br />
* &lt; (less than)<br />
* &gt; (greater than)<br />
* : (colon)<br />
* &quot; (double quote)<br />
* / (forward slash)<br />
* \ (backslash)<br />
* | (vertical bar or pipe)<br />
* ? (question mark)<br />
* * (asterisk)<br />
<br />
These are limitations of Windows and not NTFS: any other OS using the NTFS partition will be fine. Windows will fail to detect these files and running {{ic|chkdsk}} will most likely cause them to be deleted. This can lead to potential data-loss.<br />
<br />
'''NTFS-3G''' applies Windows restrictions to new file names through the [http://www.tuxera.com/community/ntfs-3g-manual/#4 windows_filenames] option (see [[fstab]]).<br />
<br />
== Installation ==<br />
<br />
The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched. The Windows installation will create the EFI System Partition which can be used by your Linux bootloader.<br />
<br />
=== BIOS systems ===<br />
<br />
==== Using a Linux boot loader ====<br />
<br />
You may use [[GRUB#Dual-booting|GRUB]] or [[Syslinux#Chainloading|Syslinux]].<br />
<br />
==== Using Windows boot loader ====<br />
<br />
With this setup the Windows bootloader loads GRUB which then boots Arch. <br />
<br />
===== Windows Vista/7/8/8.1 boot loader =====<br />
<br />
The following section contains excerpts from http://www.iceflatline.com/2009/09/how-to-dual-boot-windows-7-and-linux-using-bcdedit/.<br />
<br />
The remainder of the setup is similar to a typical installation. Some documents state that the partition being loaded by the Windows boot loader must be a primary partition but I have used this without problem on an extended partition.<br />
<br />
* When installing the GRUB boot loader, install it on your {{ic|/boot}} partition rather than the MBR. {{Note|For instance, my {{ic|/boot}} partition is {{ic|/dev/sda5}}. So I installed GRUB at {{ic|/dev/sda5}} instead of {{ic|/dev/sda}}. For help on doing this, see [[GRUB#Install to partition or partitionless disk]]}}<br />
<br />
* Under Linux make a copy of the boot info by typing the following at the command shell:<br />
<br />
my_windows_part=/dev/sda3<br />
my_boot_part=/dev/sda5<br />
mkdir /media/win<br />
mount $my_windows_part /media/win<br />
dd if=$my_boot_part of=/media/win/linux.bin bs=512 count=1<br />
<br />
* Boot to Windows and open up and you should be able to see the FAT32 partition. Copy the linux.bin file to {{ic|C:\}}. Now run '''cmd''' with administrator privileges (navigate to ''Start &gt; All Programs &gt; Accessories'', right-click on ''Command Prompt'' and select ''Run as administrator''):<br />
<br />
bcdedit /create /d “Linux” /application BOOTSECTOR<br />
<br />
* 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}. <br />
<br />
bcdedit /set {ID} device partition=c:<br />
bcdedit /set {ID} path \linux.bin<br />
bcdedit /displayorder {ID} /addlast<br />
bcdedit /timeout 30<br />
<br />
Reboot and enjoy. In my case I'm using the Windows boot loader so that I can map my Dell Precision M4500's second power button to boot Linux instead of Windows.<br />
<br />
===== Windows 2000/XP boot loader =====<br />
<br />
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 boot loader; you will still need a {{ic|/boot}} partition, and this one is arguably more difficult to set up.<br />
<br />
=== UEFI systems ===<br />
<br />
Both [[Gummiboot]] and [[rEFInd]] autodetect '''Windows Boot Manager''' {{ic|\EFI\Microsoft\Boot\bootmgfw.efi}} and show it in their boot menu, so there is no manual config required.<br />
<br />
For [[GRUB]](2) follow [[GRUB#Windows_installed_in_UEFI-GPT_Mode_menu_entry]].<br />
<br />
Syslinux (as of version 6.02 and 6.03-pre9) and ELILO do not support chainloading other EFI applications, so they cannot be used to chainload {{ic|\EFI\Microsoft\Boot\bootmgfw.efi}} .<br />
<br />
Computers that come with newer versions of Windows often have [[UEFI#Secure_Boot|secure boot]] enabled. You will need to take extra steps to either disable secure boot or to make your installation media compatible with secure boot.<br />
<br />
== Time standard ==<br />
<br />
* Recommended: Set both Arch Linux and Windows to use UTC, following [[Time#UTC in Windows]]. Also, be sure to prevent Windows from synchronizing the time on-line, because the hardware clock will default back to ''localtime''.<br />
<br />
* Not recommended: Set Arch Linux to ''localtime'' and disable any time-related services, like [[Network Time Protocol daemon|NTPd]] . This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when [[Wikipedia:Daylight saving time|DST]] kicks in. So please do not ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.<br />
<br />
== See also ==<br />
<br />
* [https://bbs.archlinux.org/viewtopic.php?id=140049 Booting Windows from a desktop shortcut]<br />
<br />
== Please remove ==<br />
Please remove my account and this edit.</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Talk:Installing_with_Software_RAID_or_LVM&diff=23700Talk:Installing with Software RAID or LVM2007-05-04T17:23:50Z<p>Kbutcher5: Lousy guide</p>
<hr />
<div>It was pointed out here:<br />
http://bbs.archlinux.org/viewtopic.php?p=121424#121495<br />
that software RAIDing your swap is not useful, and even slows performance.<br />
<br />
== bug in /etc/rc.sysinit?? ==<br />
<br />
I think there is a problem with /etc/rc.sysinit as it not loads the module for the device mapper. This is lvm specific. I just modified the file like this:<br />
<br />
if [ &quot;$USELVM&quot; = &quot;yes&quot; -o &quot;$USELVM&quot; = &quot;YES&quot; ]; then<br />
if [ -f /etc/lvmtab -a -x /sbin/vgchange ]; then<br />
# Kernel 2.4.x, LVM1 groups<br />
stat_busy &quot;Activating LVM1 groups&quot;<br />
/sbin/vgchange -a y<br />
stat_done<br />
elif [ -x /sbin/lvm -a -d /sys/block ]; then<br />
# Kernel 2.6.x, LVM2 groups<br />
stat_busy &quot;Activating LVM2 groups&quot;<br />
/sbin/modprobe dm_mod # &lt;&lt;-----Here is my change<br />
/sbin/lvm vgscan --ignorelockingfailure<br />
/sbin/lvm vgchange --ignorelockingfailure -a y<br />
stat_done<br />
fi<br />
fi<br />
<br />
i use the standard arch kernel<br />
<br />
== What about root on LVM ? ==<br />
I can't figure out how to make it...<br />
mkinitrd variable LVM_ROOT= what to set here??<br />
i am using grub and partition is like this:<br />
<br />
&lt;div&gt;<br />
/dev/sda1 ext2 /boot<br />
/dev/sda2 LVM<br />
vg_name: linux<br />
lv_name: system / ext3<br />
home /home ext3<br />
swap none sw<br />
&lt;/div&gt;<br />
<br />
I've tryed <br />
LVM_ROOT=/dev/linux/system, <br />
grub kernel ... root=/dev/mapper/linux-system or root=/dev/linux/system<br />
i have USELVM=YES and in initrd LVM is enabled...<br />
<br />
lvm partitions was made with lvm2 - but i can activate and mount them manually<br />
where am i wrong??? - <br />
still blocked in bussybox with err - can't mount root - or so... or can't switch [don't remember] - <br />
lvm partitions are disabled - i have to enable and mount them manually<br />
<br />
--[[User:Suw|Suw]] 06:24, 8 April 2006 (EDT)<br />
<br />
== Lousy guide ==<br />
<br />
This has to be the worst, most crappy designed guide i have seen in all of my time with OpenSource, restructure this thing, and strip the old stuff for 7.1, it is VERY outdated. I must say that i would feel more confident just jumping head on out into raid on my own, than following this guid, get som structure in it.</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Touchpad_Synaptics&diff=23611Touchpad Synaptics2007-05-01T20:32:20Z<p>Kbutcher5: </p>
<hr />
<div>[[Category:Input devices (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==What is this ?==<br />
<br />
This tutorial will help install and make your touchpad work properly on your laptop machine.<br />
<br />
==Loading appropriate modules== <br />
<br />
Both ''evdev'' and ''psmouse'' kernel modules have to be loaded in memory. You can check their presence by typing in a console :<br />
&lt;pre&gt;<br />
lsmod<br />
&lt;/pre&gt;<br />
<br />
<br />
In case of problem with these modules, add the following in the MODULES line of your /etc/rc.conf :<br />
&lt;pre&gt;<br />
MODULES = (... evdev psmouse ...)<br />
&lt;/pre&gt;<br />
<br />
==Driver installation==<br />
<br />
As root user type in a console:<br />
&lt;pre&gt;<br />
pacman -S synaptics<br />
&lt;/pre&gt;<br />
<br />
Additional packages may be installed too for graphical post-configuration of the touchpad : ksynaptics (for KDE), gsynaptics (for GNOME). Gsynaptics is in the community repository, which is not enabled by default.<br />
<br />
==Checking for the right device name==<br />
<br />
Type in a console :<br />
&lt;pre&gt;<br />
cat /proc/bus/input/devices<br />
&lt;/pre&gt;<br />
<br />
<br />
The device name is in the Handlers line of the Synaptics / ALPS block.<br />
&lt;pre&gt;<br />
I: Bus=0011 Vendor=0002 Product=0007 Version=0000<br />
N: Name=&quot;SynPS/2 Synaptics TouchPad&quot;<br />
P: Phys=isa0060/serio4/input0<br />
S: Sysfs=/class/input/input1<br />
H: Handlers=mouse0 event1 <br />
B: EV=b<br />
B: KEY=6420 0 7000f 0 0 0 0 0 0 0 0<br />
B: ABS=11000003<br />
&lt;/pre&gt;<br />
<br />
e.g. <br />
H: Handlers=mouse0 event1 <br />
<br />
in this example case the Device Option in the xorg.conf will be :<br />
&lt;pre&gt;<br />
Option &quot;Device&quot; &quot;/dev/input/mouse0&quot;<br />
&lt;/pre&gt;<br />
<br />
==xorg.conf configuration==<br />
<br />
Add the followings lines in the following sections of /etc/X11/xorg.conf :<br />
<br />
<br />
Section &quot;Module&quot; :<br />
&lt;pre&gt;<br />
Load &quot;synaptics&quot;<br />
&lt;/pre&gt;<br />
<br />
<br />
Section &quot;ServerLayout&quot; :<br />
&lt;pre&gt;<br />
InputDevice &quot;Touchpad&quot; &quot;AlwaysCore&quot;<br />
&lt;/pre&gt;<br />
''Note : ServerLayout Section may only contain one &quot;CorePointer&quot; entry. If another pointer is to be used, use &quot;AlwaysCore&quot;. There is only one CorePointer allowed...''<br />
<br />
<br />
Create a new &quot;InputDevice&quot; section for the touchpad:<br />
&lt;pre&gt;<br />
Section &quot;InputDevice&quot;<br />
Identifier &quot;Touchpad&quot;<br />
Driver &quot;synaptics&quot;<br />
Option &quot;Device&quot; &quot;/dev/input/mouse0&quot;<br />
Option &quot;Protocol&quot; &quot;auto-dev&quot;<br />
Option &quot;LeftEdge&quot; &quot;1700&quot;<br />
Option &quot;RightEdge&quot; &quot;5300&quot;<br />
Option &quot;TopEdge&quot; &quot;1700&quot;<br />
Option &quot;BottomEdge&quot; &quot;4200&quot;<br />
Option &quot;FingerLow&quot; &quot;25&quot;<br />
Option &quot;FingerHigh&quot; &quot;30&quot;<br />
Option &quot;MaxTapTime&quot; &quot;180&quot;<br />
Option &quot;MaxTapMove&quot; &quot;220&quot;<br />
Option &quot;VertScrollDelta&quot; &quot;100&quot;<br />
Option &quot;MinSpeed&quot; &quot;0.06&quot;<br />
Option &quot;MaxSpeed&quot; &quot;0.12&quot;<br />
Option &quot;AccelFactor&quot; &quot;0.0010&quot;<br />
Option &quot;SHMConfig&quot; &quot;on&quot;<br />
EndSection<br />
&lt;/pre&gt;<br />
<br />
==Troubleshooting==<br />
===Firefox misinterprets horizontal scrolling===<br />
Even though this problem isn't concerning the synaptics drivers, you will probably look up here for a solution anyway.<br />
To prevent firefox from &quot;scrolling&quot; the history and make it scroll the site, you have to set the following settings:<br />
&lt;pre&gt;mousewheel.horizscroll.withnokey.action = 1<br />
mousewheel.horizscroll.withnokey.sysnumlines = true&lt;/pre&gt;<br />
You can edit them by opening '''about:config'''. (Tip taken from [http://gentoo-wiki.com/HARDWARE_Synaptics_Touchpad#Horizontal_Scroll_Issues_with_Firefox gentoo wiki].)<br />
<br />
===Stopping the mouse from clicking while typing===<br />
This is a neat little trick incorporated with the synaptics driver, you can actually make sure that touchpad tap is disabled while typing. It is a very simple procedure, so here is how it is done.<br />
<br />
In you profiles .xinitrc, that is the file in your home directory of you user, if your username is john it is /home/john/.xinitrc.<br />
You have probably already messed with this file to get your WM(window manager) to start, so to make it short, you just have to add &quot;syndaemon -t -i 2 &amp;&quot; before the execution of your WM. The &quot;-t&quot; tells the daemon not to freeze your cursor and the &quot;-i 2&quot; tells the daemon for how long tapping should be disabled. Tapping will be enabled immediately if you click one of your touchpad buttons, hope this helps, for more options write &quot;syndaemon -h&quot; in a terminal. <br />
<br />
==Links==<br />
<br />
Synaptics TouchPad driver for XOrg/XFree86 :<br />
[http://web.telia.com/~u89404340/touchpad/index.html]</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15187Dual boot with Windows2006-09-07T19:47:39Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot<br />
<br />
hda3: WinXP<br />
<br />
hda4: NTFS drive<br />
<br />
hda5: swap<br />
<br />
hda6: /root<br />
<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
<br />
'''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.<br />
<br />
''Inhere we already have the configuration of our Arch system, it will look something like this:''<br />
<br />
title Arch (7.2)<br />
<br />
root (hd0,0)<br />
<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
<br />
initrd /initrd-2.4.7-10.img<br />
<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
''So here is the need info to put into you menu.lst file:''<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15186Dual boot with Windows2006-09-07T19:46:35Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot<br />
<br />
hda3: WinXP<br />
<br />
hda4: NTFS drive<br />
<br />
hda5: swap<br />
<br />
hda6: /root<br />
<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
<br />
'''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.<br />
<br />
''Inhere we already have the configuration of our Arch system, it will look something like this:''<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
''So here is the need info to put into you menu.lst file:''<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15185Dual boot with Windows2006-09-07T19:46:23Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot<br />
<br />
hda3: WinXP<br />
<br />
hda4: NTFS drive<br />
<br />
hda5: swap<br />
<br />
hda6: /root<br />
<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
<br />
'''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.<br />
''Inhere we already have the configuration of our Arch system, it will look something like this:''<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
''So here is the need info to put into you menu.lst file:''<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15184Dual boot with Windows2006-09-07T19:45:52Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot<br />
<br />
hda3: WinXP<br />
<br />
hda4: NTFS drive<br />
<br />
hda5: swap<br />
<br />
hda6: /root<br />
<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
''Inhere we already have the configuration of our Arch system, it will look something like this:''<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
''So here is the need info to put into you menu.lst file:''<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15183Dual boot with Windows2006-09-07T19:45:42Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot<br />
<br />
hda3: WinXP<br />
<br />
hda4: NTFS drive<br />
<br />
hda5: swap<br />
<br />
hda6: /root<br />
<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
''Inhere we already have the configuration of our Arch system, it will look something like this:''<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
''So here is the need info to put into you menu.lst file:''<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15182Dual boot with Windows2006-09-07T19:44:53Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example): <br />
hda1: /boot <br />
hda3: WinXP <br />
hda4: NTFS drive <br />
hda5: swap <br />
hda6: /root <br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15181Dual boot with Windows2006-09-07T19:43:37Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number. eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15180Dual boot with Windows2006-09-07T19:43:26Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15179Dual boot with Windows2006-09-07T19:43:04Z<p>Kbutcher5: </p>
<hr />
<div>== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15178Dual boot with Windows2006-09-07T19:42:34Z<p>Kbutcher5: </p>
<hr />
<div><br />
== Windows and Arch Dual Booting: ==<br />
<br />
So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15176Dual boot with Windows2006-09-07T19:41:31Z<p>Kbutcher5: User:Kbutcher5 moved to Windows and Arch Dual Boot</p>
<hr />
<div>So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=User:Kbutcher5&diff=15177User:Kbutcher52006-09-07T19:41:31Z<p>Kbutcher5: User:Kbutcher5 moved to Windows and Arch Dual Boot: Wanting to share...</p>
<hr />
<div>#redirect [[Windows and Arch Dual Boot]]</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15175Dual boot with Windows2006-09-07T19:40:05Z<p>Kbutcher5: </p>
<hr />
<div>So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15174Dual boot with Windows2006-09-07T19:39:03Z<p>Kbutcher5: </p>
<hr />
<div>So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
'''''title Windows XP''''' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
'''''rootnoverify (hd0,2)''''' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
'''''chainloader +1''''' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5https://wiki.archlinux.org/index.php?title=Dual_boot_with_Windows&diff=15173Dual boot with Windows2006-09-07T19:38:23Z<p>Kbutcher5: Grub Dual Boot Windows</p>
<hr />
<div>So i figured how to make Arch do dual boot configuration, and i will share it with you all, even though many of you might not want to use microsoft.<br />
<br />
Well to start off, you will need to install windows, i used WinXP. The reason to start with windows, is because it will mess with the MBR(Master Boot Record) if it is not done in this particular order.<br />
Now let's say you have installed WinXP like me, then we boot up the arch installer we pretty much do the same thing here, except a few things:<br />
<br />
1.We will have to use logical partitions for some of our partitions, because there can only be up to 4 primary ones.<br />
<br />
2. '''Very Important''', remember to note down your partitions numbers, for ide drives it is: &quot;hda1, hda2... hda8&quot;, scsi drives: &quot;sda1, sda2... sda8&quot;. So note down which type of partitions belong to which partition number.<br />
eks(using my own computer as example):<br />
hda1: /boot<br />
hda3: WinXP<br />
hda4: NTFS drive<br />
hda5: swap<br />
hda6: /root<br />
hda7: /home<br />
<br />
3. When installing grub, you have to alter the config file that pops up(this is where we make the choice of making WinXP to start up), and make sure to install grub to MBR, will be called hda in my case(sda in scsi case, and so on).<br />
<br />
So on to the altering of the config file(a.k.a. menu.list), if you forget to alter the file, it can be found in /boot/grub/menu.lst<br />
'''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.<br />
Inhere we already have the configuration of our Arch system, it will look something like this:<br />
title Arch (7.2)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3 hdc=ide-scsi<br />
initrd /initrd-2.4.7-10.img<br />
^^This is already specified, and will not need tampering, but notice &quot;root (hd0,0)&quot;, this defines that the root partition is on hd0=disk1 and in 0=partition1(hda1). This is why, if your arch is installed on disk1, partition 3, it will read root (hd0,2). This is because the first control systems, including linux, counts 0 as the first number, not 1!<br />
<br />
So here is the need info to put into you menu.lst file:<br />
''title Windows XP'' &lt;&lt;--Can be anything you like, it will just be what is displayed in the grub bootup screen<br />
''rootnoverify (hd0,2)'' &lt;&lt;--Remember the partiton numbers we wrote down, here you write in the partition number of your windows partition, here it is 2, because my windows is on hda3.<br />
''chainloader +1'' &lt;&lt;--No idea what this does, but better put it there, because people say so :P<br />
<br />
Good luck and i hope this helped you, because it took me a long time to figure out :)</div>Kbutcher5