Grub4dos Hard Drive boot ISO file

1. First Success
there are cases on the Internet that have successfully used grub4dos to guide ISO files, I tried to guide winpe's ISO file but it never succeeded.
the dostoolbox for waste guest is installed on Virtual Machine XP, and isogrub is extracted from the installation directory. put the ISO file in the root directory of any disk, in the menu. run the following command to write an LST file:

======================================
Title find and boot isogrub. ISO
Fallback 1
Find -- Set-root/isogrub. ISO
MAP/isogrub. ISO (0xff) | map -- MEM/isogrub. ISO (0xff)
Map -- hook
Chainloader (0xff)
Savedefault -- Wait = 2
======================================
Restart the computer and use grub4dos to guide the system. Winpe is successfully started. So I went to the real machine to test the blue screen when entering the desktop. It seems that the reason is that this winpe is not compatible with my hardware.
After all, grub4dos is used to successfully guide the ISO file, which demonstrates the feasibility of this method.

 

2. Since the ISO file of winpe downloaded for direct guidance is unsuccessful, the reason should be that these ISO files are not suitable for grub4dos boot. Use grub4dos to guide the ISO file of the ghost system CD of winpe. The command written in menu. lst is:

====================================
Title find and boot WINXP. ISO
Fallback 1
Find -- Set-root/WINXP. ISO
MAP/WINXP. ISO (0xff) | map -- MEM/WINXP. ISO (0xff)
Map -- hook
Chainloader (0xff)
Savedefault -- Wait = 2
====================================
It was successful once.
The ghostxp computer company edition was successful, and the same version was successful.
In addition, this ISO file does not have to be placed in the Windows partition, but is also successfully placed in the LINUX partition. My LINUX partition is an ext4 file system.

 

3. Accidentally boot the ISO file of the win7 installation CD.
Two boot menus are written in menu. lst:

==============================================

Title find and boot WINXP. ISO
Fallback 1
Find -- Set-root/WINXP. ISO
MAP/WINXP. ISO (0xff) | map -- MEM/WINXP. ISO (0xff)
Map -- hook
Chainloader (0xff)
Savedefault -- Wait = 2

Ttitle installwin7
Find -- Set-root/7600.16385.090713-1255_x86fre_client_zh-cn_retail_ultimate-grmculfrer_cn_dvd.iso
MAP/7600.16385.090713-evaluate (0xff) | map -- MEM/7600.16385.090713-1255_x86fre_client_zh-cn_retail_ultimate-grmculfrer_cn_dvd.iso (0xff)
Map -- hook
Chainloader (0xff)
Savedefault -- Wait = 2

========================================================== ============

The first section can directly guide an XP ghost image.
The later section is intended to guide the installation of the CD-ROM image of win7, but mistakenly writes the title as a ttitle, so that the later section is mixed with the previous section. Click find and boot winpe. ISO in the boot menu. Instead of the ghost, the image is started directly. I corrected this error and reported an error when I clicked installwin7. Cannot start. Dizzy! It seems that mistaken hits have solved a problem that many senior people cannot solve.
Do not think that you can install win7 in this way. In this way, you can only start the winpe system that comes with the win7 installation CD. You cannot enter the Sources folder on the installation CD, so you still cannot start the installation directly from the ISO file.Program. After removing the win7 optical disk, run the setup.exe program under sources.

In addition, winpe started by guiding the ISO file generally cannot load external programs (this is mainly because some winpes did not consider using this method to start ), you need to first put some external programs in accessible windows partitions.

Grub4dos boot to load ISO is one-time, so it is impossible to directly use it to guide the WINXP and win7 installation CD for system installation. In fact, the previous successful boot of the win7 installation CD is just to guide the loading of winpe in the win7 installation CD.

Note that, in order to boot successfully, files must be stored continuously on the hard disk.

Because this method of boot is only the pe that comes with the CD, and the files must be stored continuously, such a boot method has no practical significance. There are available ISO file downloads for win7pe on the Internet. You can download it for direct guidance. In addition, you can use ultraiso to open the image of the win7 disc and keep only the bootmgr file, boot folder, and all the files in it. Retain the Sources folder and the boot. Wim file. Delete all others. Save it as a standard ISO file.

4. Boot and install ubuntu9.10, place the downloaded image file in the root directory of any disk, and write the following command in menu. lst:

Title install Ubuntu
Find -- Set-root/ubuntu-9.10-desktop-amd64.iso
MAP/ubuntu-9.10-desktop-amd64.iso (hd32)
Map -- hook
Kernel (hd32)/Casper/vmlinuz boot = Casper iso-Scan/filename =/ubuntu-9.10-desktop-amd64.iso
Initrd (hd32)/Casper/initrd. LZ
Boot

However, there is a key point here. The method I use here is
MAP/ubuntu-9.10-desktop-amd64.iso (hd32)
This method requires files to be stored continuously on the hard disk.
Use the following statement:
Map -- MEM/ubuntu-9.10-desktop-amd64.iso (hd32)
This method does not require files to be stored continuously on the hard disk. It reads the entire file into the memory. This file is only about 1.5 MB, and my memory is GB. Normally, it should be successful. However, my practice fails. There are two possibilities: memory is not large enough. Another is not because of memory. This is because the file cannot be read after boot. Therefore, the installer cannot continue. It seems that this is basically the second reason.

How do I know that files are stored continuously on the hard disk? Run the following command in grub4dos:
Blocklist filename
For example:
Blocklist/ubuntu-9.10-desktop-amd64.iso
My display result is:
(Hd0, 8) 640 + 1414752
This indicates that there is only one block. If it is followed by a comma, for example:
(Hd0, 8) 640 + 1414752,1515752 + 8
These two blocks are not stored consecutively.
My experiments show that as long as the files are not stored continuously on the hard disk, using map without the -- Mem parameter will fail. Therefore, this method is not good for booting and installing ubuntu.

5. possible causes of failure.
The information found on the internet is as follows:

==================================
If the boot fails, the possible causes are:

(1) The CD-ROM File System of the CD image is Joliet CD format, grub4dos does not support this format. You need to use a tool to convert the file system format of the image file.
(2) the SATA ahci mode is activated in BIOS. Grub4dos may not be compatible with the ahci mode. Set the SATA mode to ide In the BIOS.
====================================

Later experiments showed that I used the ultraiso tool to convert an ISO file of winpe that could not be successfully guided into a standard ISO file, which was successfully guided.
The latest grub4dos is compatible with the ahci mode, which is proved on my machine. Therefore, if the ISO file cannot be successfully guided, the problem is that the file system format of this ISO file is not supported by grub4dos. Use ultraiso to convert it to a standard ISO file.

In addition, replace 0xff in the Command written in menu. lst with hd32 can also be successfully guided, for example:

Title winpeboot. ISO
# Fallback 1
Find -- Set-root/winpeboot. ISO
Map -- MEM/winpeboot. ISO (hd32)
Map -- hook
Chainloader (hd32)
Savedefault -- Wait = 2

 

In the end, it is particularly noted that the grub4dos can be easily used to guide the winpe of the ISO file, which makes the hard disk boot and installation of windows in Linux no obstacle.

PS: It is difficult to store files continuously on the hard disk. Therefore, the file has to be fully read into the memory, which requires that if the memory is not very large, the ISO file used for guidance cannot be very large.