The following list shows the development process to use to create a run-time image:
The first step in the development process is to identify the target device hardware you plan on deploying to.
You can use Target Analyzer to automatically detect the hardware on your system, or you can individually select each device driver component when you are creating your run-time image in Target Designer.
During the componentization phase you create components for your applications, shells, and device drivers. Using Component Designer, you can define the files that make up the component, assign dependencies on other components, and set registry information.
Also, during this phase you can customize your shell by eliminating pop-up balloons and intercepting message boxes.
During the design phase, choose the components required for your run-time image.
This includes components that support system hardware, and base Windows components that are required to run your applications (such as networking support or multiple languages). Additionally, this phase includes creating custom components for your own applications and device drivers.
Embedded-specific components, such as EWF and Minlogon, can be added to your run-time image during this phase.
During the design phase, you must consider how you will keep your device up to date with patches and updates. Adding a servicing mechanism, such as DUA, is required to be able to update your run-time image. For more information, see Servicing.
Additionally, it is imperative that you add security components to your run-time image to help prevent malicious attacks.
After you have designed your run-time image, you are ready to build your run-time image and deploy it to your device.
You build your run-time image in Target Designer. Target Designer creates a Windows XP embedded file system.
The standard method of deployment is to copy the XP embedded file system to your device. However, there are additional embedded-specific components that you can add to your run-time image to support different types of deployment. For example, the cloning component supports deploying to mass devices.
After your run-time image is deployed, you can service your device with updates using one of the supported servicing mechanisms. You must add one of the update mechanisms to your run-time image during the design phase of the development process. For more information, see Servicing.
Last updated on Wednesday, October 18, 2006
© 2006 Microsoft Corporation. All rights reserved.