Bug 55509 - Generated grub.conf entry is incorrect for windows 95 installed on /dev/hdb1
Summary: Generated grub.conf entry is incorrect for windows 95 installed on /dev/hdb1
Keywords:
Status: CLOSED DUPLICATE of bug 23643
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-01 15:07 UTC by John
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-11-02 20:20:56 UTC
Embargoed:


Attachments (Terms of Use)

Description John 2001-11-01 15:07:12 UTC
Description of Problem:

If windows 95 is located on /dev/hdb1 when Redhat 7.2 is installed, the   
entry in /boot/grub/grub.conf to boot that os is incorrect.  Win95 does not
boot when the dos entry in grub is chosen at boot.


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


How Reproducible:

Always.

Steps to Reproduce:

1. Install Win95 on /dev/hdb1
2. Install Redhat 7.2 on /dev/hda (or wherever, I guess.)
3. Reboot, and select the "dos" entry in the grub menu.  Windows won't boot.

Actual Results:


Expected Results:


Additional Information:

As much as I hate to fix things to make Windows work, :) here's the way I
updated my grub.conf.  The dos entry is now:

title DOS
        map (hd0) (hd1)
        map (hd1) (hd0)
        rootnoverify (hd1,0)
        makeactive
        chainloader +1
        boot

I think this is the correct fix.

Comment 1 Jeremy Katz 2001-11-02 20:20:51 UTC
Yes, anaconda doesn't currently handle the writing out of any additional drive
mapping information at present.  It is being considered for the next release as
a part of a rework of all of the bootloader configuration present in anaconda

Comment 2 Jeremy Katz 2002-01-22 01:27:01 UTC
grub instead of lilo, but same bug

*** This bug has been marked as a duplicate of 23643 ***


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