标题: The wimboot.mod not work when the wim file is not in the boot partition [打印本页] 作者: meoit 时间: 2020-5-18 06:15 标题: The wimboot.mod not work when the wim file is not in the boot partition 本帖最后由 meoit 于 2020-5-18 06:28 编辑
Hi guys,
Hi @WinToFlash / @a1ive
I installed NTBOOT to my HDD. My HDD have two partitions.The first partition for boot (FAT32), the second for data wim files (NTFS. I put wim file in here /WIM/winpe.wim).
In uEFI mode, the wimboot.mod module not work.
This is my menuentry:
Current, the second partition for data wim is (hd0,msdos5)
menuentry "WinPE WIM in uEFI mode" {
saved_root=$root
set root=(hd0,msdos5)
wimboot @:boot.wim:"${root}/WIM/winpe.wim" \
@:bcd:(${saved_root})/boot/wimboot/bcd \
@:boot.sdi:(${saved_root})/boot/wimboot/boot.sdi \
@:bootmgfw.efi:(${saved_root})/boot/wimboot/bootmgfw.efi
set root=$saved_root
}
It is show error:
STATUS: 0x00000f
Infor: An unexpected error has occured.
Why error ?.
(If in the LEGACY mode, linux16 "(${saved_root})/boot/wimboot/wimboot"
initrd16 newc..........,
working fine !
)
STATUS: 0x00000f
Infor: An unexpected error has occured.
That's because boot.sdi file isn't in the right directory,where BCD file referes to.
I upload the wimboot files:bootmgfw.efi+bcd+boot.sdi. I forget where it comes from,maybe from windows10.iso.Put those files into ${saved_root})/boot/wimboot/,(hd0,msdos5)
It is not recommand to use wimboot to boot pe.wim,I prefer NTBOOT,which is about 15 seconds faster then wimboot.mod.
