SUSE / openSUSEThis 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.
Ever since I installed Suse 10.0 RC1, my Windows partition has refused to boot, saying that my hal.dll file is missing or corrupt. I tried everything that I could do on the internet but nothing has helped. I tried to use the recovery console in my Windows install disc but then I got a BSOD after everything was configured. My last option was to reinstall Windows but that meant I would have had to reconfigure GRUB to overwrite the MBR Windows would have wrote.
When I read the GRUB documentation, I found that I could install Windows after installing Linux by creating a bootable CD option in GRUB and installing it from there. I used YaST to configure GRUB to create a CD option but I'm not sure what device I should link it to. I tried the device in my fstab file but that didn't work.
Could someone tell me which device I should link the CD option to so that I could boot off of my Windows CD to gain access to the recovery console or to reinstall Windows?
/dev/fd0 is the floppy drive which is already configured in GRUB. I need the CD drive. I've already tried /dev/cdrecorder, /dev/cdrom, and dev/hda and everytime it says, "Error 23: Error while parsing number"
I'll consider that but I want to recover Windows first before reinstalling it. Besides, it sounds a lot simpler adding a bootable CD option and installing through that. I could always create a bootable floppy but the only other computer that I have running is a laptop without a floppy drive but I could always make one when I go home this weekend. Though do they come with a recovery console?
As far as I know, you can use the existing installation or boot CD's you may already have. Once they detect an installed system, they should give you the option 'Boot from harddrive'. Meaning you don't need to create such a CD.
Even more, you can use the installation CD to restore grub to include both Windows and Linux in the boot menu.
Originally posted by saikee The Windows MBR can be restored by booting to a DOS floppy with fdisk.exe inside and type
It does the same job as an installation CD.
I think this is where I went wrong earlier tonight. I Had set up a partition under windows and tried to install FC4. When I went to reboot, I got a grub prompt, but didn't know what to do. I figured my win partition was gone so I did a full wipe and (come to find out, a system restore only cleans the c drive, not both c and d (partitions, not drives)) Now, I'm ready to try again. I have searched and searched, but found nothing for my model computer. I will post in the newbie forums and post a link here shortly.
It is sad that most people panic and do not know how to use a Grub prompt.
I can use the same Grub prompt to boot up any of my 50+ systems using almost identical 3 lines of commands regardless if the system is a DOS, Windows, Linux, *BSD or Solaris.
The 3 lines are
where i=disk No. and j=partition No. bearing in mind GRub counts from 0
The only necessary condition for Grub to boot any of them is the target system must have its boot loader in its own partition, which is always the case for a Window, BSD and Solaris. In Linux it can be replicated any time or chosen during installation