Felix Miata wrote:
On 2014-06-22 09:32 (GMT-0700) Tony Alfrey composed:
I did it!
About time!
I have two drives;
That we knew.
1. a SATA drive plugged into a PCI card.
There's another detail I don't recall seeing you mention before. Mixing HDs on addin cards and on motherboard controllers complicates things. They may get further complicated if the addin card has its own option whether to be bootable or not.
Grub2 thinks it is hd0, SuSE is on the first partition.
2. an IDE drive plugged into the first IDE port on the motherboard. Windows is on the first partition. Grub2 thinks it is hd1.
In BIOS, the order is Floppy CDROM SCSI (the bios thinks that the SATA card is a SCSI drive)
That's an old motherboard, right? There didn't exist SATA cards way back when. Calling addin HD controllers SCSI has to do with the way they are handled by the BIOS, a legacy going back to the '80s before IDE displaced MFM and RLL, and no HD controllers on motherboards existed. BIOS typically gave preference to bootable SCSI over MFM, RLL and later IDE, a preference typically still present in recent years and all years since IDE "controllers" began appearing built into motherboards.
If I replace SCSI with HD0, Windows boots all by itself. Otherwise (if BIOS is as shown) I see a Grub2 boot screen with the selections that SuSE installed; a SUSE 13.1, an advanced features SUSE 13.1 and a Windows XP selection which doesn't boot.
This BIOS setup should have been addressed had we known about the addin controller.
The BIOS setup or the SATA card was never really a problem. I played with that back and forth to diagnose what things were going on. It saved my butt because I would not have been able to boot Windows without it. And I always knew what Grub was calling the drives because I could see that in the yast bootloader feature. All that is really necessary in all of that is to know what Grub calls the drives.
Add this menu entry in /boot/grub2/grub.cfg in the "custom entries" section.
menuentry 'Windows XP' { set root=(hd1,1) chainloader +1 drivemanp (hd1) (hd0) boot {
A fourth Windows XP selection appears that boots.
How does that selection differ from the one above?
1. The search feature in Grub2 did not assign the correct drive,partition to root, so I assigned it manually. 2. Windows did not like the two-way drive map drivemap -s (hd1) (hd0) Note the "-s" -- Tony Alfrey tonyalfrey@earthlink.net "I'd Rather Be Sailing" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org