lilo question

[TheOmegaCode]

Okay, I've searched for the answer to this question, and I can't find out if LILO is capable of dual booting to OS's that are on differen't hard drives. I've got Linux on hda1 and Windows on hdc1. I've read the man pages and searched around on google (well I skimmed). Most places show examples where windows is on hda1 and linux is on hda2, and the boot is set to hda. Any help would be appreciated...

 

[cleverhandle]

It will work just fine. The drive will be indicated in the "image=" line - no other configuration is needed.

 

[TheOmegaCode]

Originally posted by: cleverhandle
It will work just fine. The drive will be indicated in the "image=" line - no other configuration is needed.

You would use other= for windows, and I tried that.

other=/dev/hdc1
alias=Windows

I've also tried

other=/dev/hdc
alias=Windows

and neither of them work. I think it's probably a windows version of a kernel panic. I moved the drive that windows was on from ide0 to ide2. I'm new to lilo, and I just wanted to make sure that lilo was capable of this, since all the docs showed examples where OS's were on the same hard drive. Thanks for the input.

 

[TheOmegaCode]

I guess I just don't understand how master boot records work. LILO is installed in the MBR of ide0, and the ntloader is in the MBR of ide2. If I set BIOS to boot to ide2, I get an error that the nt kernel can't be found.
Now, if I take my cdrom (ide1), and set it to master (so ide0 and ide1 fight for master) the cdrom becomes master, the hard drive next to it doesn't get detected, and Windows boots just fine...

 

[AkumaBao]

Try:

other=/dev/hdc1
label=Windows
table=/dev/hdc

 

[Bremen]

# DOS bootable partition config begins
other = /dev/hdc1
label = dos
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
table = /dev/hdc
# DOS bootable partition config ends

This is what I use for Win98. From what I understand windows has to be on the first hard drive (dosn't matter if ATAPI devices are in front), and so what the above does is make windows think it is the first hdd. Not sure if this will solve your NT problem, but your experiment removing changing the cdrom would seem to suggest this is the problem.