How to remove GRUB loader!?
#1
Posted 12 August 2004 - 07:59 PM
#3
Posted 13 August 2004 - 11:59 AM
Do you have Windows installed already? If so, boot from the CD, enter the recovery console (press R when it asks you whether you want to install windows etc.) When you're at the console, type:
fixmbr
and that will remove GRUB from your system.
If you don't have Windows installed, GRUB will be overwritten as part of the installation.
Rgds
AndyF
#4
Posted 05 September 2004 - 07:32 PM
#5
Posted 06 September 2004 - 10:30 PM
#6
Posted 13 September 2004 - 07:00 PM
zadrras - I'm not sure why fixmbr doesn't work - it's always worked for me in the past. You could try fixboot instead, which will rewrite all of the Windows boot files.
cybersam - I suggested using the Windows install CD becuase the chances of zadrras having a DOS disk spare were slim (I don't have one either) and since he couldn't get into Windows, he couldn't run a command prompt from there either :p
Rgds
AndyF
#7
Posted 25 October 2004 - 12:49 AM
#8
Posted 11 November 2004 - 07:32 PM
You need a boot disk (cd or floppy) with fdisk on it, then run
fdisk /mbr.
This worked for me with LILO and it should work with GRUB.
http://www.nu2.nu/bootdisk/cdrom/
Croma
#9
Posted 22 November 2004 - 04:17 AM
alternatively, you can use grub to help you to boot your windows by directing the GRUB to load your NTLoader.
grub> rootnoverify (hd0,0)
grub> makeactive
grub> chainloader +1
grub> boot
Assuming your Windows is in HDD 1 and partition 1.
grub is a tool helping you to choose which OS you want to load if your machine loaded with multiple OSs.
#10
Posted 27 November 2004 - 05:19 PM
I tried the "fdisk /mbr" & still had Grub showing also.
After checking fdisk again, I noticed the /mbr option had removed the ACTIVE flag.
This seemed to have done the trick for me.
PS: check also http://www.linuxquestions.org
#11
Posted 27 November 2004 - 05:28 PM
http://www.gnu.org/software/grub/grub-legacy-faq.en.html#q12
#12
Posted 09 January 2005 - 05:15 AM
fixboot c:
fixmbr
is you want to change the boot.ini file then execute the command:
bootcfg /rebuild
the last will put a new entry in the boot.ini file.
To do this successfully you should have started your system from the Windows XP CD and selected the 'repair' option.
This also assumes that you have not moved any partitions around, that is in the order or number that they exist on your HDD. If you have then you should execute bootcfg and rewrite the boot.ini file.
You also should be in the root directory, as in 'C:\' not 'C:\windows'.
Please don't ask me why I know this so well. As most people in our industry know so well, sometimes you lear VERY well by experience.
Hope this helps others.
John
#13
Posted 11 January 2005 - 02:33 AM
I have this problem on a XP volume in which GRUB was installed into the MBR/replaced the MBR, and FIXMBR will not remove it or repair the MBR. This is a SATA drive.
#14
Posted 12 January 2005 - 01:04 AM
#15
Posted 12 January 2005 - 06:49 PM
It only worked if I was in the root directory for the instance that I wanted to fix:
example:
when selecting repair function used
C:\WINDOWS
CD ..
FIXBOOT C:
FIXMBR
BOOTCFG /rebuild
after all that I was able to select the new entry from the selection menu.
Like I said, I don't know why you could not get it to work.
Regards,
John
#16
Posted 28 January 2005 - 01:21 PM
I do admire MS software, but one thing that I have noticed throughout the years in supporting, using, developing, and often times enjoying it, is that Windows/MS based apps are the single most intermittent POS available at times. I realize the very broad range of hardware platforms does playa major role in such intermittent"ness" in regards to software/development issues, but now-a-days, in this year of 2005, the hardware platforms we are working with, even for most clones, are almost identical in construction and somewhat regulated and ?standardized?, this obviously due to many years of developer's and engineer's trying to accomplish exactly that, a IBM PC based architecture that runs efficient, with solid performance and reliability, yet somewhat standardized even across multi-corporation/manufacture platforms. This is the #1 reason Macs have 60% less support issues with their OS/Software. Just a thought. Anyways, who likes macs anyway, 5 minutes with a one button mouse, and I will place a large wager in Vegas on the fact that you probably ripped it out of the box and destroyed it in a very understandable and most lilkly enjoyable fit of rage as I did
Anyway, just some thoughts....anyone else
l8
intenzity
_____________________________________________________________________________________
EliTE PEOPLE R0CK, but PUBLIC DOMAIN IS BETER, but why? LOL, EXACTLY Mate.
#17
Posted 28 January 2005 - 01:39 PM
#18
Posted 03 August 2006 - 11:49 AM
I have this problem on a XP volume in which GRUB was installed into the MBR/replaced the MBR, and FIXMBR will not remove it or repair the MBR. This is a SATA drive.
I had the same problem. I have a SATA drive and an EIDE drive. XP always wants to think the EIDE drive is the first, and when in recovery mode it would think the installation was at D:\Windows -> this caused the FIXBOOT/FIXMBR/BOOTCFG combo not to work. When I disabled the EIDE drive and tried again, it worked out fine. Just simplify the process by temporarily disabling extra drives in the BIOS.
#19
Posted 03 August 2006 - 03:12 PM
Originally posted by jbirkett:
CD ..
FIXBOOT C:
FIXMBR
BOOTCFG /rebuild
I noticed that i ended up with a second instance of "Microsoft Windows XP Professional" in the NTLoader when I start up. But that will be quickly removed when I edit the boot.ini file in Windows to remove it.
Thanks!!
===========================================================================
Asus A7N8X
Athlon 2600+ Barton Core
1GB DDR RAM Dual Channel
128MB Radeon 9600XT
Sound Blaster Audigy 2 7.1
hey...It's 3 years old and still holds it's own...
....even up against a brand new DELL XPS!!!
#20
Posted 26 September 2006 - 12:15 AM

Help










