*Updated formatting - 4/13/10*
This is the second blog in a series of articles which discusses the troubleshooting and diagnosis of driver installation issues in Windows Embedded Standard 7 (Standard 7). Previously we presented the different phases of setup and a brief introduction to SetupAPI logging and the SetupAPI.dev.log file. We will now start off with the format of the SetupAPI.dev.log file.
Comments Product Updates
Mass deployment is the process of creating a master Windows Embedded Standard 7 runtime image on a reference system and then deploying this image to multiple target systems. The deployment process typically uses specific tools such as System Preparation tool (sysprep.exe) and Imagex.exe as well as Windows PE Environment to perform the following tasks:
- Generalize the master system by removing machine specific information
- Capture the system into a Windows image (wim) file
Windows Embedded Standard 7 adopts same localization model as the Windows 7. Basically, language resources are completely separated from the code, enabling a worldwide binary which does not require localization in all supported language. All localizable resources are packaged in the form of language pack, and Standard 7consists of language neutral image plus language packs.
A while back JT talked about Application Templates for Image Configuration Editor and the resources and community that we’re building around them. I wanted to explain how to create a template for ICE and clarify any questions you might have.
Templates are functionally just like answer files, but are meant to represent some functionality or subset that you would like to have available or share to build upon. ICE can take these templates and merge them into the answer file you are currently working with, as well as export them to share with other people, like on our new Application Templates web page. This allows you to work with images at a higher level of abstraction, grouping things such as drivers needed for your various models of devices, flagship 3rd party apps that have had their dependencies fully analyzed and tested, audio and visual packages needed for kiosk or gaming machine bases, etc.
To create a template, create an answer file as you normally would, then save it in the Templates folder (or any subfolder under it) of the distribution share in which you created it. The distribution share pane will then refresh and show your template in the pane.
ASK: The Embedded product group has been asked by customers to reduce the size of the monthly Windows XP Embedded and Windows Embedded Standard 2009 Security Update supplemental releases on MOO and ECE.
HISTORY: The monthly supplement has accumulated every security DQI (runtime update package) that is applicable for each of our embedded platforms. The supplement also includes a cumulative component database update for each platform development environment, which contains all applicable Security updates since the platform released. By accumulating the applicable DQIs for every platform on the download, over time the size of the monthly security supplement has grown quite large. For example, the December 2008 IMG (ISO) download was approximately 507MB. This has grown to approximately 800MB for the December 2009 IMG (ISO) download.
ACTION: Beginning with the January 2010 supplement, we have implemented a new process. The January 2010 supplement provides the DQIs for December 2009 and January 2010 as well as the cumulative component database updates for each platform, which still contain all Security updates since the platform release through December 2009 (the database updates are bi-monthly and current in the even numbered months). DQIs will accumulate for each supported platform throughout the year. At the beginning of 2011, we will do a similar refresh of the supplement.