Thomas Taylor composed on 2015-07-22 09:40 (UTC-0700):
Having "upgraded" MS versions many times in the past in multi-boot systems can say there are some "gotchas" on MS part.
First, openSuSE has an UEFI shim so that shouldn't be a problem.
Next, MS tends to try to use the "ENTIRE" physical drive by default.
That only applies if you provide it an entire physical drive to do with as it pleases, not if you don't.
One has to do some gymnastics to get that changed.
It's not at all complicated. Simply partition before booting the installation media, then it will ask where you want it to install, and you tell it, no more difficult than deciding the best choice to make in YaST's first partitioning step at openSUSE installation time.
Another problem will be the bootloader. MS ALWAYS but boot code in the MBR track, meaning you will at minimum need to re-create a new bootloader for multi-boot.
Neither are correct, at least for BIOS systems. For those it puts legacy-compatible code in the MBR sector, leaving the rest of the MBR track untouched. If legacy-compatible code is already in the MBR sector, it doesn't change it. Most of my installations actually use IBM OS/2 MBR code. Windows (through v7 at least) is perfectly content to leave it alone and boot as if it had installed its own MBR code. Multiboot does not depend on alternative boot code in either MBR sector or sectors immediately following. Legacy-compatible boot code searches for an active primary partition on BIOS HD0, and if only one is found, it transfers control to it (if !=1, then it produces an error message and halts). So, Windows boot normally proceeds based upon what is in the active primary partition's boot sector, only indirectly on account of code in MBR. It works the same way for Linux similarly configured, which is how all my many multiboot systems work, Grub is on PBR for / filesystems, not on MBR, plus Grub is on PBR of a primary, which will chainload a Windows non-active primary, or any Linux / partition with Grub in its PBR. None of my installations have any non-legacy-compatible bootloader code in MBR sector or sectors immediately following. Most are virtually always booting Linux, Windows maybe once or twice a month, sometimes months at a time not at all.
The above having been said, you may or may not need to re-install OS 13.1 depending on how friendly (Unfriendly?) MS decides to be.
Mere minutes ago I completed installation (and some hours of updates and reboots) from Win7 DVD on a system with working 13.1, 13.2 & TW installations. Windows installation had zero impact on Grub or its ability to boot Linux, once I moved the primary partition boot flag back from sda1 to sda3. As Windows' bootloader has the capability to in effect chainload any primary partition, if you configure it to do so, then the boot flag can be left set on the Windows primary, and Windows bootloader can load Grub to get Linux booted. This is that fresh Win7 installation's partitioning: http://fm.no-ip.com/Tmp/Dfsee/dfsLmalco722.txt -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org