Tech Support > Operating Systems > Linux / Variants > lilo install problem
lilo install problem
Posted by Jacques Charroy on July 18th, 2003


hello,
I use a suse 7.3 distribution and had installed lilo on the mbr during
installation.
But I couldn't get windows (95) to be booted first even by putting
default=windows or default=hdc1
in the lilo.conf file. So I used Yast1 to setup lilo once again and by
error set it up on the boot sector of the root partition. Now windows is
the default boot but it doesn't boot right: just after the lilo screen,
I get this error message:
I/O error
replace it and hit a key
which probably means that I got a boot sector problem.
by using a windows boot disk, I'm able to access the windows disk,
though.
Does somebody know how I can get windows to boot once again?
thanks a lot inadvance,
Jacques Charroy

Posted by spike1@freenet.co.uk on July 18th, 2003


Jacques Charroy <jcharroy@club-internet.fr> wrote:
hdc1? So, you have a primary master with linux and a secondary master with
windows?

This should work then

boot=/dev/hda
vga=normal
read-only
lba32
prompt
timeout = 80
message = /boot/message
# assuming you have a /boot/message file
default=windows

# End LILO global Section
#
other = /dev/hdc1
label = windows

image = /boot/vmlinuz
root = /dev/hda2
label = linux
initrd=/boot/initrd # assuming you have one of course

tweak the filenames as nessecary of course.


Then run lilo to enforce the change.

Posted by Jacques Charroy on July 18th, 2003


spike1@freenet.co.uk a écrit :
no. hda1 is my cdrom drive. I have only one hard disk and the partitions
are the following (report from KDE control center):

major: minor: #blocks: use:
hdc: 22 0 8257032 I guess it represents the hardware
hdc1: 22 1 6369741 windows
hdc2: 22 2 1 (?) I don't understand the use of it
hdc5: 22 5 24066 /boot
hdc6: 22 6 136521 /swap
hdc7: 22 7 1718823 /


do you think this is going to solve the problem that windows can't boot
(see initial message)?
this is the real problem now because linux boots correctly and windows
is the default os at present.
It's just that it (windows) won't boot at all.
thank you, though. I'll try this if you say it solves the windows boot
problem.
Jacques

Posted by spike1@freenet.co.uk on July 18th, 2003


Jacques Charroy <jcharroy@club-internet.fr> did eloquently scribble:
Why on earth have you got the CD on the primary?

--
__________________________________________________ ____________________________
| spike1@freenet.co.uk | "Are you pondering what I'm pondering Pinky?" |
|Andrew Halliwell BSc(hons)| |
| in | "I think so brain, but this time, you control |
| Computer Science | the Encounter suit, and I'll do the voice..." |
------------------------------------------------------------------------------

Posted by johninsd at san dot rr dot com on July 20th, 2003


LILO versions earlier than 22.5.3 will have a very hard time figuring out that
/dev/hdc1 is BIOS device 0x80.

disk=/dev/hdc bios=0x80

would be highly recommended in your lilo.conf file.

With the newer versions of LILO (22.5.4++) the disk= line won't be needed, but
insurance for booting windows can be had with:

other=/dev/hdc1 # Win partition
master-boot # This is drive C:

--John




On Fri, 18 Jul 2003 15:49:24 +0200, Jacques Charroy
<jcharroy@club-internet.fr> wrote:


LILO version 22++ links at:
http://freshmeat.net/projects/lilo


Similar Posts