Boot is GURB can not enter the system

lower/523200K upper memory) [MINIMAL BASH-like line editing is supproted.For the first word.TAB lists possiable commmand comepetion.Anywhere else TAB list the possoble competions of a dievce/filename.] Now delete a key or GNU GRUB version 0.97 (639K lower/523200K upper memory) [MINIMAL BASH-like line editing is supproted.For the first word.TAB lists possiable commmand comepetion.Anywhere else TAB list the possoble competions of a dievce/filename.] grub> _

It is estimated that you are installing Linux+Windows dual system ……, Grub is not deleted after reinstallation. The solution is to rewrite MBR: After deleting linux, restore a windows 2000 image with ghost. After that, it is impossible to enter the windows startup interface normally, and the Grub boot interface always appears. Later, after rewriting the MBR, the problem is solved. Today, I caught up with the same problem on the germa83 machine. I checked it online and how to deal with similar problems quickly. LILO (or GRUB) is the boot manager for Linux. Most current Linux distributions currently load LILO into the master boot record (MBR) of the primary hard disk. This is why the first screen of the machine boot becomes Linux LILO after installing Linux. When installing Linux, we can ask the installer to install the Linux boot manager to another hard drive or boot floppy to prevent the Linux launcher from overwriting the MBR. However, for users who install Linux for the first time, or users who use the automatic installation mode, it is very likely that the Linux boot manager will not rewrite the MBR. After the MBR was rewritten, the boot module of Windows itself was still not lost, but it is now necessary to access it through the Linux boot manager LILO or GRUB. So, how can I clear LILO or GRUB and return to the startup interface of Windows itself? For a system with only one Windows, it's simple: make a boot floppy containing the FDISK program, boot the machine with a floppy disk, and then execute FDISK /MBR on the command line. This command resets the MBR so that the system starts Windows directly. However, if the system has multiple Windows before installing Linux, running the FDISK /MBR command in this way will override the Windows multi-boot menu so that the machine can only boot from the default primary operating system. To clear LILO or GRUB back to the previous Windows boot interface, the quickest and most reliable way is to use the Windows Recovery Console. The Recovery Console can be accessed from the Windows CD or to the system. If you want to run the Recovery Console from the CD, assuming that the main operating system of the machine is Windows XP, start the machine with the WinXP CD first. When prompted, select Manual Recovery (press R). Installing the Recovery Console directly on the system speeds up processing. First, open the Win XP command line window (select menu <; start & rdquo; & rarr; & ldquo; run & rdquo;, execute cmd); then, insert the WinXP CD in the CD-ROM, run D: i386 winnt32 on the command line. Exe/cmdcons command, where D: is the letter of the CD-ROM drive. After the installation is complete, you can select the Recovery Console from the Windows startup screen the next time you start. If more than one Win XP system is installed on the machine, the Recovery Console will prompt which Win XP to fix. At this point, you should select the last installed system and then enter the administrator's password to log in to WinXP. On the command line, type fixboot and press Enter. Type fixmbr and press Enter. The system prompts that there is already an illegal startup record, so don't bother, just confirm to continue. Restart, the Windows boot menu is back. Or: Is it necessary to let the system boot directly to Windows, without the Linux Grub (or LILO) boot interface (Solution 1~3), or after Windows partition is deleted in Windows, Windows cannot be started correctly, and stays at “ Grub>” What should I do (Solution 4)? Please look down, here are several practical methods for you: Solution 1 Use the DOS command fdisk to restore the main boot sector MBR (Main/Master Boot Record) --- Use win98 boot disk or DOS boot disk to boot the system to pure At the DOS prompt, execute: "fdisk /mbr". Solution 2 On a Linux system, restore the MBR. (If you can still log in to the Linux system) --- At the command prompt of the terminal, type: "dd if=/boot/boot.NNNN of=/dev/hda bs=446 count=1" Where bs (buffer size) refers to the number of bytes rewritten. Why not 512? The main boot sector is a sector (512 bytes) because we just want to fix the system MBR boot or delete the Grub/LILO boot through the fan command; instead of restoring the entire master boot sector. So we only rewrite the first 446 bytes of the backup file boot.NNNN of the primary boot sector to the primary boot sector. boot.NNNN is the backup of the entire primary boot partition before we installed Linux. If we write all 512 bytes to the main boot sector, it may destroy the hard disk DPT table that has been changed after installing Linux. That's a bad thing!!! (MBR's 512 bytes of the first 446 bytes for the bootloader, followed by the next 64 bytes for the partition table, the last 2 bytes for the end tag) Solution 3 If your fdisk is not So, or Linux is already upturned, don't worry, God closes all the doors, but he will leave a window for you, the following tools can help you: Clear MBR 0.9: http://jelle. Go.nease.net/resource/clsmbr.exe --- directly run the implementation "Clear MBR", I have tested, absolutely safe, please rest assured to use. The Solution 4 Linux partition has been removed from Windows and stopped at the “grub>” prompt after the system boots. (Method 1: Follow the Solution 1 method, Method 2: below) --- At the “grub>” prompt, type: <;rootnoverify (hd0,0)” Enter. //Set the first partition (0) of the first hard disk (hd0) as the root partition/root device, but do not load the file system. --- At the “grub>” prompt, type: <;chainloader +1” Enter. //Transfer the bootstrapping authority to the first sector of the current partition (the first sector of the partition where the Windows system is located). --- At the “grub>” prompt, type: “boot” Enter. The system will start Windows. If it is unsuccessful, it means that (hd0,0) is not the partition where the Windows system is located, and then try the first step from the first step (root (hd0,1)/root (hd0,2)/root (hd0,3)/.. .”, in short, this will definitely boot your Windows system. --- Well, enter Windows, please use Solution 3 method, easy to get!