ICcBootStrap::Launch
Other versions of this page are also available for the following:
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
This method launches an application with command line arguments on a remote device.
Syntax
HRESULT Launch(
BSTR bstrCommand,
LPCOLESTR bstrArguments,
DWORD dwLaunchFlags
);
Parameters
- bstrCommand
[in] Application name to launch, including the full path if the application is not in the standard search path.
- bstrArguments
[in] Command line arguments for bstrCommand.
dwLaunchFlags
[in] Flag to determine which KITL transport to start on a device boot.The flag is an OR combination of one of the following:
Flag Value Description KTS_DEFAULT
0
Default transport for platform.
KTS_ETHER
1
Ethernet transport.
KTS_SERIAL
2
Serial transport.
KTS_USB
3
USB transport.
KTS_NONE
63
No transport.
KTS_PASSIVE_MODE
0x40
Passive KITL mode transport.
Return Value
The following table shows return values for this method.
| Value | Description |
|---|---|
S_OK |
Indicates success. |
HRESULT_FROM_WIN32() |
Indicates an error code returned by CeCreateProcess (RAPI) or CreateProcess on the device. |
E_FAIL |
Indicates any other failure. |
Remarks
The dwLaunchFlags launch flags are passed in as arguments to CreateProcess.
In the case of a kernel bootstrap, this API also sends instructions to the device to jump to the starting address of the image. In this case, wszCommand is ignored.
For application bootstraps, dwLaunchFlags value is passed to CreateProcess without any modifications.
Requirements
| Header | ccbootstrap.idl |
| Windows Embedded CE | Windows CE 5.0 and later |