michael norman wrote:
Anyway, now I need to learn enough about GRUB to add the WindowsXP drive.
When I dual booted SUSE (most recently 12.3) and using legacy GRUB it picked up the Windows partition and added it automatically. If it didn't I just went into YAST and added it.
FWIW I always change to GRUB legacy from the default GRUB2 simply because that's what I know how to use. All of this is simply accomplished on installation first thing I untick is automatic installation and after that review every option to find what you want/prefer.
Apologies if others have covered any of this, I haven’t read every word of the thread.
When I started, I had a fully independent WindowsXP drive. It would boot all by itself. Yesterday when I reinstalled SUSE13.1 on its own drive, and had the Windows drive plugged in, it added the Windows drive to grub.cfg. But now I discover the following: 1. If I leave the Windows drive /out/ of the BIOS order and leave the SUSE drive /in/ the BIOS order, the Windows drive appears in the GRUB splash screen but will not boot. 2. If I leave the SUSE drive /out/ of the BIOS order /entirely/ and leave the Windows drive /in/ the BIOS order, the same GRUB splash screen appears, and everything will boot. It sounds as though the SUSE install wrote the MBR to the Windows drive and the SUSE drive. Is this correct? If so, this really ticks me off. I specifically selected in the install that the boot loader gets written to the SUSE MBR. I wanted the Windows drive to remain uncorrupted. I expected to have to add the piece of drive re-mapping code to grub.cfg so that Windows would boot. That re-mapping stuff is not in grub.cfg. -- 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