Ventoy Forums
Ventoy-1.0.49 release - Printable Version

+- Ventoy Forums (https://forums.ventoy.net)
+-- Forum: Ventoy General Use —— Ventoy 使用交流 (https://forums.ventoy.net/forumdisplay.php?fid=1)
+--- Forum: Ventoy Discussion Forum (https://forums.ventoy.net/forumdisplay.php?fid=2)
+--- Thread: Ventoy-1.0.49 release (/showthread.php?tid=1762)



Ventoy-1.0.49 release - longpanda - 08-03-2021

  • 2021/08/03 --- 1.0.49 release
  1. Compatibility improvement for some WinPE

  2. Optimization for booting SUSE/openSUSE

  3. Fixed the boot issue for "StorageCraft Recovery Environment" ISO in UEFI mode (#1034)

  4. languages.ini update



RE: Ventoy-1.0.49 release - strongbad75 - 08-04-2021

(08-03-2021, 04:08 PM)longpanda Wrote:
  • 2021/08/03 --- 1.0.49 release
  1. Compatibility improvement for some WinPE

  2. Optimization for booting SUSE/openSUSE

  3. Fixed the boot issue for "StorageCraft Recovery Environment" ISO in UEFI mode (#1034)

  4. languages.ini update

@longpanda  Can you give some more details on improvements to WinPE?  There are many folks that are curious.


RE: Ventoy-1.0.49 release - Atari800XL - 08-05-2021

I second that request.
It seems that PE compatibility has improved with 1.0.49, this is confirmed by my own tests, and other people's tests.
Please let us know what was changed to make this happen.

Big thanks for the new improvements!!!


RE: Ventoy-1.0.49 release - longpanda - 08-06-2021

Here is a description about the internal mechanism that how Ventoy boot standard Windows ISO.
http://reboot.pro/index.php?showtopic=22277&page=4#entry214750

The key is the process on winpeshl.exe, but some WinPE don't use winpeshl.exe. They use PECMD.EXE instead.
So in the latest release, Ventoy will firstly do the same process on PECMD.EXE if it exist.


RE: Ventoy-1.0.49 release - Atari800XL - 08-06-2021

Thank you very much for reporting back.
I will download some old Ventoy versions and do some extra checking to confirm.
I don't remember now if any of **my** systems had this problem with PEs, but I'm 100% sure of some *other* PE users had the problem, and for them it was indeed fixed with the new version 1.0.49. So that's great news, thanks again LongPanda!