Comments on: GRUB Error 17, LILO Rules http://www.kerrywong.com/2007/12/09/grub-error-17-lilo-rules/ Mon, 06 Feb 2012 08:13:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Brad Farris http://www.kerrywong.com/2007/12/09/grub-error-17-lilo-rules/comment-page-1/#comment-2112 Brad Farris Tue, 29 Jan 2008 01:56:12 +0000 http://www.kerrywong.com/2007/12/09/grub-error-17-lilo-rules/#comment-2112 17 is beyond annoying! I am running Vista and Gutsy Gibbon. The issue would alternate between the SDA (Vista) and HDA(Gutsy). Apparently each operating system thinks it's important to change a couple of bits that identify the boot sector. It's kinda like the neighbors dog that comes to visit your dog. They leave their mark! I'm sure there may be a technical reason, however I would like to excercise the opt out. Each time a "corruption" occured, the opposing OS had been "updated" or during the install process. Bottom line, I think that each OS should give you the curtesy of asking permmision to soil a boot sector that belongs to another operating system. The commands for repairing the MS Operating system were simple. The only problem is that it took 9 hours to find the information. If I can remember how to get back to this post I will post them. They are on my Ubuntu system and I can't boot that one right now. As I remember there was a couple of terminal lines executing relative to LILO. Then a fixmbr / from the command line opportunity during Vista Boot. Again it boots fine using the bios to choose the operating system. OS need to either get the multiboot right or give you the choice of complete recovery. Oh and the Vista home premium is crap. I am surprised that Intel has not pursued an injuction regarding the degredated performance. As I understand it Vista 159.00USD only utilizes 1 32bit path through the core duo. If you want to "take advantage of a high performace" MB then you have to shell out another 159.00 USD. I guess for Microsoft it's smart, as they don't use a middle man or retailer so the margins are better. I'd be pissed if I were a retailer, cause they are limiting what I can sell. IE the only choice when I bought the OS was Vista Home and Vista Premium. Pretty slick Microsoft... Deception is alive and well. 17 is beyond annoying! I am running Vista and Gutsy Gibbon. The issue would alternate between the SDA (Vista) and HDA(Gutsy). Apparently each operating system thinks it’s important to change a couple of bits that identify the boot sector. It’s kinda like the neighbors dog that comes to visit your dog. They leave their mark! I’m sure there may be a technical reason, however I would like to excercise the opt out. Each time a “corruption” occured, the opposing OS had been “updated” or during the install process.

Bottom line, I think that each OS should give you the curtesy of asking permmision to soil a boot sector that belongs to another operating system.

The commands for repairing the MS Operating system were simple. The only problem is that it took 9 hours to find the information.

If I can remember how to get back to this post I will post them. They are on my Ubuntu system and I can’t boot that one right now.

As I remember there was a couple of terminal lines executing relative to LILO. Then a fixmbr / from the command line opportunity during Vista Boot.

Again it boots fine using the bios to choose the operating system. OS need to either get the multiboot right or give you the choice of complete recovery.

Oh and the Vista home premium is crap. I am surprised that Intel has not pursued an injuction regarding the degredated performance. As I understand it Vista 159.00USD only utilizes 1 32bit path through the core duo. If you want to “take advantage of a high performace” MB then you have to shell out another 159.00 USD. I guess for Microsoft it’s smart, as they don’t use a middle man or retailer so the margins are better. I’d be pissed if I were a retailer, cause they are limiting what I can sell. IE the only choice when I bought the OS was Vista Home and Vista Premium. Pretty slick Microsoft… Deception is alive and well.

]]>