Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Tripredacus

Posted 23 June 2008 - 01:44 PM

Wait, I am confused here. Are you saying that your startnet.cmd doesn't automatically launch when you boot the PE? If so it sounds like you skipped a step! The default PE setup doesn't even use the winpeshl.ini and the startnet.cmd opens by itself.

niveknonrev

Posted 24 June 2008 - 06:41 AM

niveknonrev

Member

5 posts

Joined 21-December 04

Wait, I am confused here. Are you saying that your startnet.cmd doesn't automatically launch when you boot the PE? If so it sounds like you skipped a step! The default PE setup doesn't even use the winpeshl.ini and the startnet.cmd opens by itself.

Tripedacus, thanks for looking at this post.

No that is not what I am saying. Startnet.cmd launches perfectly all by itself. However following Microsoft's instructions for launching a "custom shell" or "custom apps" etc. It says to use the winpeshl.ini file, the LaunchApp with the AppPath = %systemdrive%\myshell.exe - etc.

Then you are supposed to be able to uset the LaunchApps section to launch other applications after your shell starts.I followed the directions below using BSExplore as my shell, but it still didn't work:

Winpeshl.ini FilesWinpeshl.ini controls whether a customized shell is loaded in Windows PE instead of the default Command Prompt window. To load a customized shell, create a file named Winpeshl.ini and place it in %SYSTEMROOT%\System32 of your customized Windows PE image. The .ini file must have the following section and entry.

Set the AppPath entry to the path to your shell application. The path can be either fully qualified, or you can use environment variables, such as %SYSTEMROOT%\System32\Myshell.exe. The AppPath entry does not support command-line options.

Use the [LaunchApps] section to run applications with command-line options. The applications run in the order listed; separate the name of the application from its options with a comma.

Tripredacus

Posted 24 June 2008 - 12:19 PM

Yes, It does indeed seem like a better way, but I like having the command prompt there. If you put your custom app in the startnet.cmd, it will open on top of the command prompt. So if your app is full-screen you won't see the CMD anyways. But you can still get to it if you alt+tab there.

paxamime

Posted 26 June 2008 - 02:39 PM

paxamime

Newbie

Member

36 posts

Joined 28-September 06

If your looking for a cleaner way of launching multiple programs I suggest doing it a different way. Create an xml file with your applications you want to run, save it in system32 and edit your Startnet.cmd

yaleyu

Posted 30 July 2008 - 08:31 PM

yaleyu

Member

5 posts

Joined 26-July 08

I cannot get LaunchApps work in winpeshl.ini, except the AppPath=... shell line, all other lines are unable to run, doesn't matter it's startnet.cmd, x:\windows\system32\startnet.cmd, or %systemdrive%\startnet.cmd

phgddr

Posted 22 August 2008 - 02:16 AM

phgddr

Member

2 posts

Joined 22-August 08

Hello,

I found a solution which allows to launch many applications from winpeshl.ini. From what I have observed, it seems you cannot use both [LaunchApp] and [LaunchApps] sections together. So if you have many applications to launch just use [LaunchApps] and put your shell in the last position. Here is my winpeshl.ini file which works fine :

Be careful, the syntax of the commands is a bit tricky in case there are arguments. There MUST be a comma after the command itself and, in case there multiple arguments, all the arguments MUST be enclosed between double quotes (see bginfo line in the previous example).

phgddr

Posted 22 August 2008 - 02:18 AM

phgddr

Member

2 posts

Joined 22-August 08

Hello,

I found a solution which allows to launch many applications from winpeshl.ini. From what I have observed, it seems you cannot use both [LaunchApp] and [LaunchApps] sections together. So if you have many applications to launch just use [LaunchApps] and put your shell in the last position. Here is my winpeshl.ini file which works fine :

Be careful, the syntax of the commands is a bit tricky in case there are arguments. There MUST be a comma after the command itself and, in case there multiple arguments, all the arguments MUST be enclosed between double quotes (see bginfo line in the previous example).

Schiiwa

Posted 19 October 2011 - 03:14 PM

Schiiwa

Junior

Member

77 posts

Joined 23-December 10

OS:none specified

Country:

Hello,

I found a solution which allows to launch many applications from winpeshl.ini. From what I have observed, it seems you cannot use both [LaunchApp] and [LaunchApps] sections together. So if you have many applications to launch just use [LaunchApps] and put your shell in the last position. Here is my winpeshl.ini file which works fine :

Be careful, the syntax of the commands is a bit tricky in case there are arguments. There MUST be a comma after the command itself and, in case there multiple arguments, all the arguments MUST be enclosed between double quotes (see bginfo line in the previous example).

Why not include the 2nd and 3rd in STARTNET.CMD to avoid the unlovely comma & quotes?

Tripredacus

Posted 20 October 2011 - 07:47 AM

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

Posted 20 October 2011 - 09:50 AM

Schiiwa

Junior

Member

77 posts

Joined 23-December 10

OS:none specified

Country:

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