Bug 80452 - Anaconda's bootloader configuration doesn't detect Windows XP
Anaconda's bootloader configuration doesn't detect Windows XP
Status: CLOSED CURRENTRELEASE
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
phoebe
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks: 79579
  Show dependency treegraph
 
Reported: 2002-12-26 14:39 EST by Peter van Egdom
Modified: 2007-04-18 12:49 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-27 17:33:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter van Egdom 2002-12-26 14:39:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:

During installation of Red Hat Linux release 8.0.92 (Phoebe) I noticed that
Anaconda's
bootloader configuration did not detect the presence of Windows XP on my harddrive.

The solution for me was to just to do "Add" and point to "/dev/hda1".


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


How reproducible:
Always

Steps to Reproduce:
1. Install Phoebe (RH 8.0.92) on a system with Windows XP.
2. Observe the bootloader config screen.
3.
    

Actual Results:
  Anaconda did not detect Windows XP.

Expected Results:
  Anaconda should've detected Windows XP and put it automatically in the
bootloader menu.

Additional info:

Red Hat Linux release 8.0.92 (Phoebe)
Comment 1 John J. Germs 2002-12-31 20:56:27 EST
Experienced the same with a Win2K install on a 2nd HD.
Tried two seperate installs (one with Grub and one with LILO)
setting it manually as /dev/hdb1 with no success in booting
the 2K install.

I'm not new to Linux so I suspected it would have difficulty, but
I just had to try.  ;)

If everything worked perfect that 2K install would be bye bye anyways.. heh.
Comment 2 Thomas M Steenholdt 2003-01-22 17:35:57 EST
Same results here - the bootloader configurator did find and configure an entry
for an unbootable extended DOS partition though.
Yes i AM aware that it will be very difficult to check if a device is actually
bootable, i'm only hinting at; if the configuration can find a configure an
entry for a vfat device, it really shouldn't be that hard to add the ability to
do the same for any NTFS devices, or...? Instead of DOS call it WINDOWS
Comment 3 Thomas M Steenholdt 2003-01-22 17:36:36 EST
Oh and the above is with Phoebe .93
Comment 4 Jeremy Katz 2003-01-22 19:22:52 EST
Fixed in CVS.  An update disk for 8.0.93 is available from
http://people.redhat.com/~katzj/phoebe-update.img with the fix.
Comment 5 Peter van Egdom 2003-02-27 17:33:24 EST
Confirmed fixed in Phoebe 8.0.94.
Resolving bug with resolution "CURRENTRELEASE"
Thanks!

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