![]() ![]() You were not only SLOWER, you also posted an invalid link! I never said that you had to click on it. iso emulation UNLESS it has been "designed/built" for it or anyway uses already a "comaptible" boting mechanism. iso can be mapped and booted through grub4dos. Hope to have contributed to clear the point that NOT "ANY". Only SOME distros/builds can be loaded with. This is the reason why I started this thread: iso mapping, like Parted Magic, most miss this mechanism. Some distros have been built with a mechanism that allows this kind of booting, a few with the actual idea of being booted by grub4dos through. Some modifications need to be made on the Linux side. ![]() Initrd /initram.igzONCE the ROOT has been established.īut once the initial ramdisk has been loaded, the Linux distro needs to know HOW/WHERE from to load the rest of the files.īut it probably WON'T work as well as INSIDE the Linux distro there is NOT a provision to find and load the boot volume (or the files in it). In Linux this is as well given by drivers, things are easier than in Windows NT, but still you need to give to the build some hint on HOW to mount the booting volume, and WHERE it is. In Windows NT this is given by a DRIVER that takes control of the source of booting, a PE 2.x has this mecahnism automated, whilst PE 1.x need the RAMDISK.SYS mechanism or the Diskless Angel or however another Mass Storage Driver capable of giving access to the booting volume. Windows NT and Linux need some mechanism to "hook" the - in this case only temporary - info. Thus anything mapped or re-mapped in grub4dos is ONLY valid during the booting phase when the BIOS info is trusted.ĭOS based things work allright, as the BIOS is always trusted. Grub4dos mapping actually replaces (temporarily) the BIOS. Linux does more or less the same, but not exactly. Windows NT based systems starts in "real mode", trusting the info the BIOS gives it, then switches to "protected" mode, when the hardware is re-scanned and "protected mode" drivers load. "trusts" the info the BIOS gives it, and Windows 3.x/9x/Me though having a "protected mode" still trust the BIOS. It's booting mechanism is different from that of a Windows based build.īut there are some points in common that maybe we can try to clarify in this particular occasion.Īn operating system has basically two modes (exception made for DOS, see later) "real mode" and "protected mode".ĭOS has ONLY "real mode" i.e. The above is completely OFF-TOPIC, exactly as steve6375 post. I use a lot of hot pepper on my linguine al pomodoro. I use this for WinPE v2 ISO - if 1 does not work then try 2 or 3 (you will need to change BOOTMGR to bootloader file used in your iso ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |