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. <img src="images/smilies/face-wink.png" align="absmiddle" border="0"> 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
Re:
Dear WinDrv:
Thanks for your attention to the ISOEmu and 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 true for the 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 determine the partition type before looking into it.
While getting the proper isoemu.ini, ISOEmu analyses it, and tries 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. ;-) Otherwise, 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 environment, and Windows Environment. 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 beautiful 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
