To be honest it was due to laziness. And not wanting to muck up windows drive allocations etc. Thinking it through, it may be easier to fix it first and see if it helps lilo out. Is there any chance that switching them could work? -----Original Message----- From: philippt@t-online.de [mailto:philippt@t-online.de] Sent: Friday, October 05, 2001 3:48 PM To: suse-linux-e Subject: Re: [SLE] New Lilo problems * Carley, Jason (Hong Kong) [Fri, 5 Oct 2001 09:47:11 +0800 ]:

It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind a CDROM drive on the 1st IDE controller

Might I ask which reasons this were? For all means, removable drives should always follow fixed drives.

I get the famous LI response from the bootloader. Now after looking this up in the docs and being told that it relates to disk geometry I am stumped.

It might be as simple as lilo using the wrong BIOS identifier. If that's the reason, but this in the global section: disk=/dev/hdb bios=0x80 This tells lilo that your slave will be the first disk discovered by the BIOS (which enumerates the drives in the order it detects them). Philipp -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com