LaunchApps in Winpeshl.ini not running

[Tripredacus]

The big difference between the two options is that if you use winpeshl.ini, you don't get the command prompt. This is a much better option if you don't want the end-user to have access to the prompt, say if you were making a recovery partition.

[Schiiwa]

The big difference between the two options is that if you use winpeshl.ini, you don't get the command prompt. This is a much better option if you don't want the end-user to have access to the prompt, say if you were making a recovery partition.

U didn't understand what i try to say. I related to the previous post #14

That was in my mind:

Make a Winpeshl.ini:

[LaunchApps]
%SYSTEMDRIVE%\Windows\system32\startnet.cmd

And a startnet.cmd

REM wpeinit
%SYSTEMDRIVE%\Programs\bginfo.exe %SYSTEMDRIVE%\Programs\bginfo.bgi /timer:0 /accepteula
%SYSTEMDRIVE%\Programs\nu2menu\nu2menu.exe
X:\sources\recovery\recenv.exe

BUT:

As expected the cmd-windows stays behind the shell until reboot, or if it will be closed, reboot is the consequence

I will try to run my Commands from [LaunchApps] now to avoid the CMD in background

rundll32 setupapi,InstallHinfSection DefaultInstall 132 %SystemDrive%\windows\system32\drivers\wimfltr.inf
Net start wimfltr

According to phgddr's post #13, it should look like this:

%SYSTEMDRIVE%\Windows\System32\rundll32.exe, "setupapi,InstallHinfSection DefaultInstall 132 %SYSTEMDRIVE%\windows\system32\drivers\wimfltr.inf"
%SYSTEMDRIVE%\Windows\System32\net.exe, "start wimfltr"
%SYSTEMDRIVE%\sources\recovery\recenv.exe

works great..... big thanks to phgddr

Edited October 20, 2011 by Schiiwa