lilo

[John Seth]

Since I no longer use Lilo (now using GRUB), I can't recall my dual boot
script. However, you need to create the two seperate images for lilo to
boot. ie: Linux and Windows.

# Start LILO global section
boot = /dev/fd0
#compact        # faster, but won't work on all systems.
# delay = 5
# VESA framebuffer console @ 800x600x256
vga = 771
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda1
  label = Linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for
checking
# Linux bootable partition config ends
#
# Windows boot
<-- insert windows hd info here -->
# End Windows boot

That's what I have on my Linux server at work which runs Slackware 8.x
w/ LILO. Try setting your HD info on a "per hard drive" basis. Install
LILO on the MBR, and have it wait 5-10 second for you to type "linux" or
"windows" to boot into whichever it wants.  It won't matter from there
which drive is first or not.  Unless you're not sure about writing to
the MBR of your IDE drive, or which drive the BIOS sees first.

 - Tony

----- Original Message -----
From: "Cyber Source" <peter at thecybersource.com>
To: <nflug at nflug.org>
Sent: Saturday, November 09, 2002 12:56 AM
Subject: lilo


: Ok, here's one for ya....
: I am redoing my system, just got a new scsi hard drive and installed
: RedHat 8 on it. I also have an existing windows xp drive (on ide
drive)
: that I used to dual boot with. When connected to the new system, I
could
: not successfully install lilo because it would take the ide drive as
the
: first drive and the scsi drive after. I read the man page on lilo and
: found that the syntax of "disk=/dev/sda bios=0x80" could be added to
: lilo.conf to tell the system that this is the first drive in the
system,
: even with an ide at hda. That worked fine and then successfully
: installed lilo, which booted Linux fine. However, I cannot figure out
: how to get it to dual boot now. I use to use the syntax of
: "map-drive=0x80 to=0x82 map-drive=0x82 to=0x80" but that no longer
: works. That use to work with the drive connected on as hde1 (I have a
: motherboard with additional ATA controllers). I tried connecting it as
: hda to simplify things but that didn't work either. Anyone have any
: experience with this one?
:
:
:
:
: