On 2014-06-21 14:26 (GMT-0700) Tony Alfrey composed:
Felix Miata wrote:
IMO, putting non-legacy code into the MBR of a BIOS multiboot-with-Windows system is pointlessly and unnecessarily asking for trouble, like you've encountered and more.
Well, then we need to talk to whomever designed the SuSE install disk to understand how that code ended up in my Windows MBR, in spite of my watching carefully during installation to see that the boot loader ended up ONLY on the linux disk.
To be clear, installing bootloader to MBR is a virtually universal, if not completely universal, default policy among all Linux distros' installation programs. Because of my policy of always installing to a partition, I have no ideas why bits of Grub2 would have been spread across boot tracks of multiple disks. Again, problems such as yours are why many who have Windows on its own HD are why they disconnect the Windows HD before installing Linux. It's been more than a decade since any disk manufacturers made disks small as the space I ever allow Windows access to on any of my installations, so Windows when installed at all here is on the same HD as Linux (licensed Windows all my Dells, no Windows on any others). A simple minimalist installation like this can be seen on http://fm.no-ip.com/PC/install-doz-after.html (20G HD). -- "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