Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
One of the biggest changes between our Windows Embedded Standard 2009 (XP Embedded) and Windows Embedded Standard 2011 tools is the concept of image building. In Windows Embedded Standard 2009, components were selected in Target Designer and images assembled on the developer machine, after which it had to be transferred to the target device. In Windows Embedded Standard 2011, images are now built directly on the device using our Image Based Wizard (IBW) which can be configured “on the fly” using the wizard interface, or by using a preconfigured answer file. Each method has its own pros and cons, and while I won’t go into them, there certain applications and scenarios where it is still advantageous to be able to build images offline.
This article goes over the steps for assembling a Windows Embedded Standard 2011 image with the desired feature sets, using only the tools found on your developer machine. This method can save a lot of time and also utilize less memory on the target, if you have to build & deploy your images on a resource constrained devices. As an example, we found that the time taken for building and deploying a MaxBoot image on a target device with 2 Ghz machine w/ 1gig of ram can be cut from 30 minutes to 15 minutes. The time savings only get greater for target devices with more limited resources. Note: This does not include the time taken to offline-build the image as those times can vary significantly depending on the configuration of the developer machine.
Before I proceed further, please note that this method for building images is not a perfect substitute for building images using the IBW. Not all image configurations can be built using this method, and I’ll call out what developers should be aware of as we proceed through the steps.
So you’ve spent a few hours, and you’ve made the perfect answer file for your device. Internet Explorer works, media files can be played, and you are very happy with how it turned out. However, after testing for just 5 minutes, you realize you can’t open and view certain picture formats, such as PNGs, on your device.
Do you really have to go back into Image Configuration Editor (ICE), re-create the answer file and then reinstall the image on your device?
Dialog Box Filter is a new feature in Windows Embedded Standard 2011. Dialog Box Filter can be used to prevent dialogs or windows from appearing on your embedded system. In order to use Dialog Box Filter properly it is important that you understand how it performs this task. This article will explain how Dialog Box Filter works and its limitations, as well as how to troubleshoot issues.
The Dialog Box Filter feature has 4 main components:
During the planning phases of Windows Embedded Standard 2011, we invested considerable effort to make Windows Embedded Standard 2011 customizable to the point where our customers will be able to create a custom experience – from the moment the machine boots up until it shuts down. To reach this goal we introduced several new packages and features.
When using Enhanced Write Filter (EWF) in RAM or RAMREG mode several customers might assume the EWF overlay is limited solely by the availability of physical memory. Consequently, many assume they will be able to achieve an overlay twice as big on a system with 2 GB RAM than on a system with 1 GB RAM. This is not true by any means. This article explains the factors that limit the overlay size and the significant improvements seen on Windows Embedded Standard 2011.
If you are interested more in the conclusion than the internals, skip the following sections and jump directly to the “Results and Conclusion” section.