Re: getting LILO to boot windows
From: Luca Pireddu (ilveroluca_at_n.o.s.p.a.m.hotmail.com)
Date: Fri, 26 Nov 2004 18:38:18 GMT
Dr Balwinder Singh Dheeman wrote:
> On 11/26/04 10:35, Luca Pireddu wrote:
>> Hi all. I guess this may be off topic in this newsgroup, but I figure
>> people with experience getting LILO or Grub to work may be able to help me.
>> I need to get my windows installation working to flash my dvd drive. I
>> actually had a dual-boot setup going a while ago (with LILO), but ever
>> since I changed my motherboard (and consequently changed the location of my
>> HDD) I
>> haven't been able to start the windows installation. I have left it like
>> that for a while, but given the current situation I've decided to reinstall
>> it. However, the windows installation doesn't seem to write over the MBR
>> (when I reboot I get my LILO prompt back). I've tried to overwrite the MBR
>> in various ways:
>> * fdisk /mbr
>> * fixboot
>> * fixmbr
>> but the best result has been a message saying "Missing operating system" at
>> boot. I tried getting LILO to start windows, but I just get
>> "Loading Windows(hda1)"
>> and then nothing.
>> Here's my LILO stanza relating to windows:
> That's not enough, pls provide full listing of your /etc/lilo.conf
I've pasted my entire lilo.conf at the bottom of this msg.
>> Windows is set up on /dev/hda1, and the partition is marked active. Here's
> If LILO or Grub is installed in MBR, the active flag is useless.
>> what fdisk says:
>> Device Boot Start End Blocks Id System
>> /dev/hda1 * 1 30476 15359872+ c W95 FAT32 (LBA)
>> What's going wrong here? Right now I'm not even sure where to start
>> looking. Thanks in advance for any help.
> Can you boot your Linux now, even after executing fdisk /mbr et ell?
> where is/was it installed?
> I think after swapping your HDD's you have changed your BIOS setting to
> boot from HDD-1, instead of booting from HDD-0; this on some BIOS's (not
> sure) may swap the id's for your HDD's which WinDOS can't handle.
You're probably right. Here are the details of what happened.
My old motherboard was an Abit kt7a-raid. It had an extra ide controller
providing ide channels 2 and 3 into which had plugged in my hard drives (it
supported ATA-100, while ide 0 and 1 only provided ATA-66). My primary disk
showed up as /dev/hde. To get things to boot I had the following two lines
in my LILO configuration:
On my new mb the same primary disk is on ide 0 (it shows up as /dev/hda) so I
use no drive id remapping.
Here's what happens when I try to use the windows tools to get it to boot.
1. windows installation -> I still get the LILO prompt on boot
2. fixboot -> I still get the LILO prompt on boot
3. fdisk /mbr -> the computer stops when it's time to boot from the disk.
It's not frozen (I can toggle caps lock and num lock, reboot with
alt+ctrl+del) but it just sits there.
4. fixmbr -> gives me the msg "Missing operating system"
I can boot my original linux installation (I had to change all references
to /dev/hde to /dev/hda).
I've also blanked the entire windows partition in hopes of removing any hidden
reference to the old setup.
Thanks for your help
------------------ /etc/lilo.conf ---------------------
[fidele luca]# cat /etc/lilo.conf
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# Support LBA for large hard disks.
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
# Specifies the device that should be mounted as root. (`/')
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
# Specifies the location of the map file
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
# Boot up Linux by default.
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.