On Fri April 9 2004 15:36, CAMERON NIKITIUK wrote: > Hi All, > > I tried to post this earlier but I don't know if it went through or not, so > forgive me if this double-posts.
Okay. Consider yourself forgiven. :-) > I did a little googleing and from what I have seen, the BIOS may not > recognize the geometry on the hard disk and GRUB takes it's information > from there to set up the boot loading. The suggestions I have come across > include booting off a win98 boot disk (person had a dual bot with 98) and > entering "fdisk /mbr" at the command prompt. I have been cautioned that > this can pooch your system and want to be slow and deliberate as I deal > with this problem. I, personally, have never had any trouble using 'fdisk /mbr'. OTOH, I would only use it if I needed my Windows system back in order to work. Otherwise, since you eventually want to move away from Windows altogether, I think it should only be used as an interim fix. > Seeing as it is a fresh install I don't mind blowing away the install (on > hdb) and doing it again if I need to, but I want to maintain the integrity > of the existing windows hard disk (hda) seeinga s that is my current > working environment. I am just wondering if rebooting from a win98 disk is > the smart thing to to do or should I just try reinstalling suse again from > the CD. If I remember my bootloader parameters correctly I may have put > GRUB on hda. Not SUre if that is the right thing to do or not? I haven't installed SuSE before (and have limited experience with GRUB), so I may be missing something, but I think most installations are going to try to install the boot loader to the first disk (20GB in this case). Now, I wouldn't think that GRUB would have a problem booting to your ridiculously large second disk (hehe disk envy ;-), but you're right; the BIOS may be hampering that effort. > ANy suggestions are welcome as are offers to come over and fix the problem > for me <hehehe ;-)>are greatly appreciated!!! I don't think you want me to come over, I've been sick for 3 days. :-P But I'm always full of suggestions (not all of them useful). :-) If you have any space left on your first disk, I would make a small (50-100MB) partition for / (or at least /boot). That way the MBR can find the first partition, and load everything else from the second disk once the kernel is initialized. If that's not possible, then it may pay to move the 160GB drive to be the first disk as suggested by Mike. Failing that, you may need to dig deeper into your BIOS and/or GRUB. Keep me posted. Curtis _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
