https://bugzilla.novell.com/show_bug.cgi?id=896369 https://bugzilla.novell.com/show_bug.cgi?id=896369#c6 --- Comment #6 from Felix Miata <mrmazda@earthlink.net> 2014-09-12 09:47:49 EDT --- (In reply to comment #5)
...make broken bioses happy...
You keep mentioning this. It makes me think you don't understand that it is normal for legacy-compatible PC MBR code to expect to find no more than one boot flag in any HD's MBR table. The BIOS is not broken just because with legacy code in HD0's MBR a PC fails to boot when more than one flag is set. The failure with more than one set is purposeful. There's not enough space in the MBR's code block for deciding which to choose if more than one flag is set. And, the BIOS and the MBR code original writers knew the operating systems for which it was originally designed, PC-DOS, and later OS/2, will not function in a state with more than one flag set in HD0's MBR. In fact, IBM's Boot Manager would and will ensure only one boot flag is set in HD0's MBR table at every boot. My first two suggestions necessarily assume one is in expert mode and knows that multiple flags set can be boot obstacle with legacy-compatible MBR code. My #3 suggestion makes the best sense to me too, but I think a way to manage flags before reaching summary view makes good sense too. Maybe boot flag management deserves a separate screen if Grub on MBR is not selected, possibly similar to the way selecting fstab options works? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.