GRUB.EXE is completely grub, but refines, so that it can run in DOS. So, Grub.exe has all the excellent features of the GRUB you are familiar with. Currently, the latest stable version of GRUB_FOR_DOS 0.0.8 can be obtained from here:
ftp://ftp.cosoft.org.cn/incoming/grub_for_dos-0.0.8.tar.gz
Or enter the directory view: ftp://ftp.cosoft.org.cn/incoming/
Version 0.0.8 can also be safely running GRUB.exe in the drive map (can be nested multiple times). The method used is that the previous drive mapping is automatically uninstalled while running Grub.exe, and the old BIOS INT13 interrupt vector is restored. The development version (for example, version 0.1.4) is of course this feature.
After decompression, copy the grub.exe file to the DOS hard disk partition or DOS floppy disk. usage:
Grub --config-file = (hd0, 0) /boot/grub/menu.lst
Or without parameters:
grub
The default configuration file is (HD0, 0) /boot/grub/Menu.lst
-------------------------------------------------- ------------------------------
If the Linux is installed, it cannot be started, and the possible reason is the fault of LILO. At this time, start with a GRUB boot floppy disk to ensure successful startup. If you don't have a GRUB boot floppy disk, use a DOS to boot the floppy disk, plus a grub.exe file, which can also get the GRUB powerful multi-start function.
Incidentally, the floppy disk made by the "DOS boot disk grub.exe" method can be used to start DOS and other operating systems, which is the real "universal boot floppy disk". This floppy disk can also boot DOS when the hard disk cannot boot DOS / Windows, and the GRUB floppy disk created by other methods can no longer be used as a DOS boot disk. The "DOS boot disk" mentioned here can be MS-DOS, or Freedos (by way of Freedos Build 2029 has supported Win98's FAT32 Masseat format).
-------------------------------------------------- ------------------------------
Another situation: When you reinstall Windows, Windows will rewrite MBR to erase the LILO or GRUB startup code. With Grub.exe, you can start other operating systems without the floppy disk (assuming your Windows is 9X, or DOS is installed on your hard disk).
With loadlin.exe, you can start Linux, but LoadLin requires a kernel file (VMLinuz), which must be in DOS / Windows partition, sometimes this kernel file is not suitable as the kernel of your newly installed Linux system. Grub.exe has no such restriction, it can give you a lot of freedom, it starts from DOS, and you can find any files from the Linux partition (including kernel files), you can easily know that this kernel will be guided by you. It is matched to guide the Linux system.
Loadlin.exe is also a Linux boot device that can be used without installing. Grub.exe is different from that it is a boot manager that can boot other operating systems. -------------------------------------------------- ------------------------------
Search for details on GRUB in the search engine (http://www.google.com/). Here is just a very common simple example, command line operation:
GRUB> Find / Boot / VMLinuz
(HD0, 7)
GRUB> root (HD0, 7)
GRUB> kernel / boot / vmlinuz root = / dev / hda8
GRUB> Boot
Simply a few grub commands, you can start Linux, very convenient? By the way, the grub's Find command is very good, and GRUB has even a CAT command to display a file content. Under the GRUB's prompt, you can get online help. The partition number (HD0, N) of GRUB is generally Linux / DEV / HDA (N 1), for example: (HD0, 7) is / dev / hda8, if you are a SCSI hard disk, / dev / sda8. A special case is that when there is no IDE primary disk in your system, only one slave plate on IDE 0, GRUB displays (HD0, 7) will be Linux / dev / hdb8, that is, GRUB found A BIOS hard drive (HD0) is / dev / hdb in the system. A complex example:
Find the location of the kernel file in the system:
GRUB> Find / Boot / VMLinuz
(HD0, 7)
If you use a separate boot partition, you need to use
GRUB> Find / Vmlinuz
Come look for. Assume that the result found is
(HD0, 6)
Reconfers what root partition in the system:
Grub> Find / Sbin / Init
(HD0, 7)
The command to start the kernel is:
Grub> kernel (HD0, 6) / vmlinuz root = / dev / hda8
GRUB> Boot
If you (HD0, 7) is not / dev / hda8 but / dev / hdb8, you try it:
GRUB> KERNEL (HD0, 6) / vmlinuz root = / dev / hdb8
GRUB> Boot
The partition number is accurate, only the hard drive may have change. The IDE hard disk has only 4 changes, HDA, HDB, HDC, HDD, one test, can always succeed. Of course, if you are a SCSI hard drive, you need to test It is SDA, SDB, SDC, SDD, etc.
Of course, GRUB also supports menu operations. GRUB.EXE The default menu profile is (HD0, 0) /boot/grub/Menu.lst, as mentioned earlier, the location of this configuration file can be re-specified by the DOS command line parameter. The partition (default (HD0, 0)) of this file can be the DOS / Windows FAT12, FAT16, FAT32, or the type of linux EXT2, and other partition types supported by GRUB. By the way, the new version of GRUB will support the ISO9660 disc format, NTFS file system, and the use of floppography img files to boot the machine (especially suitable for users who do not have floppy disk to start the machine).
-------------------------------------------------- ------------------------------
Remind, Google is very powerful: Type GRUB.EXE in the http://www.google.com/ Search box to quickly find the web page. -------------------------------------------------- ------------------------------
Attached: RedHat and Mandrake's hard drive installation method
Assuming your (HD0, 0) [that is, / dev / hda1 partition] is a DOS partition, and your ISO files are already in this partition. You have created a boot subdirectory in the root of this DOS partition, created a grub subdirectory in the boot directory, and add a name called Menu.lst in the GRUB directory, as follows:
Default = 0
TIMEOUT = 30
Title Red Hat 9 Hard Disk INSTALL
root (HD0, 0)
Kernel / boot / vmlinuz-redhat9
Initrd /boot/initrd-redhat9.img
Title Mandrake 9.1 Hard Disk Install
root (HD0, 0)
Kernel /Boot/vmlinuz-mdk9.1 ramdisk_size = 128000 root = / dev / ram3 automatic = method: disk ACPI = Off VGA = 788
INITRD /BOOT/HD-MDK9.1.RDZ
Title Mandrake 9.1 NetWork Install
Root (HD0, 0)
Kernel /Boot/vmlinuz-mdk9.1 ramdisk_size = 128000 root = / dev / ram3 ACPI = Off VGA = 788
Initrd /boot/network-mdk9.1.rdz
Title Mandrake 9.1 HDCDROM_USB INSTALL
Root (HD0, 0)
Kernel /Boot/vmlinuz-mdk9.1 ramdisk_size = 128000 root = / dev / ram3 ACPI = Off VGA = 788
INITRD /BOOT/HDCDROM_USB-MDK9.1.RDZ
Title Mandrake 9.1 CDROM INSTALL
root (HD0, 0)
Kernel /Boot/Vmlinuz-mdk9.1 ramdisk_size = 128000 root = / dev / ram3 automatic = method: CDROM ACPI = OFF VGA = 788
Initrd /Boot/cdrom-mdk9.1.rdz
Title Windows
Rootnoverify (HD0, 0)
ChainLoader 1
Title Chainlined The Old Mbr, That IS, The Original Mbr
Rootnoverify (HD0, 0)
ChainLoader (HD0, 7) /BOOT / BOOT.0300
Oh, a small episode: The last paragraph (HD0, 7) is assumed to be your Linux root partition. The Linux installer generally saves the MBR before the installation in the /boot/boot.0300 file of the Linux root partition, and we just borrow it to boot the original operating system. This may be useful for systems such as Windows XP. With this way to guide Win XP, it should be no longer lost (provided that the boot.0300 file is the copy of the MBR main boot sector when WinXP can be guided, and the process you install Linux does not change WinXP partition, for example, just on the hard disk Add a new Linux partition in the idle space of the tail. Note that in the boot directory, there should be REDHAT and MANDRAKE VMLinuz and Initrd files, and their names can be arbitrary, just guarantees that redhat and Mandrake's file names are not conflict (not covered with each other). These files can be found from the first CD of Redhat and Mandrake. On the disc, Redhat is called VMLinuz and Initrd.img, while Mandrake is called VMLinuz and HD.Img, Network.img, and more. You need to continue to remove VMLinuz and HD.RDZ and Network.rdz files from HD.IMG or NetWork.IMG. [Redhat doesn't need to be so troublesome, the initrd.img file is directly on the disc].
Ok, run GRUB.EXE from DOS, the installation menu should be present on the screen. Very cool?
-------------------------------------------------- ------------------------------
Since Mandrake's installer cannot automatically find CD2 and CD3, the installation is slightly complicated with ISO file installation. For this question, I like this to solve:
Use a CD1 to install a basic system. When you encounter the mistake of "can't find the file", press "Continue to install". After the installation is complete, enter a terminal knock into the command (description: RC3 is exactly the same as the official version):
MKDIR / MNT / CD1
MKDIR / MNT / CD2
MKDIR / MNT / CD3
Mount -o loop mandrakelinux-9.1-rc3-cd1.i586.ISO / MNT / CD1
Mount -o loop mandrakelinux-9.1-rc3-cd2.i586.ISO / MNT / CD2
Mount -o loop mandrakelinux-9.1-rc3-cd3.i586.iso / MNT / CD3
Then enter the "KDE menu" - "Settings" - "Mandrake Control Center", you need to knock into the root password. Click Software Management in the left bar, then click the icon with the Software Manager to help you define where to download the package. Click "Add" in the Configuration Source dialog that appears. In the "Add A Source" dialog box, there is a "name" bar, you enter "CD1", there is a "path" bar, you entered "/ MNT / CD1", the source type default is "local file", do not change it. There is also a "relative Synthesis / hdlist path" column, let it be empty, don't fill anything. Ok, click "OK".
For CD2 and CD3, similar processing is made.
After completing, click "Save and Exit". Then go to the Mandrake Control Center, click "RPMDrake" in Software Management, you can see the package in three ISO files in "Software Management", wait a minute, you can see the package in the three ISO files, you can choose to install it. . =========================
