Trevor Farrell wrote:

> Mage Grimau wrote:
>
> > I'm trying to get my machine to dual-boot Win98 and
> > linux. After I install linux (have to do it first or
> > the partitioning doesn't work right) I installed
> > Win98. Then I tried to use my linux boot disk to
> > reload LILO, but it says "/dev/hda1 has no boot
> > record" and quits without doing anything useful.
> > /dev/hda1 is the 7M partition I mount as /boot. I
> > assume I'm doing something wrong, but I can't figure
> > out what (besides adding Win98, that is).
> >
> > =====
> > Mage Grimau, Strange Unwashed & Somewhat Slightly Dazed
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
>
> I could be wrong, but I believe that Windows writes its boot loader to
> the first active partition (usually c: or hda1). In your case, this is
> also the linux boot partition, hence your problem. If the other
> suggestions don't work, I suggest you let Windows have the first
> partition, even if it means having 2 fat32 partitions, with the /boot
> partition between them.
>
> I've done plenty of dual boot installs and never had a problem, but I've
> always had M$ os's on the first partition, and linux further up the
> disk, or on a second disk.
>
> Trevor

Yes it does... wintendo always want to be the first...!

What I have done, is install win98 win95 or whatever version of M$ first...
then install
linux second... that actually works.

Another thing I've done sometimes is install wintendo in the first hd (as
supposed)
then move that hd drive as second hd (hdb) and then install linux in the
second hd (hda)
and installing LILO to take care of the boot process.

After linux has started modified the lilo conf and add the wintendo in
(hdb)
then add the entry in fstab so you can have access to your files in
/wind.... errr whatever.

I hope this helps, I have used both of these approaches and both work. LILO
takes care
of the dual boot nicely.

Sergio

Reply via email to