On Saturday 13 December 2008 14:38:43 Joe Morris wrote:
I suspect it is correct, but Windows is looking at disk1 for its boot files and cannot find them there.
I don't want to look like an idiot to my manager, and I was hoping that my experiment might eventually lead to our using Linux for a lot of our file and printer servers, not just my machine. Seems like every week that we need to install updates that require rebooting the servers.
Hope this helps you in your quest.
Thanks to both you and Rajko. I used the SuSE installation disk to 'repair' my bootloader, and I think I got it right. Since I knew the second disk (original disk D:) isn't bootable, I just opted for the first one, and called it 'Windows'. The results from that were the same as before. Then I unplugged the new disk, and GRUB was still started, so it was apparently installed on the original Windows drive C:. I'm at home, and this system is at work, but I'm going in to the office tomorrow to see if I can make it work from the BIOS. I'd like to AT LEAST get it booted so that I can backup the C: and D: Windows drives. I started to do that first, but with a 250 GB and a 500 GB drive, it would have taken hours. And I had no reason to distrust my previous Linux experience with dual-boot systems. You're probably right about changing the boot order. When I've done this before, I don't believe the new drive became the first drive. That's probably the whole difference. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org