Tony Alfrey wrote:
Carlos E. R. wrote:
On 2014-06-21 20:15, Tony Alfrey wrote:
This totally sucks!!. It means that my Windows disk is dependent on the existence of the SuSE disk. If I pull the SuSE disk out, and try to boot the Windows disk, grub in the Windows MBR looks for the Windows disk as sdb when it now the /first/ drive in the system!
Not exactly.
Grub, installed in the first disk (using the MBR sector, and some hidden sectors on the first track) has inside coded to transfer control to the boot partition of the second disk. Missing this disk, nothing can boot. Missing the first disk, same thing. Changing the disks ordering, problem.
That is, grub is half on one disk, half on the other.
There is a complete grub on the SuSE drive as far as I can see. I pulled the Windows IDE drive and grub comes up nicely with the menu of the drives and I select SuSE and linux boots. So I think that all I have to do is put in the Windows drive, pull out the SUSE drive and restore the MBR on the Windows drive.
Then fix the grub.conf file on SuSE to add the mapping thing that make Windows think it's the first drive.
Comments?
Let me just add one comment/question: If the Windows drive will boot independently all by itself w/o any help from grub, why would grub need to /add/ anything to the Windows drive to boot it. Let me just add that this is the first time I've ever used grub. I've used LILO forever. All one does is map the drive numbers correctly in lilo.conf, run /sbin/lilo and you are done. Windows boots. IMHO, LILO is the simplest thing since sliced bread. If I knew that I would not break something, I'd put in a lilo.conf file that I KNOW will work and run /sbin/lilo and be done with it. I actually may try just that now that I know that, eventually, I can install SuSE 13.1 -- 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