How to DUAL BOOT Windows 10 and OpenSUSE 13.2
The following images were taken while dual-booting a Dell D630 running Microsoft Windows 10. OpenSUSE 13.2 was selected as
the Linux version because it does not require an internet connection during installation. The laptop was not on a network.
The system was running with the local user (luser) logged in, luser has admin rights. The DVD was inserted and the executable
on the DVD was activated to setup a Live session of SUSE Linux. Once this was done the installation option was selected and
it modified the boot process and then rebooted the laptop, coming up into the installer. When it completed the bootup process
went to a menu where Linux or Windows could be selected, once there it went to a Microsoft boot loader, where another choice
was possible. One could multi-boot a system using these methods. You could configure Windows to boot XP, Win7, Win8 and Win10,
and THEN install different versions of Linux.
IMPORTANT NOTE: When configuring multiple boots on a system, always try to install Microsoft first, because it will dominate the
boot up utility and wipe out anything Linux installs. Linux will modify the Microsoft files and coexist peacefully.
One other note, it is recommended that you first partition your drives as desired, then install Microsoft, then Linux.
To configure your drive use Gparted or other utilities to created partitions, remembering that there are only 4 primary partitions available.
To partition a drive in preparation, see:
http://johnmeister.com/linux/Notes/Gparted-for-Recovery/ALL.html for info on Gparted.
video issues... driver or hardware... comes and goes - dual-booting benefit
Having a dual-booted system allows you to access your files on a system that may have corrupted drivers. However, if it's Linux
that has the corruption you'll not be able to see them from the Microsoft side, however, you will be able to verify that the hardware is
working and connect remotely to the Linux system once it boots up, or remove the hard drive and mount it to another Linux system.
The real benefit is to support the Microsoft installation, it's not a question of if, but when you will get adware, malware, a virus or hacked,
so having a "back door" into your system via Linux will allow you to rescue your files and possibly rescue the Windows system if you know what
files are infected.
One of my Toshiba laptops has an apparent video issue as shown in the picture below,
this happens every now and then... usually when I need it... seemed like it only happened when booting up on SuSE 13.2,
as it worked well with MINT. But I noticed it also did it with MINT Linux... right when I needed it in a training session.
The other difference, so I though, was that MINT was on a 256GB SSD, SuSE was on a 2TB SATA drive. Thinking that the extra work of spinning
platters might have been too much for the little laptop.
So, I'm going to try changing out/upgrading the memory in hopes that will help, otherwise I'll be looking for another mother board as the laptop
is great at 2 lbs 4 ounces (1,025 grams).
We have talked about "shell shock" before when discussing security and the risks, attack vectors and such, here's the command to test your BASH
shell to see if it has been patched. If it hasn't and you are not using your system as a webserver or with multiple users there's no reason
to panic, but if you're not reading log files and such you might activate the firewall to add a little extra safety until you can patch.
In addition, the other notes were in my recently retired notebook and are useful for deleting blank lines in files. I always seem to forget
these shorter commands when I need them.
The last line is a find command used in a few scripts, seeking out and eliminating zero byte files that didn't make it in a file transfer.
Forgetting short commands is a common theme, guess that's why I stick to the bread and butter commands in Linux.
Was creating this page and dealing with the annoying colors flashing and changing every time I typed an HTML symbol, so
I tried to remember how to stop it... to shut off the recoloring of the page that will show errors in HTML and even some
programming languages. I first thought it was the set command... well... it wasn't. But not wanting to waste a great bunch
of eye candy and screen info, I captured the output of ":set all" and made a page out of it... but all I was looking for was
":syntax off - but, tried set all: http://johnmeister.com/linux/vi/vi-set-all.html
I believe that output is from the BASH shell on a MacBook Air, but it could be on a Dell running SuSE 13.2, don't recall which shell I was in.
some assorted general info on Dual booting
I've been dual and multi-booting systems since the '90's... had a 286 laptop that was multi- booted with Microsoft DOS 6.0,
Windows NT 4.0, Win 3.11, Win 95, and Slackware Linux... trying to remember if I had Win NT 3.1 on it as well. At the time my boss
and a few of my co-workers were beta testing NT 4.0 and I may have installed it as well. The issues of booting into different
operating systems can be quite complex and frustrating, especially if there are any hardware issues, or bugs in install scripts.
Before we cover the process of Dual-Booting Windows 10 and SUSE, sharing some other dual-booting issues
encountered to raise various points to watch as you configure a dual booted system.
MINT Linux onto SuSE Linux 13.2
The install screen from LINUX MINT - install alongside SUSE - excellent... or so I thought.
FALSE STARTS... failed to RTM (well, the screen)
However, this is what MINT did to the drive... because I didn't read all the checked boxes and details. It was trying
to implement a good model. But I had a design in mind but didn't ensure that it happened.
I did not want extended partitoins, and I had resized partitions already to allow Mint to drop right into /dev/sda1
However, I neglected to look at what Mint was going to do. Always look at the proposal, it takes a little time, but
much less than having to use Gparted to put things back to "simple".
A closer look at the allocations.
I used Gparted to fix this issue, the picture shows the cleanup.
Created a partition after undoing what MINT did the first time when I wasn't paying attention.
Typical of a good install they created an extended partition and placed their root and home directories there. But I had
already allocated space for them and they moved stuff around unnecessarily, but it was my fault, I clicked through too quickly.
I used ext3 for the MINT partition because of some of the issues with the newer file systems. Ext4 is ok, but would have chosen ext3.
These are all journaled file systems and stable. The newer file systems are "mostly" stable. I've been burned several times with lost files
using newer types of file systems. I would suggest avoiding them; pay attention to what the screens are describing.
So, MINT will go into /dev/sda1, about 31 GB, swap into /dev/sda3 and SUSE was on /dev/sda2.
This ended up different than what I had intended. I used Gparted to shrink /dev/sda2 from 1.8TB
to allow about 30GB for MINT. The swap was set to about 4GB, but I ended up reducing it to 2GB in
the final version. It turned out that the laptop I was attempting to dual boot this on has a BIOS issue
that I found about on line. I had to set the BIOS to IDE for it to find the SATA drives... enough said.
So, the follow on screens show a vain attempt to repair GRUB2, but I gave up and will wipe this 2TB drive
and make it all one big Windows 7 system for digital photography, with a small back door of MINT just in case.
This shows the end result by MINT after installing alongside of SUSE. Of course it won't boot
on the system intended, and I haven't taken apart the other laptop to try it there. I have confidence that
using either the MINT or the SUSE install media and doing an "update" will likely fix the GRUB2 issue, but
not on the laptop involved as others have also noted a BIOS issue with this model. It's not a serious problem,
unless you try to get creative. Remember most of these systems were designed to work with Microsoft, not other OSes.
So, at this point I put the Microsoft/MINT drive back into the ASUS and booted into Win7 in prep of working
on the dashcam video project. Soon after installing spybot or CygWin Firefox was not going to my selected
home pages, but to Yahoo. Then a popup would be displayed that talked about Crime Watch click here... yeah,
right... nuked Yahoo from the registry, cache, cookies, and a few other things... think it's fixed... but that
laptop is going away... as a dual-booted Win7/MINT device.
This is a screen shot of Microsoft Essentials and Spybot Search and Destroy scanning and loading.
As I bought this laptop used on Craigslist and never used Win7, just dual-booted it immediately and
have only used it in Linux, I'm thinking it had this adware/malware issue already. When I decided to use it
for Win7 to do some of the video work from the dash cam I discovered adware/malware, and realized I'd never
installed spybot or Microsoft Essentials.
However, I'm not sure if my download of CygWin from Soureforge caused the infection or if it existed
on the system already. I read that SourceForge had been infected. I have cleaned it, and am selling the
laptop because it's heavier than my others, but is a really nice system, i7 core with 4gb of memory and a 500gb drive.
It is very nice to see Spybot working (against Microsoft). I've used spybot for years, install
it and often forget about it... until it alerts at some point in time of an issue. However, be
careful where you download it, many of the free download sites are infected apparently, and also
automatically check boxes to enable yahoo or google or whatever... watch the check boxes.
Here's an attempt at GRUB rescue... I found step by step commands on a nice web page, called it
up on my iphone... typed said commands in place... barf. Suspect the BiOS issue, or a script
issue in the MINT install script. By the time this picture was taken it was quite late and
I decided to bail on the idea of making the 2TB drive a dual boot Linux system in part because
only Linux could read it. So, the 2TB drive will be configured with NTFS by Win7 so it can
be read by my Linux and Mac systems. I will back it up to an external 4TB drive that will live
on Linux though. The Win7 environment permits use of familar digital image editing tools like
Irfanview, Bomes Image Resizer and even LViewPro... don't laugh, it is the Win95 version too.
These are the detailed steps to execute a grub-rescue. I partially suspect that the path to
the modules were wrong in the script and I was too tired to edit the commands to find them and
attempt to make this work. This system was using GRUB2. When you get into the entire booting
realm it isn't extremely clear or simple. GRUB and GRUB2 are only slightly less complex than LILO.
the "normal.mod" file was likely in the path: /boot/grub2/i386-pc NOT /boot/grub/i386-pc
see it's down in the middle. ONE little character... not the fault of the folks creating the
grub-rescue tool, it's the folks that keep changing the basics in LINUX with things like systemd
and /etc/sysconfig and /run and other "improvements" that complicate and break, but do improve.
acpi.mod adler32.mod affs.mod afs.mod ahci.mod all_video.mod aout.mod archelp.mod ata.mod
at_keyboard.mod backtrace.mod bfs.mod biosdisk.mod bitmap.mod bitmap_scale.mod blocklist.mod
boot_hybrid.img boot.img boot.mod bsd.mod btrfs.mod bufio.mod cat.mod cbfs.mod cbls.mod cbmemc.mod
cbtable.mod cbtime.mod cdboot.img chain.mod cmdline_cat_test.mod cmosdump.mod cmostest.mod cmp.mod
command.lst configfile.mod core.img cpio_be.mod cpio.mod cpuid.mod crc64.mod cryptodisk.mod crypto.lst
crypto.mod cs5536.mod datehook.mod date.mod datetime.mod diskboot.img diskfilter.mod dm_nv.mod drivemap.mod
echo.mod efiemu32.o efiemu64.o efiemu.mod ehci.mod elf.mod eval.mod exfat.mod exfctest.mod ext2.mod extcmd.mod
fat.mod font.mod freedos.mod fshelp.mod fs.lst functional_test.mod gcry_arcfour.mod gcry_blowfish.mod
gcry_camellia.mod gcry_cast5.mod gcry_crc.mod gcry_des.mod gcry_dsa.mod gcry_ecc.mod gcry_md4.mod
gcry_md5.mod gcry_rfc2268.mod gcry_rijndael.mod gcry_rmd160.mod gcry_rsa.mod gcry_seed.mod gcry_serpent.mod
gcry_sha1.mod gcry_sha256.mod gcry_sha512.mod gcry_tiger.mod gcry_twofish.mod gcry_whirlpool.mod gdb.mod
geli.mod gettext.mod gfxmenu.mod gfxterm_background.mod gfxterm_menu.mod gfxterm.mod gptsync.mod
gzio.mod halt.mod hashsum.mod hdparm.mod hello.mod help.mod hexdump.mod hfs.mod hfspluscomp.mod
hfsplus.mod http.mod iorw.mod iso9660.mod jfs.mod jpeg.mod kernel.img keylayouts.mod keystatus.mod ldm.mod
legacycfg.mod linux16.mod linux.mod lnxboot.img loadenv.mod loopback.mod lsacpi.mod lsapm.mod
lsmmap.mod ls.mod lspci.mod luks.mod lvm.mod lzma_decompress.img lzopio.mod mda_text.mod
mdraid09_be.mod mdraid09.mod mdraid1x.mod memdisk.mod memrw.mod minicmd.mod minix2_be.mod minix2.mod
minix3_be.mod minix3.mod minix_be.mod minix.mod mmap.mod moddep.lst morse.mod mpi.mod
msdospart.mod multiboot2.mod multiboot.mod nativedisk.mod net.mod newc.mod nilfs2.mod normal.mod
ntfscomp.mod ntfs.mod ntldr.mod odc.mod ohci.mod part_acorn.mod part_amiga.mod part_apple.mod
part_bsd.mod part_dfly.mod part_dvh.mod part_gpt.mod partmap.lst part_msdos.mod part_plan.mod part_sun.mod
part_sunpc.mod parttool.lst parttool.mod password.mod password_pbkdf2.mod pata.mod pbkdf2.mod pcidump.mod
pci.mod plan9.mod play.mod png.mod priority_queue.mod probe.mod procfs.mod pxeboot.img
pxechain.mod pxe.mod raid5rec.mod raid6rec.mod read.mod reboot.mod regexp.mod reiserfs.mod
relocator.mod romfs.mod scsi.mod search_fs_file.mod search_fs_uuid.mod search_label.mod search.mod sendkey.mod
serial.mod setjmp.mod setjmp_test.mod setpci.mod sfs.mod sleep.mod spkmodem.mod squash4.mod
tar.mod terminal.lst terminal.mod terminfo.mod test_blockarg.mod testload.mod test.mod testspeed.mod
tftp.mod tga.mod time.mod trig.mod true.mod udf.mod ufs1_be.mod ufs1.mod
ufs2.mod uhci.mod usb_keyboard.mod usb.mod usbms.mod usbserial_common.mod usbserial_ftdi.mod usbserial_pl2303.mod
usbserial_usbdebug.mod usbtest.mod vbe.mod verify.mod vga.mod vga_text.mod video_bochs.mod video_cirrus.mod
video_colors.mod video_fb.mod videoinfo.mod video.lst video.mod videotest_checksum.mod videotest.mod xfs.mod
xnu.mod xnu_uuid.mod xzio.mod zfscrypt.mod zfsinfo.mod zfs.mod
The way this is supposed to work is you end up using the install "live" disk to get to some tools to repair grub.
You should know which OS is on which partition. From the "live" CD you should be able to type "grub-mkconfig" to
find the /boot files and build the menus and cfg files.
Using os-prober helps you verify that the partitions and operating systems. Again, grub-mkconfig was having
trouble because the canonical names of the distributions weren't exactly as expected by this older tool. At least
that's my assumption based on the errors and the fact that the files expected were either not there or reported
in a different format. What this means to me is that I needed to learn GRUB and GRUB2... I tried to find time
to do that. Gave up. The 2TB drive is going Win7, the ASUS is going away. Problem solved. I know that both
MINT and SUSE should be able to fix this from their LIVE CDs as I've been here many times before. A minor hardware
issue and updated Linux features with old tools just do not make for a productive Saturday night.
Tried to use some MINT tools to fix the boot process.
apt-get install -y boot-repair
that should have worked... and will on a different laptop.
Before we dual boot Windows 10, let's note that some of us might not want Windows 10... at the very least
we do not want to be pushed, prodded and irritated with the free upgrade... thankfully a friend who used
to work at Microsoft and now works on Linux texted the answer to my facebook post complaining about the popup...
YES, YES, YES... make it stop... oh wait... we're talking about Dual-Booting Win10 with Linux... I forgot
what we were doing... :) Ok, so only do this if you don't want Windows 10...
also: this might be a problem for dual booting according to some forums:
As for me, I dual-booted a test system, and have no plans on using Win10, or Win8... when Win10 comes up
with a classic desktop, nice and clean, crisp, with a functional file manager excluding "libraries" and "favorites"
and all the other "my crap" then I'll use it. In the meantime, dual-booting allows you to get things done and
still have access to programs that the programmers weren't smart enough to write for Linux. It's a crutch. As soon
as you get done with the Windows app, boot back to safety and security... :)
and now... the MAIN feature...
dual booting Windows 10 with Open SUSE 13.2
Used OpenSUSE 13.2 because it did not require a network connection. Did the installs without a network.
I prefer my Linux systems with wine...
in other views...
They had this 747-400 Freighter sitting outside the factory last week... must have been for an oil change or something...
PRO PATRIA VIGILANS:
(The motto of the US Army Signal Corps, "watchful for the country" )
18 August 2015
where it all happens:
some links to notes on various viruses, mostly Microsoft
(these files will be updated and moved onto LinuxMeister at some point, not
permantely linked, or activated...) (tmp means temporary...)