07-29-2020, 12:57 PM (This post was last modified: 08-03-2020, 01:40 PM by dancer78.)
In version 1.0.16 and 1.0.17 and 1.0.18 Win10XPE starts loading but fails about a quarter of he way .
error says disk was removed.
Version 1.0.14 and 1.0.15 work fine
Any idea why it worked without memdisk in 1.0.16 and before and now it doesn't ?
You write that WINXPE does not work with 1.0.16, 1.0.17 and 1.0.18.
cyablo writes here: https://forums.ventoy.net/showthread.php?tid=398
I used Ventoy 1.0.15. The .16 was released yesterday, I'll give it a try.
You're right! It works with 1.0.16.
I think there are too many different Bios and UEFI systems. 450 different ISO should work without problems on all systems? We must not forget that longpanda has to modify the code for some ISO to make them work. This can cause problems for other ISOs that were working before. We should not complain if we need to use Memdisk or an extracted boot.wim.
Any idea why it worked without memdisk in 1.0.16 and before and now it doesn't ?
You write that WINXPE does not work with 1.0.16, 1.0.17 and 1.0.18.
cyablo writes here: https://forums.ventoy.net/showthread.php?tid=398
I used Ventoy 1.0.15. The .16 was released yesterday, I'll give it a try.
You're right! It works with 1.0.16.
I think there are too many different Bios and UEFI systems. 450 different ISO should work without problems on all systems? We must not forget that longpanda has to modify the code for some ISO to make them work. This can cause problems for other ISOs that were working before. We should not complain if we need to use Memdisk or an extracted boot.wim.
I don't think anyone is complaining - I posted my particular ISO (Galdalf's) as tested and working with 1.0.15 just prior to 1.0.16 being released and am now reporting it as no longer working since it is now listed on the "Tested ISO" page.
Note: Memdisk isn't an option in my environment due to ISO size vs. RAM - Workarounds are great, but my guess is that longpanda would want to know when there are things that no longer work following a release, and that's why this thread exists :-)
I tried multiple sizes of win10xpe without f1 to see what happened and made list below.
XPE 1,2 worked
XPE 3-6 failed with error in picture 1
Xpe 7-11 failed with error in picture 2
Win10xpe size iso size boot.win size boot type of error
1096348 1056753 yes none
1110406 1056753 yes none
1119896 1061043 no picture 1
1132680 1062776 no picture 1
1142372 1062776 no picture 1
1652518 1070308 no picture 1
1690552 1070782 no picture 2
1815392 1070783 no picture 2
1903230 1070783 no picture 2
1997234 1070783 no picture 2
2136480 1071788 no picture 2
NOTE: all Win10XPE iso's will load using f1 (memboot)
and all boot.wim will load if ventoy_wimboot.img is there