中国DOS联盟

请问各位高手,我在试用ISO镜像文件引导系统时遇到的问题。我的操作系统为XP，C盘为NTFS格式，G盘为FAT32格式。用ISOEMU虚拟
引导。把IELDR放在C盘根目录，并修改BOOT.INI的相应先项,把ISOEMU.INI和镜像文件放在G盘根目录,用ISOEMU自带的镜像文件
可以引导,但用其的镜像文件却无法引导,提示说我的盘不是引导盘。但实际上该镜像的源光盘是可引导盘。很想知道是为什么？哪里错了。请知道的朋友赐教。

这东东哪里有的下？

看其他地方的文章说不能启动XP安装盘。

是的,不能启动非虚拟的

你有没有把isoemu.ini文件中最后一行中“isoemu isogrub.iso”isogrub.iso这个文件名替换成你放到C盘根目录中的ISO文件名。

最新的是 ISOEmu 109, 在这里有：

http://sysoft.zdwx.com/isoemu/bin/

10:21 2005-3-21 Version 1.09+
◎ 从 NTLDR 环境里启动(ieldr)， 也可以从纯 DOS 环境的命令行启动(ieldr.exe,
参照了 Mr. tinybit 的 Grub.exe)；
◎ 更新的 Logo；
◎ 支持 FAT32/NTFS 的隐藏分区上放置 isoemu.ini, isogrub.iso；
◎ 支持 FAT32/NTFS 的扩展分区；
◎ 加入 “IELDR 内置 Shell 使用说明”(ishell.chm)

出现ISOGRUB.ISO的中文GRUB画面,但是不管选择什么菜单都死机

以后会支持FAT12/16格式吗？

也许吧。 可能在 AviatoR 上会实现的。

以下是引用Gandalf在2005-4-7 9:45:16的发言：也许吧。 可能在 AviatoR 上会实现的。

Dear Gandalf,What is AviatoR? Is it an enhanced version of ieldr?May I know more about how isoemu is implemented?I have previously tried to use it and found that unless it is greatly enhanced, it does not serve much purpose.For instance, at present what isolinux and grub do in non-emulation mode for booting cd/dvd is to load up a memdisk containing an os or fire up a linux or other os kernels from the cd/dvd.I don't know whether at present isoemu is simply calling up the isolinux or grub loader set to be the bootable file embedded in the iso file. If it is so, the limitation are two folds:1. isolinux or grub loader may not recognize the iso file found on the hard disk anymore, especially when the iso file is large and discontiguous on a FAT/NTFS partition; this is why many people found problems when using isoemu with iso file they made2. the second limitation is even though the isolinux or grub loader is able to load up a vfloppy or memdisk containing DOS or WIN9X, the latter also does not recognize the iso file as a cd/dvd except loading up some other utilities to do so. For instance, under DOS you may have to load up shsucdhd and shsucdx to turn the iso file to be a virtual cd/. Furthermore, if the hard disk on which the iso file is is in NTFS format, then DOS/WIN9X cannot recognize it. So there is no way that the iso file can be recognized except loading a NTFS driver.So for ieldr or AviatoR to be useful, it should at best be able to do the job of isolinux or grub loader and more by overcoming limitation 1 above; i.e. to be able to recognize large and discontinuous iso file on FAT/NTFS partition and to load up an OS kernel embedded within the iso file. After that, the work is left to the OS loaded up. You can do no more.

Edited。。。

Re:
Dear WinDrv:
Thanks for you atteintion of the ISOEmu and the its next generation AviatoR.
Basically, it is true that isoemu has the limitations, i.e.
1. Only support FAT32/NTFS partition;
2. Only support Non-Emu mode Bootable CD;
3. Only support RealMode access;
... ...
But, I don't think it is ture for ISOEmu you mentioned above. If you tried it
you would get to know that. Let's explore the internal info of ISOEmu, and draw
some conclusion(s):
While getting the control of local system, ISOEmu will try to find its configuration
file - isoemu.ini, from the 1st hard disk, on the partition one by one(not only the
pri. partition but also dos-ext. prtition). Of course, ISOEmu will determinate the
partition type before looking into it.
While geting the proper isoemu.ini, ISOEmu analyses it, and try to get the
`isoemu` tag for the emulating iso filename. When ISOEmu found the ISO file at
the same position of isoemu.ini, it will use some basic information of this ISO
file to initialize the INT13h hook-stub, and uses the drive number `0xee` to access
the emulated CD. ;-)
Here, we must know:
A). ISOEmu has the powerful mini-fs of FAT32/NTFS, that can access those dis-
continuous files hosted on FAT32/NTFS partition;
B). ISOEmu will analyse the bootable type of CD. If this CD is non-emu mode,
ISOEmu will read the 1st 4KB of bootstrap program to memory: 0x0000:0x7c00, and
trans control to it, system is now booting with this emulated CD. ;-) Otherwize,
it will drop user to the internal shell. For how to use this CD, you can get
the information from the isoemu_eng.chm coming with 'isoemu 109th' release; or
get it from http://sysoft.zdwx.com/isomu/.
C). the INT13h hook-stub is FAT32/NTFS aware. So, the booting method is not
`simply jump to grub or syslinux`;

-------------------------
Something about ISOEmu G2, AviatoR
==================================
In general, the AviatoR is an OS, not a pure os loader. Now, I'd like to tell
you all 2 things about it:
A). AviatoR will use `3 in 1` technology as its existence. I mean, it will be
at the same file of its loader. And, AviatoR's loader, Avldr.exe, can be loaded
by NTLDR, can be run from DOS envirenment, and Windows Envirenment. Of course,
the Windows' function is only an installer, an assembler of Loader and Kernel; not
the same function of Grub4Lin from Mr. Tinybit. ;-)
B). AviatoR is an OS, which can act as a common multi-boot platform just like
NTLDR, GRUB and Syslinux. It is running on the Protected Mode, with beatiful GUI,
and has the full Chinese Supporting: Display, and Input. ;-)
But, I want to say, the Grub is so powerful that I even want to use it as the
loader of AviatoR. ;-) And the AviatoR is some kind of the exploring of x86's
protected mode.
OK, that's all.
Best wishes,
AviatoR