How to start a progarm after "VistaPE Loader"

I wants to run a program on start up that depends on the network drive been loaded and TCP/IP protocol up and running, how can I do that?
Is there anyway to detect if the TCP/IP is up and running before doing the further scanning extra drivers, I would like to pack a small pack of common drivers together, so they will be scanned first, if the TCP/IP is not running, then all other driver will be processed!

That will cut down a lot of wait time for technician, thanks in advance!

You can set up a loop that runs as long as "ping google.com" fails.

I've done some more reading, in VistaPE API, in [Process] section, VistaPE API, there are two commands:
AddAutoRun
AddPostConfig

They can be used to start programs. But I need to start a Windows service after network card drivers is initialized and obtain an DHCP IP address.

Anyone can help?

I've done some more reading, in VistaPE API, in [Process] section, VistaPE API, there are two commands:
AddAutoRun
AddPostConfig

They can be used to start programs. But I need to start a Windows service after network card drivers is initialized and obtain an DHCP IP address.

Maybe AddPostConfig,%SystemRoot%\System32\Net,"start ServiceName",4?

Tried:
AddPostConfig,"Program Name",%SystemRoot%\System32\Net.exe,#$sstart#$sServiceName,4

Not working*

Tried:
AddPostConfig,NotePad,%SystemRoot%\System32\Notepad.exe,,4

Working

What does AddPostConfig do? Adding something to a batch file? Anybody has the name of the file?

Help pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaase!

Tried:
AddPostConfig,"Program Name",%SystemRoot%\System32\Net.exe,#$sstart#$sServiceName,4

Not working*

Tried:
AddPostConfig,NotePad,%SystemRoot%\System32\Notepad.exe,,4

Working

What does AddPostConfig do? Adding something to a batch file? Anybody has the name of the file?

Help pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaase!

AddPostConfig adds a command to the vpeldr's config file that will be processed last thing before the loader exits.
if you look in your target dir you can view the contents of vistape.cfg and targetdir\windows\system32\vistape.cfg with any text editor and see the commands the loader will process.

AddPostConfig adds an entry to the [postconfig] section in the file: vistape.cfg
when booting VistaPE the vpeldr.exe will execute these lines as last steps
(like a HKLM\Software\Microsoft\Windows\CurrentVersion\Run entry in normal windows or like a \ Start Menu\ Programs\ Startup\ autostart entry)

e.g. at me this line is working:
AddPostConfig,start_mms,x:\windows\system32\net.exe,start mms,3
(the above example starts the 'mms' services of Acronis Backup And Recovery 10)

AddPostConfig adds an entry to the [postconfig] section in the file: vistape.cfg
when booting VistaPE the vpeldr.exe will execute these lines as last steps
(like a HKLM\Software\Microsoft\Windows\CurrentVersion\Run entry in normal windows or like a \ Start Menu\ Programs\ Startup\ autostart entry)

e.g. at me this line is working:
AddPostConfig,start_mms,x:\windows\system32\net.exe,start mms,3
(the above example starts the 'mms' services of Acronis Backup And Recovery 10)

What does the added line looks like in the [postconfig] section, mine has nothing after AddPostConfig command, I'll try again now!

[postconfig]
hidewait|start_mms|x:\windows\system32\net.exe start mms

usually every VistaPE app. script contains something similar lines:
e.g.

[Interface]
pCheckBox1="Run from ram (boot.wim)",1,3,28,16,320,18,True

[process]
RunFromRam,%pCheckBox1%

in case of 'RunFromRam,True'
the file 'windows\system32\vistape.cfg' packed into vistape.wim
will contain this postconfig entry

in case of 'RunFromRam,False'
the vistape.cfg in the root of the builded CD
will contain this postconfig entry

Note that there are two vistape.cfg files, one in the root of the CD and one in Windows\System32. This has already been posted but it's not certain (to me) that you noticed it and checked both of them.

When you are editing a script's source code in WinBuilder, you can click the Magic Wand button or right-click where you want to insert a command, and you will get a menu that covers almost all of them. The AddPostConfig command is an "API command" which is added to WinBuilder's base commands by the API script in a project. API command are listed at the bottom of the first Magic Wand menu.

There's some documentation of the VistaPE API at http://www.vistape.n...istape-api.html. The "Description of commands and options" heading is the one I find the most useful.

The VistaPE-CAPI project uses a "Common API" script, which works in multiple projects, and extends some of the commands described at the above link (ReadEnv springs t mind).

usually every VistaPE app. script contains something similar lines:
e.g.

[Interface]
pCheckBox1="Run from ram (boot.wim)",1,3,28,16,320,18,True

[process]
RunFromRam,%pCheckBox1%

in case of 'RunFromRam,True'
the file 'windows\system32\vistape.cfg' packed into vistape.wim
will contain this postconfig entry

in case of 'RunFromRam,False'
the vistape.cfg in the root of the builded CD
will contain this postconfig entry

Do you imply that if I use RunFromRAM command, I should not use AddPostConfig at same time?

Do you imply

No,
of course it is possible to use AddPostConfig in both case

as JonF explained:

Note that there are two vistape.cfg files, one in the root of the CD and one in Windows\System32. This has already been posted but it's not certain (to me) that you noticed it and checked both of them.

Do you imply that if I use RunFromRAM command, I should not use AddPostConfig at same time?

No. He's just listing some of the circumstances in which one vistape.cfg file contains the information generated by a particular script, and when the other vistape.cfg file contains it.

IT is a good idea toinclude the checkbox and RunFrom Ram, but it's independent of AddPostConfig.

BTW, if you look in Base\07-config.script, you will find several examples of starting services withj AddPostConfig.

Thanks All.


The AddPostConfig works well. The problem was the Vista project I downloaded did not function properly. People should download the VistaPE project from VistaPe.Winbuilder.net instead of vistape.net/project.