Target Designer is used to select components that are necessary to support the hardware of a target system, and then to build the XP Embedded (XPe) image. Information about the hardware in a target device is normally stored in a PMQ file, which is then imported into Target Designer.
As Allen notes, "if you have to build a new configuration that uses [the same] PMQ, you have to start from scratch and re-import the PMQ, which takes a significant chunk of time. You also encounter this time hit if you need to import multiple PMQs ... because you want to build an image for different sets of hardware."
The suggested way around this problem is to change a registry key on the machine that's running the XP Embedded suite of tools. Once an "EnableCache" string has been added to the relevant part of the registry, a cache of component data will be created the first time a PMQ file is imported into the database.
"Thereafter," Allen writes, "any subsequent PMQ imports will utilize the cache data to resolve the data in the PMQ to components, rather than having to research the entire database for this information." The caveat is that any imports to the database -- such as hot fixes, updates, or custom components -- will render the cache out of date.
To read Allen's post, complete with registry details, go
here.
Related stories:
