Bug 70704 - Selecting installation of lilo to first sector of mbr isn't working with Windows XP
Selecting installation of lilo to first sector of mbr isn't working with Wind...
Product: Red Hat Linux
Classification: Retired
Component: lilo (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-08-04 07:57 EDT by Need Real Name
Modified: 2007-04-18 12:45 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-04 07:57:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-08-04 07:57:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 

Description of problem:
When selecting to install lilo into the first sector of mbr Windows XP loads 
automatically and the lilo selection screen does not load at all. This problem 
is fixed when selecting the first option in the installation.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Select 'Install to first sector of mbr' in the bootloader part of the 
2. Finishing the installation successfully.
3. Rebooting the computer and seeing Windows loading automatically.

Actual Results:  Windows loads automatically with no sign of wither lilo or 

Expected Results:  The lilo boot screen should have appeard, allowing me to 
select whether I want to boot linux or windows.

Additional info:
Comment 1 Jeremy Katz 2002-08-04 11:33:08 EDT
No, installing the boot loader to the first sector of the boot partition leaves
what was previously in the MBR (the NT loader as used by XP).  You must install
to the master boot record if you already have an OS booting from the MBR.

Note You need to log in before you can comment on or make changes to this bug.