... when I boot my machine with WinPE iso image all the drives of hard drive are there in the tree but "network" is not there...

You must ensure that wpeinit has completed before executing your application. You may need to wait several minutes.Perhaps, in your case it would be best to have taskmgr as the first line in startnet.cmd, followed by wpeinit. That way you can see in the Task Manager Processes Tab when wpeinit has completed.

Just a suggestion. It may be a driver issue.

Regards

Now I create Winpeshl.ini having following lines and paste it to g:\madan\mount\windows\syetm32\

[LaunchApp]

AppPath = %SYSTEMROOT%\System32\myApplication.exe

[LaunchApps]

Sorry. I had forgotten that you had given control to winpeshl.ini. From the Users Guide:

If you create a customized Winpeshl.ini and require Plug and Play or network

support, you must include a call to Wipeinit.exe. Wpeinit.exe specifically

installs Plug and Play devices, processes Unattend.xml settings, and loads

network resources.

You need to add wpeinit to the [LaunchApps] section, followed by your Application:

[LaunchApp]
[LaunchApps]
wpeinit
%SYSTEMROOT%\System32\myApplication.exe

The [LaunchApp] section is for a custom Shell.

Regards

EDIT: I do not use this method. It may be the case that your Application will still execute before wpeinit has completed. You can try other calls to wpeinit in the [LaunchApps] Section, such as 'CALL startnet.cmd', or 'cmd.exe, /k wpeinit', 'start /wait wpeinit', etc. I don't know which method will give satisfactory results. Trial and error!

Edited March 19, 200917 yr by allanf

Now I create Winpeshl.ini having following lines and paste it to g:\madan\mount\windows\syetm32\

[LaunchApp]

AppPath = %SYSTEMROOT%\System32\myApplication.exe

[LaunchApps]

Sorry. I had forgotten that you had given control to winpeshl.ini. From the Users Guide:

If you create a customized Winpeshl.ini and require Plug and Play or network

support, you must include a call to Wipeinit.exe. Wpeinit.exe specifically

installs Plug and Play devices, processes Unattend.xml settings, and loads

network resources.

You need to add wpeinit to the [LaunchApps] section, followed by your Application:

[LaunchApp]
[LaunchApps]
wpeinit
%SYSTEMROOT%\System32\myApplication.exe

The [LaunchApp] section is for a custom Shell.

Regards

EDIT: I do not use this method. It may be the case that your Application will still execute before wpeinit has completed. You can try other calls to wpeinit in the [LaunchApps] Section, such as 'CALL startnet.cmd', or 'cmd.exe, /k wpeinit', 'start /wait wpeinit', etc. I don't know which method will give satisfactory results. Trial and error!

Thanks Allanf,

thanks for your kind support. I will try the way you suggested me and then I will reply.

Regards

Madan Chauhan

In the file \windows\system32\startnet.cmd, why the various default paths of Windows PE there not are? These paths are written where?

THANKS

BYE

... These paths are written where?

In the registry:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment

(... from XP, but should be the same for Windows PE 2.x/3/0.)

In Windows PE Command Prompt, type:

SET

or

SET PATH

Regards