中国DOS联盟

I saw this post in time and space, but no one replied. I also really want to know the reason, so I repost it here!

I have a few questions about the mutual invocation of various bootloaders, hoping that experts can give me some advice!

1. After the A bootloader --> B bootloader, does the A bootloader still exist in memory? Or does A have an impact on the subsequent B?

2. After DOS --> Grub4dos, when returning to DOS from Grub4dos, is DOS reloaded, or is DOS already in memory and directly called?

3. Why is the boot speed of the USB flash drive in the way of GNU GRUB --> NTLDR --> Grub4dos --> pe much faster than that in the way of GNU GRUB --> Grub4dos --> pe?

4. After syslinux starts, can it directly call NTLDR, that is, syslinux --> ntldr -->....? If yes, how to write syslinux.cfg?

Thanks!!!

# boot from hd

label 0

	localboot 0x80



# boot from floppy

label a

	localboot 0x00



# cancel and try next boot device

label q

	localboot -1

# boot from 1st hd

label aHD

kernel chain.c32

append hd0 0



# boot from 2nd hd

label bHD

kernel chain.c32

append hd1 0

syslinux cannot boot ntldr, but the following methods can be used

# boot from hd

label 0

	localboot 0x80



# boot from floppy

label a

	localboot 0x00



# cancel and try next boot device

label q

	localboot -1

# boot from 1st hd

label aHD

kernel chain.c32

append hd0 0



# boot from 2nd hd

label bHD

kernel chain.c32

append hd1 0

Last edited by barton on 2008-2-17 at 07:12 PM ]

syslinux cannot boot ntldr, but the following methods can be used

Does this mean that NTLDR must be installed in the MBR to be called?


Also, please tell me about the first three questions, thank you!

Moderator!!! Expert!!!
Come on!

Why is there no one replying anymore? Just share your thoughts, please! Thanks!!!

These questions have been answered by bean in terms of space and time.
1. Does not exist. Theoretically, A will not have an impact on B, but in reality, when A starts B, it may retain some hardware settings, such as A20, interrupt vector interception, etc., which will cause certain impacts on B.
2. When grub4dos starts, it will save the DOS in memory to the upper memory, and restore it when exiting.
3. I don't know the specific reason either. It may be caused by hardware.
4. Using loadbin, you can start grub/grub2/grub4dos/ntldr in any boot manager that supports the Linux kernel. For detailed usage, please refer to:
http://bbs.znpc.net/viewthread.php?tid=4273&highlight=loadbin