Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 really annoying problem. I've reinstalled my whole system, starting with WinXP on the first partition. Then a FAT32 partition #2. Then I installed SuSE 9.3 on the third partition. Unfortunately, YaST did not configure WinXP as a boot option, so now I can't get into WinXP.
I have tried, from information gathered in this forum, to manually edit the grub boot file thing. This is what it looks like:
# Modified by YaST2. Last modification on Thu Sep 29 20:00:26 BST 2005
color white/blue black/light-gray
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.3
kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 selinux=0 splash=silent resume=/dev/hda4 showopts
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 9.3
kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3
###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Memory Test
As you can see, I added the last two lines myself. Unfortunately, when I try to boot into windows, an error message comes up about NTLDR.exe missing, or something like that. I then went to check for the boot.ini file on BOTH the WinXP partition and the FAT32 partition. Using Konqueror, I selected "show hidden files/folders", but boot.ini is not there!
So, I was wondering could anybody tell me what I need to put into the grub file for grub to directly load WinXP without using the windows bootloader, if that makes sens
GRUB is supposed to relocate NTLDR and NTDETECT.com. GRUB replaces BOOT.ini with itself. Boot from the SuSE 9.3 CD, or DVD and select "Install". When it asks you, select "Repair Installed System". Install the bootloader, GRUB, again. That's in expert tools. But first configure the entry:
title MS Windows XP
in the configuration files
You'll see how to do it.
There is an edit button on the lower left of the reinstall bootloader screen. Install the bootloader to the MBR, and replace MBR code.
Originally posted by AwesomeMachine GRUB is supposed to relocate NTLDR and NTDETECT.com. GRUB replaces BOOT.ini with itself...
To the best of my knowledge, neither comment is true. The grub commands I listed above do not modify anything in the windows partition and neither does installing grub to the Master Boot Record (MBR).
You may be confusing how grub functions when written to “the first sector of the boot partition” in a linux partition, with how it functions when grub stage-1 is written to the MBR.
The critical things that the grub commands do when booting windows is (1) to load the first sector of the windows partition (i.e., the boot sector) and (2) to start the execution of the code contained in the boot sector. Windows is responsible for creating the boot sector contents of a windows partition, not grub.
Grub’s job in booting windows is to substitute for the process normally carried out on a windows-based system after the Master Boot Code is loaded from the MBR and is executed.