PRB: Replacing OS Files in a Custom .kdf File (298894)
The information in this article applies to:
- Microsoft Windows NT Embedded 4.0
This article was previously published under Q298894 SYMPTOMS
When Target Designer is used to add a different version of a file that is already part of a default operating system (OS) component, the resulting image will contain the original file, not the new file.
CAUSE
This behavior is caused by the order in which Target Designer evaluates a configuration when executing a build.
STATUS
This behavior is by design.
MORE INFORMATIONProblem scenario:
A user creates a custom component definition file (.kdf) in Component Designer that includes a different version of any file than those that Target Designer includes as part of an operating system component. Component Designer will allow the component to be created, and the user can import the .kdf file into Target Designer through Component Management. However, when the user executes a build, the resulting image only includes the original OS file, and not the one in the custom .kdf file.
| Modification Type: | Minor | Last Reviewed: | 12/26/2003 |
|---|
| Keywords: | kbprb KB298894 |
|---|
|