🚀 go-pugleaf

Elem103 <elem103@smokey.aic.net.au> wrote:


>> Can Win 2k boot loader run after lilo has taken in? I had the idea that 2k
>> acts like NT and doesn't boot if it doesn't 'own' the MBR? Am I wrong?

> I'm running my system with NT and Linux and Linux owns MBR.  Also have a
> system with Win2K and linux and it works fine too.

OK. I'm just making sure that this is possible, because Red Hat guides
state that: "To create a dual-boot environment on a system that currently
has NT, you must install LILO on the first sector of the root partition,
not the MBR." 

I have also assumed, that NT or 2k won't boot if it doesn't
own the MBR. Glad that you made it. How did you install the OS's? First
the M$ stuff and then Linux, writing the MBR over?


>> Anyway, if you have lilo in MBR and you're able to boot 2k, please let me
>> know your configuration.

> Err.. everyone has different lilo config.

> Generally the important parts are:

Yes, I assume that I know what rows in lilo.conf mean. I just asked that
also to know if there was something special. 

Just asked both due to scepticism on 2k booting without 'owning' the MBR.
Didn't want to experiment, you know?


Anyway this prob below was odd, I thought that newer lilo's could load
with that lba32 setting the OS being quite far from beginning of drive. Or
is that the problem I'm having?

>> Yes, I have similiar problem, I have first 3 Fat32 partitions
>> (hde1,hde5,hd6) 8 Gigs each and then linux / and swap. Tried to do that
>> MINI-HOWTO-procedure for NT-bootloader, but lilo says then only 'LI' and
>> repeats it over and over again... Like this:
>> LI
>> LI
>> LI
>> LI ...and so on.
>>
>> (I've RH 7.0)
>>
>> Even tried both 'linear' and 'lba32'. Would grub work better?