QEMU中的引导加载器靴子,即使启动签名错误
我在QEMU中使用自己的bootloader播放X32位系统,并尝试从ISO文件中启动,而没有设置0xaa55
作为该扇区的最后两个字节,而0x2233
而不是而不是< br> 但是Qemu仍然启动并显示出与之前相同的结果 没有正确的签名,QEMU不应该将我的磁盘视为可引导设备吗? 它仍在启动如何?
这是我的bootloader.asm:
org 0x7c00 ; We are loaded by BIOS at 0x7C00
bits 16 ; We are still in 16 bit Real Mode
Start:
cli ; Clear all Interrupts
hlt ; halt the system
times 510 - ($-$$) db 0 ; We have to be 512 bytes. Clear the rest of the bytes with 0
dw 0x2233 ; Boot Signiture
我关注 iso
要启动的文件,甚至尝试更改问题的ASM代码的签名,然后Qemu再次将其识别为可引导媒体,并打印为“这是我很酷的新OS!”在屏幕上
I was playing around with my own bootloader in QEMU for x32 bit systems and tried booting from iso file with not setting 0xAA55
as the last two bytes of the sector and 0x2233
instead
But QEMU still booted and showed the same results as it did before
Without the correct signature shouldnt QEMU fail to recognize my disk as bootable device?
How is it still booting?
Heres my bootloader.asm :
org 0x7c00 ; We are loaded by BIOS at 0x7C00
bits 16 ; We are still in 16 bit Real Mode
Start:
cli ; Clear all Interrupts
hlt ; halt the system
times 510 - ($-$) db 0 ; We have to be 512 bytes. Clear the rest of the bytes with 0
dw 0x2233 ; Boot Signiture
I followed this question to make the iso
file to boot from and even tried with changing the signature of asm code of the question, and QEMU again recognized it as a bootable media and printed "This is my cool new OS!" on screen
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论