On Wed, 31 Jan 2007 14:36:47 -0500, Carl Hartung <[EMAIL PROTECTED]> took time to say the following:
(^_^)Hi Darryl, (^_^) (^_^)The repaired menu.lst I posted yesterday (quoted below) seems to match your (^_^)interpretation. One thing, though, I 'clipped out' one of the two apparent (^_^)Windows installations thinking it could be added back later, manually or via (^_^)the bootloader configuration module. That, and confirming the version numbers (^_^)for his installed initrd and vmlinuz, are the only outstanding questions for (^_^)this part of the puzzle. (^_^) (^_^)> - - - - - 8< - - - - - (^_^)> # Modified by YaST2. Last modification on Sun Jan 28 20:13:54 PST 2007 (^_^)> default 0 (^_^)> timeout 12 (^_^)> gfxmenu (hd0,7)/boot/message (^_^)> (^_^)> ###Don't change this comment - YaST2 identifier: Original name: linux### (^_^)> title openSUSE 10.2 (^_^)> root (hd0,7) (^_^)> kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda8 (^_^)> resume=/dev/sda7 splash=silent showopts (^_^)> initrd /boot/initrd-2.6.18.2-34-default (^_^)> (^_^)> ###Don't change this comment - YaST2 identifier: Original name: Windows ### (^_^)> title windows 1 (^_^)> rootnoverify (hd0,0) (^_^)> chainloader (hd0,0)+1 (^_^)> (^_^)> ###Don't change this comment - YaST2 identifier: Original name: failsafe### (^_^)> title Failsafe -- openSUSE 10.2 (^_^)> root (hd0,7) (^_^)> kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda8 showopts (^_^)> ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 (^_^)> initrd /boot/initrd-2.6.18.2-34-default (^_^)> (^_^)> - - - - - 8< - - - - - (^_^) (^_^)> It is possible that the grub MBR contains incorrect offsets because of (^_^)> these errors. However, correct menu.lst only and see if you can boot; we (^_^)> can re-install the grub boot record later, if that proves to be necessary. (^_^) (^_^)agreed (^_^) (^_^)> The only other possible source of a problem is a missing or incorrect (^_^)> stage 1.5 file embedded in the grub MBR. We'll check that if the above (^_^)> corrections do not work. (^_^) (^_^)agreed (^_^) (^_^)If Charles is working a full day today we many not know the results before (^_^)late evening (EDT). (^_^) (^_^)regards, (^_^) (^_^)Carl I'm not certain if I posted it or not, but the version numbers are the same. <drum roll> After re-checking the fstab, menu.lst and device.map files, I decided to give it a try. <pause for affect> I have some good news and some not so bad news I guess. I went to re-install the bootloader, and it did NOT give me the error it has been giving me. That's the "good" news. the "not so bad news" is, There's still no grub bootloader when the computer boots up. :-( It still goes straight into XP. Which will be the default anyway if the bootloader was actually functioning. So that's where things are right now. Good Night! Thanks to everyone who helped me get this far. Too many people spend money they haven't earned to buy things they don't want, to impress people they don't like. -Will Rogers -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
