Have you tried running fixboot and fixmbr from the windows recovery console? Also Testdisk has some options for fixing problem MBRs, though I haven't used any of them yet. On Sat, Oct 11, 2008 at 02:57:59PM -0700, Steve Holmes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > Well, things are even worse now. In trying to isolate my problem, I > took out the new drive that I was installing linux on and replaced it > with my original (second drive) which had my old working slackware on > it and I still can't boot. With my original drive, I even did a lilo > - -r /mnt from my slackware CD and that appeared to go fine; I can't say > I've ever experienced this kind of problem before. I'm trying to do > everything to avoid having to completely re-install windows. I > unfortunately need windows on my box for some time yet. For whatever > reason, my MBR won't take the loader or won't boot for me. > > On Sat, Oct 11, 2008 at 12:32:08PM -0700, Gregory Nowak wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Sat, Oct 11, 2008 at 03:55:44AM -0700, Tony Baechler wrote: > > > The solution is to > > > not chroot. Instead, mount your boot partition under /boot or /mnt/boot > > > and change your lilo.conf as needed temporarily. Run something like: > > > > > > lilo -C /mnt/etc/lilo.conf > > > > > > That should hopefully work, or at least give a useful error message. > > > > After you've got your lilo.conf setup the way you want, don't forget > > to do > > lilo -r /mnt > > to reinstall lilo. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > > iD8DBQFI8SFlWSjv55S0LfERA6F8AKC/ArvNCjVwRWjrfWt5HZ0yTuNVNACffGYv > /VhxetDenfV8M+i9IfT6kKc= > =BYs9 > -----END PGP SIGNATURE----- > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- If Bill Gates is the Devil then Linus Torvalds must be the Messiah. -- Unknown source
