Just as a side note, I thought I'd add that I have also seen this exact
problem occur in a linux-only system (malen: remember phobos?). In this
particular scenario, we were using a 486 "frankenputer" which had a bunch
of strung together *really* *really* *really* old and messed up <=
300-ish-MB drives. Now that I think of it, part of me wonders if it may
have had anything to do with the quality of the drives? It's all kind of
hazy to me now, but I think we solved the problem by swapping the drive
for another in our bucket o' old and rusty drives.
apologies if that isn't all that helpful.
laziness + abundent franken-parts = cheap and thoughtless fixes ;)
return 0;
/* adam */
On Wed, 25 Jul 2001, Sach Jobb wrote:
> Yeah, i think what you've got here is an order of operations problem. I've
> run into the same thing several times. You should install windows, and
> then linux.
>
> Now, here's how to get out of your current problem.
>
> 1) Boot off of a dos floppy that has format on it.
> 2) run 'format /mbr' (this is an undocumented feature)
>
> This command restores the master boot record and plops in the dos one for
> you. Now you should be able to boot back into windows no problem. Of
> course, you;ve lost the ability to boot into Linux. This can be fixed by
> booting off the cd in recue mode and then rerunning lilo (with some
> switches), or by simple reinstalling. As tack said too, try to use grub if
> you can. Oh, and a newer version of Debian wouldn't hurt either. ;) Do you
> have a copy of 2.2 sitting around?
>
> Cheers,
> sach
>
>
>
>
> On Wed, 25 Jul 2001, Toby Jacobson wrote:
>
> > Strangely enough, I have only had that problem with dual-booting
> > windows systems. Perhaps windows overwrites all but two bytes of the
> > mba, or something? I like the idea of using a different boot loader as
> > tack suggests. Running NT or 2000 (if indeed you are dual-booting),
> > one can add another entry to windows' default bootloader, then use
> > loadlin. Otherwise, re-"upgrading" a redhat installation seems to
> > reinstall lilo.
> >
> > -malen
> >
> > --- Jonas Ditch <[EMAIL PROTECTED]> wrote:
> > > Hola!!
> > >
> > > I belive that I have a messed up LILO install.
> > > The symptoms are:
> > > Boots up to LI and stops (As in LILO boot prompt)
> > >
> > > I had just installed Debian 2.1 I reinstalled and
> > > that did not fix the problem. Switched to
> > > anouther version of Linux (RH 6 Kernal 2.2.10)
> > > that did not work either. I am currently booting
> > > up threw floppy which is time consuming.
> > >
> > > Thank you for your help
> > >
> > > Jonas
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Make international calls for as low as $.04/minute with Yahoo!
> > > Messenger
> > > http://phonecard.yahoo.com/
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Make international calls for as low as $.04/minute with Yahoo! Messenger
> > http://phonecard.yahoo.com/
> >
>
>