FBA Commands
5/10/2007
By using Component Designer or Target Designer, you can specify commands that must run during the First Boot Agent (FBA) portion of run-time image deployment. These commands are also referred to as custom resources.
The following table shows the eight FBA commands.
| Command | Description |
|---|---|
Generic Command |
Executes a generic command during FBA processing. You can call entry points in a DLL, execute a script, or call an application. The Generic Command allows you to specify the exact phase at which to run, and can be called before or after a component. .gif "Bb521637.note(en-US,WinEmbedded.5).gif") Note:
The default phase number for this command is 0, but must be changed to a number greater than 8500. Phases 0-8500 are reserved for system use only.
|
DLL/COM Registration |
Registers DLLs and COM objects. Note:
The default phase number for this command is 4500, but must be changed to a number greater than 8500. Phases 0-8500 are reserved for system use only.
|
OC Manager Request |
OC Manager is the Optional Component Manager. This allows the integration of external components into the setup process. This command is reserved for Microsoft. |
RunOnce Request |
Executes a file during FBA or after you log on. You cannot specify a phase number as you can with a Generic Command. For more information, see RunOnce Request Types and Scenarios. |
Service Data |
Adds Windows XP service information to the run-time image registry. |
PnP Device ID |
Adds a PnP device driver ID to the run-time image registry. |
Component Branch |
Specifies which component will replace a specified end-of-life component. Directs Target Designer to use the new component when it builds a configuration. |
Shortcut |
Creates a short-cut link for an application. |