09-16-2023, 09:45 AM
For VentoyAutoRun.bat:
There is no Window when run it. So no shell windows is available.
For winpeshl.ini:
iVentoy also use winpeshl.ini.
So in current release, iVentoy just create a new winpeshl.ini file (so it override the one that you injected).
I will fix this in the next release, then if there is already a winpeshl.ini file, iVentoy just append to the end of the file.
So you can wait for the next release, and use winpeshl.ini method.
But it should be noted that, you can not add setup.exe in winpeshl.ini file, because iVentoy will add it to the end of winpeshl.ini file.
Your winpeshl.ini file can be as follows:
There is no Window when run it. So no shell windows is available.
For winpeshl.ini:
iVentoy also use winpeshl.ini.
So in current release, iVentoy just create a new winpeshl.ini file (so it override the one that you injected).
I will fix this in the next release, then if there is already a winpeshl.ini file, iVentoy just append to the end of the file.
So you can wait for the next release, and use winpeshl.ini method.
But it should be noted that, you can not add setup.exe in winpeshl.ini file, because iVentoy will add it to the end of winpeshl.ini file.
Your winpeshl.ini file can be as follows:
Code:
[LaunchApps]
%SYSTEMDRIVE%\prompt.bat