Dual-Booting - Revision history

Rpeters: /* New Windows 10 Computers */

2016-12-03T22:29:44Z

New Windows 10 Computers

← Older revision		Revision as of 22:29, 3 December 2016
Line 45:		Line 45:
	#**#failure to boot the CD/USB at all confirms that the machine is in Legacy/BIOS boot mode - and must be reconfigured		#**#failure to boot the CD/USB at all confirms that the machine is in Legacy/BIOS boot mode - and must be reconfigured
	#do a trial boot of your preferred Linux installation medium		#do a trial boot of your preferred Linux installation medium
	#*if it fails to boot, then it is probably configured for Legacy/BIOS mode and is '''unsuitable'''		#*if it fails to boot, then it is probably configured for Legacy/BIOS mode only and is '''unsuitable'''
	#*as of 2016, mainstream Linux and many smaller distro configure their dotISO ~~for~~ ~~both~~ UEFI or Legacy/BIOS boot.		#*as of 2016, mainstream Linux and many smaller distro configure their dotISO to work in either UEFI or Legacy/BIOS boot.

	Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:		Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:

Rpeters: /* New Windows 10 Computers */

2016-12-03T22:28:13Z

New Windows 10 Computers

← Older revision		Revision as of 22:28, 3 December 2016
Line 40:		Line 40:
	#**do '''not''' change to "Legacy/BIOS" mode		#**do '''not''' change to "Legacy/BIOS" mode
	#**as a '''reliable''' confirmation that the machine is booting in UEFI mode:		#**as a '''reliable''' confirmation that the machine is booting in UEFI mode:
	#**#download the "rEFInd" dotISO or dot.IMG file from the above site and make CD or USB ~~device~~ from it		#**#download the "rEFInd" dotISO or dot.IMG file from the above site and make CD or USB media from it
	#**#boot from this CD/USB - invoking F12 at early stage boot/reboot should ensure this		#**#boot from this CD/USB - invoking F12 at early stage boot/reboot should ensure this
	#**#display of rEFInd's distinctive series of icons confirms that the machine is in UEFI boot mode		#**#display of rEFInd's distinctive series of icons confirms that the machine is in UEFI boot mode

Rpeters: /* New Windows 10 Computers */

2016-12-03T22:26:33Z

New Windows 10 Computers

← Older revision		Revision as of 22:26, 3 December 2016
Line 21:		Line 21:

	=== <span style="color:#e57c09; background:#black">''New Windows 10 Computers'' ===		=== <span style="color:#e57c09; background:#black">''New Windows 10 Computers'' ===
			<span style="color:#e57c09; background:#black">It might be '''unwise''' to simply delete/overwrite Windows. Some manufacturers provide no alternate mechanism for upgrading firmware (UEFI - which is "work in progress")

	Such computers invariably have UEFI firmware and "secure boot" enabled. The following link provides general guidance on this process		Such computers invariably have UEFI firmware and "secure boot" enabled. The following link provides general guidance on this process

Line 41:		Line 43:
	#**#boot from this CD/USB - invoking F12 at early stage boot/reboot should ensure this		#**#boot from this CD/USB - invoking F12 at early stage boot/reboot should ensure this
	#**#display of rEFInd's distinctive series of icons confirms that the machine is in UEFI boot mode		#**#display of rEFInd's distinctive series of icons confirms that the machine is in UEFI boot mode
	#**#failure to boot the CD/USB at all confirms that the machine is in ~~BIOS/~~Legacy boot mode - and must be reconfigured		#**#failure to boot the CD/USB at all confirms that the machine is in Legacy/BIOS boot mode - and must be reconfigured
			#do a trial boot of your preferred Linux installation medium
			#*if it fails to boot, then it is probably configured for Legacy/BIOS mode and is '''unsuitable'''
			#*as of 2016, mainstream Linux and many smaller distro configure their dotISO for both UEFI or Legacy/BIOS boot.

	Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:		Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:

Rpeters: /* New Windows 10 Computers */

2016-12-03T22:14:45Z

New Windows 10 Computers

← Older revision		Revision as of 22:14, 3 December 2016
Line 37:		Line 37:
	#*ensure that boot mode is "UEFI"		#*ensure that boot mode is "UEFI"
	#**do '''not''' change to "Legacy/BIOS" mode		#**do '''not''' change to "Legacy/BIOS" mode
			#**as a '''reliable''' confirmation that the machine is booting in UEFI mode:
			#**#download the "rEFInd" dotISO or dot.IMG file from the above site and make CD or USB device from it
			#**#boot from this CD/USB - invoking F12 at early stage boot/reboot should ensure this
			#**#display of rEFInd's distinctive series of icons confirms that the machine is in UEFI boot mode
			#**#failure to boot the CD/USB at all confirms that the machine is in BIOS/Legacy boot mode - and must be reconfigured

	Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:		Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:

Rpeters: /* New Windows 10 Computers */added detailed preliminaries plus mention of instlux

2016-12-03T22:06:28Z

New Windows 10 Computers: added detailed preliminaries plus mention of instlux

@@ Line 24: / Line 24: @@
 http://www.rodsbooks.com/linux-uefi/
 Here are two links to successful procedures for UEFI & BIOS computers.  Although oriented to Ubuntu, analogous steps should work with other Linux:
@@ Line 35: / Line 48: @@
 http://www.everydaylinuxuser.com/2015/11/how-to-shrink-windows-10-to-make-space.html
 ==== Linux Mint 18 ====

Rpeters: /* New Windows 10 Computers */added external links

2016-11-04T22:33:02Z

New Windows 10 Computers: added external links

← Older revision		Revision as of 22:33, 4 November 2016
Line 24:		Line 24:

	http://www.rodsbooks.com/linux-uefi/		http://www.rodsbooks.com/linux-uefi/

			Here are two links to successful procedures for UEFI & BIOS computers. Although oriented to Ubuntu, analogous steps should work with other Linux:

			http://www.everydaylinuxuser.com/2015/11/how-to-install-ubuntu-linux-alongside.html

			http://www.everydaylinuxuser.com/2015/11/how-to-install-ubuntu-linux-alongside_8.html

			Win 10 will probably need to be shrunk:

			http://www.everydaylinuxuser.com/2015/11/how-to-shrink-windows-10-to-make-space.html


	==== Linux Mint 18 ====		==== Linux Mint 18 ====

Rpeters at 22:13, 12 September 2016

2016-09-12T22:13:28Z

← Older revision		Revision as of 22:13, 12 September 2016
Line 53:		Line 53:
	#if the opening UEFI page contains reference to a "UEFI version number" then the computer has UEFI firmware and falls into this category		#if the opening UEFI page contains reference to a "UEFI version number" then the computer has UEFI firmware and falls into this category

	==== Computers having BIOS Firmware ====		==== <span style="color:#005600; background:#black">Computers having BIOS Firmware ====
	This upgrade generally proceeds without problems. The following specific combination of factors has been tested:		This upgrade generally proceeds without problems. The following specific combination of factors has been tested:
	'''if''' existing Windows 7		'''if''' existing Windows 7

	'''and''' firmware is BIOS		'''and''' firmware is BIOS

	'''and''' partition table(s) are MBR(DOS)		'''and''' partition table(s) are MBR(DOS)

	'''Then''' it is reported that an upgrade to Windows 10 can dual-boot. Examples include:		'''Then''' it is reported that an upgrade to Windows 10 can dual-boot. Examples include:

Rpeters: /* Upgrades to Windows 10 */

2016-09-12T22:09:22Z

Upgrades to Windows 10

← Older revision		Revision as of 22:09, 12 September 2016
Line 42:		Line 42:

	=== <span style="color:#e57c09; background:#black">''Upgrades to Windows 10 '' ===		=== <span style="color:#e57c09; background:#black">''Upgrades to Windows 10 '' ===
			==== Computers having UEFI Firmware ====
⚫	'''if''' existing Windows 7
			typically home computers that came with Windows 8.x or generic mainboards of the same era
			*be aware that business-oriented computers of the same hardware era were often installed with Windows 7, but fall into this category
			*many are currently (2016) being refurbished and re-sold by major retailers

			Upgrade to this category of hardware is proving to be the most troublesome
⚫	'''and''' firmware is BIOS

			Be aware that UEFI & BIOS firmware have many similar screens & settings. Check for this hardware as follows:
⚫	'''and''' partition table(s) are MBR(DOS)
			#invoke UEFI settings, at boot time
			#if the opening UEFI page contains reference to a "UEFI version number" then the computer has UEFI firmware and falls into this category

			==== Computers having BIOS Firmware ====
			This upgrade generally proceeds without problems. The following specific combination of factors has been tested:
		⚫	'''if''' existing Windows 7

		⚫	'''and''' firmware is BIOS

		⚫	'''and''' partition table(s) are MBR(DOS)

	'''Then''' it is reported that an upgrade to Windows 10 can dual-boot. Examples include:		'''Then''' it is reported that an upgrade to Windows 10 can dual-boot. Examples include:

	Desktop running separate HDD for Linux and Windows.		Desktop running separate HDD for Linux and Windows.
	*BIOS normally boots to the ~~LInux~~ HDD, which is running OpenSUSE Leap42.1		*BIOS normally boots to the Linux HDD, which is running OpenSUSE Leap42.1
	**and from which Windows 10 can be booted via GRUB 2		**and from which Windows 10 can be booted via GRUB 2
	*During Windows upgrades, disconnect Linux HDD and set BIOS to boot to Windows HDD.		*During Windows upgrades, disconnect Linux HDD and set BIOS to boot to Windows HDD.

Rpeters: /* Linux Mint 18 */corrected first boot situation

2016-09-12T21:50:06Z

Linux Mint 18: corrected first boot situation

← Older revision		Revision as of 21:50, 12 September 2016
Line 27:		Line 27:
	==== Linux Mint 18 ====		==== Linux Mint 18 ====
	#invoke UEFI settings and '''disable''' "secure boot"		#invoke UEFI settings and '''disable''' "secure boot"
	#*although the procedure works without this ~~step~~, it provides better long-term flexibility - see above link		#*although the procedure works, for major Linux distributions, without this change, it provides better long-term flexibility - see above link
	#boot from Linux Mint USB/DVD		#boot from Linux Mint USB/DVD
	#select (the somewhat confusingly named) installation option 1 "install in boot partition alongside Windows"		#select (the somewhat confusingly named) installation option 1 "install in boot partition alongside Windows"
	#on first reboot, ~~Linux~~ only is bootable		#on first reboot, Windows only is bootable
	#reboot, invoke UEFI settings again		#reboot, invoke UEFI settings again
	#amend UEFI boot order to place Windows '''second''' (Ubuntu/Mint first)		#amend UEFI boot order to place Windows '''second''' (Ubuntu/Mint first)

Rpeters: /* Linux Mint 18 */

2016-09-12T08:06:39Z

Linux Mint 18

← Older revision		Revision as of 08:06, 12 September 2016
Line 31:		Line 31:
	#select (the somewhat confusingly named) installation option 1 "install in boot partition alongside Windows"		#select (the somewhat confusingly named) installation option 1 "install in boot partition alongside Windows"
	#on first reboot, Linux only is bootable		#on first reboot, Linux only is bootable
			#reboot, invoke UEFI settings again
	#amend ~~Grub 2~~ boot order to place Windows '''second'''		#amend UEFI boot order to place Windows '''second''' (Ubuntu/Mint first)
⚫	#*either Linux or Windows should ~~now~~ ~~boot,~~ as selected
			#*subsequent boots should now present a Grub 2 menu
		⚫	#*either Linux or Windows should be able to be selected and boot correctly
			#*any additional OS need to be included in the grub.cfg file for Mint

	YMMV with other Linux distributions. Although installation is generally successful, one OS might not boot:		YMMV with other Linux distributions. Although installation is generally successful, one OS might not boot:
	*invoking firmware level boot menu (often F2 on OEM computers or F11 on generic) should enable either to be booted		*invoking firmware level boot menu (often F2 on OEM computers or F11 on generic) should enable either to be booted
	*as a last resort, Linux Mint could be installed and then replaced with the preferred Linux.		*as a last resort, Linux Mint could be installed and then replaced with the preferred Linux.

	=== <span style="color:#e57c09; background:#black">''Upgrades to Windows 10 '' ===		=== <span style="color:#e57c09; background:#black">''Upgrades to Windows 10 '' ===