[Bug #486] map doesn't work in some environments

[nobody]

=================== BUG #486: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=486&group_id=68

Changes by: Anonymous user        Date: 2002-Aug-12 19:11

------------------ Additional Follow-up Comments ----------------------------
I have found a 'map' related issue with grub 0.90-11.

I have 2 hard drives: ide channel 1 primary master (linux)
and ide channel 1 slave (win98). 

I can use the bios (ancient ASUS P5A-B motherboard) to boot from what 
it calls 'C' (ide  channel 1 master) or 'D' (ide channel 1 slave).  Either way  
linux or win98 boot ok. 

If I use grub in the MBR on ide channel 1 master, it will not boot the win98 on 
the slave (as expected) unless I use the 'map' command in the grub.conf to 
'swap' the drives around.  

However, even though I can get grub to boot win98 this way, the resultant win98 
environment is broken. The win98 drive (Quantun CR8.4) on ide channel 1 slave 
is chopped up  into three partitions which come up normally as C: D: and E:. If 
I use grub on the MBR of the master to boot win98, it comes up with C: D: E: F: 
and G: .  C: is ok, but D: & E: and don't work at all, and the 'real' 2nd and 
3rd partitions are now mapped to F: and G:.

If instead of using grub I use lilo, this fault does not occur, i.e C: D: and 
E: come up normally. Also, when booting to the win98 disk from lilo, no screen 
messages appear that you would'nt normally see, but when using grub the 'map' 
instruction appear on the screen in between the various win98 splash screens as 
they come and go before it finally takes over properly. 





=================== BUG #486: FULL BUG SNAPSHOT ===================


Submitted by: okuji                     Project: GNU GRUB                       
Submitted on: 2002-May-28 17:26
Category:  Booting                      Severity:  Ordinary                     
Priority:  Low                          Bug Group:  Software Error              
Resolution:  None                       Assigned to:  None                      
Status:  Open                           Release:  0.92                          
Reproducibility:  Intermittent          Planned Release:                        

Summary:  map doesn't work in some environments

Original Submission:  The command "map" seems not to work properly in some 
environments.
Little is known about this problem. Someone who experienced the problem
actually should address the problem. Otherwise, I cannot do anything
with the problem.

Okuji


Follow-up Comments
*******************

-------------------------------------------------------
Date: 2002-Aug-12 19:11             By: None
I have found a 'map' related issue with grub 0.90-11.

I have 2 hard drives: ide channel 1 primary master (linux)
and ide channel 1 slave (win98). 

I can use the bios (ancient ASUS P5A-B motherboard) to boot from what 
it calls 'C' (ide  channel 1 master) or 'D' (ide channel 1 slave).  Either way  
linux or win98 boot ok. 

If I use grub in the MBR on ide channel 1 master, it will not boot the win98 on 
the slave (as expected) unless I use the 'map' command in the grub.conf to 
'swap' the drives around.  

However, even though I can get grub to boot win98 this way, the resultant win98 
environment is broken. The win98 drive (Quantun CR8.4) on ide channel 1 slave 
is chopped up  into three partitions which come up normally as C: D: and E:. If 
I use grub on the MBR of the master to boot win98, it comes up with C: D: E: F: 
and G: .  C: is ok, but D: & E: and don't work at all, and the 'real' 2nd and 
3rd partitions are now mapped to F: and G:.

If instead of using grub I use lilo, this fault does not occur, i.e C: D: and 
E: come up normally. Also, when booting to the win98 disk from lilo, no screen 
messages appear that you would'nt normally see, but when using grub the 'map' 
instruction appear on the screen in between the various win98 splash screens as 
they come and go before it finally takes over properly. 






No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=486&group_id=68