Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a Pentium 4 with 2GB memory and 3 SATA drives. My first drive had Vista loaded and on the second I had UBUNTU 6.10. They were working fine until I decided to Install SUSE 10.0 on the third drive as I had it before and wanted to get back to it. The installation went fine except that GRUB loader that SUSE installed has an entry for Windows and bombs with ERROR 15 when I tried to access it. I can boot UBUNTU and SUSE from the menu no problem. How can I get back to accessing the windows. Vista had a root entry (hd0,0). Many thanks.
From the information you give, I assume that when you installed Suse, you elected to install Suse's grub to the MBR instead of the the root of the Suse partition. Now it's broken; reason unknown.
Easiest way to fix this, boot Ubuntu from the install cd. Re-install Ubuntu's grub to the MBR. Before doing anything else, mount the Suse partition and open Suse's /boot/grub/menu.lst and copy the menu entry for Suse (you will have to either add the Suse partition to /etc/fstab, or just create a mount point for it for a one-time mount). Close that file, then open Ubuntu's /boot/grub/menu.lst and paste the Suse entry there.
Reboot. Try all three OSs to see that they are all bootable.
Come back here with any problems you have. Also post the menu.lst entries for all three OSs.
I looked at VistaBoot but I wanted to try and fix myself..
I did find the problems however.. When I did an upgrade of XP to Vista I was able to go into Vista and Linux using Grub without an issue (after re-installing grub).
After a Clean install of Vista and re-installed grub, I was unable to log on with the winload error.. What was the problem? Well for some reason vista put the boot stuff on D although I installed on C (D was the bigger partition)..
Once I got all that cleared out with bcdedit, etc. I was a ok to go, and now have both..
The reason for the problem: ntldr has been depricated in favor of the new un-linux friendly winboot.exe. I've read in a few places about the hoops that must be jumped through to get a dual-boot with vista to work...
saikee, I have read that the final RTM version of Vista does give GRUB problems. I am guessing your posts (from the dates) are the Release Candidate version? I have had no problem booting either RC1 or 2 but would be interested to hear if there is really a problem with the final.
Yep, mine was a free version. It is possible Vista would try to make it harder for Linux boot loaders to boot it but it will affect the NT versions of Windows, BSD and Solaris too, especially if it deviates from the established PC standard. No matter what it does it cannot survive without a MBR section as no Bios would read more than that.