What's New in the February 2013 release of Standard 7 Documentation (Standard 7 SP1)
7/8/2014
Your ratings and feedback about the accuracy and thoroughness of Windows Embedded Standard 7 documentation are important to us. We review your input to understand how you would like us to improve a topic. In this release, we updated the following topics as a direct result of your input.
Concepts
- Compare Standard 7 32-bit and 64-bit
Updated to better explain when and why you would use the 32-bit version or the 64-bit version of Standard 7.
- How Configuration Passes Work
Updated to describe configuration passes as part of the Windows operating system that Image Builder uses to determine when to apply settings in an unattended installation answer file. A new image shows when the configuration passes run, and two new procedures describe how to work with configuration passes to complete typical tasks like building a reference image or modifying and deploying a reference image on devices.
Settings
- EnablePrefetcher
Added a description of Prefetch, a tool that can load application data into memory before it is demanded, and added values that show how the setting works.
- EnableSuperfetch
Added a description of SuperFetch, a tool that improves on Prefetch by monitoring which applications you use the most and preloading those into system memory. We also added values that show how the setting works.
Building and Deploying an Image
- Bootable Windows USB Stack
To avoid confusion, added an introduction to describe that you use the Bootable Windows USB Stack, an Embedded Enabling Feature, to start a Standard 7 image from a USB mass storage device. Deleted the topic “Build a Bootable USB Image” and directed readers to “Create a Bootable USB Flash Drive” for information about how to create a bootable USB Flash Drive (UFD) so that they can capture or extract an image on a device.
- Build an Answer File Using Image Configuration Editor
Updated to include more information about what it means to build an image and to help you choose whether to use Image Builder Wizard (the express method) or Image Configuration Editor( the advanced method) to build an image. We also describe how to use these tools to create an answer file and then deploy it to your image.
- Build Your First Standard 7 Image Using Image Builder Wizard
Renamed from “Build Your First Windows Embedded Standard 7 Image” and added information to make it clear how to use Image Builder Wizard to build a minimal Standard 7 image. We also streamlined the procedural steps so that they are clearer and can be more easily followed.
- Capture and Mount an Image
Renamed from “Capture an Image” and updated the topic to walk through the process of using ImageX to capture an image, and then mount it as a new volume with a drive letter associated so that you can read or change the contents.
- Create a Bootable USB Flash Drive
Renamed from “Create a Bootable Utility Image” to avoid confusion and streamlined and clarified the steps to create a USB flash drive (UFD). We also merged information from “Files for a Bootable Utility Disk” and “Create a Bootable Utility UFD” into this topic, and then deleted those topics.
- Configure an Answer File to Be Unattended
Updated the procedure to be clearer and more easily followed.
- Install the Windows Image File System Filter Driver
Corrected information about how to install the Windows Imaging File System Filter (WIM FS Filter) driver from the Standard 7 installation disk and also described how to install the driver from a custom source. You must install the WIM FS Filter driver before you can mount an image using ImageX.
Troubleshooting and Maintenance
- Maintain an Image Using a Configuration Set and DISM
Updated the procedure to be clearer and more easily followed, and added a Troubleshooting section that describes how to fix an error message.
- Troubleshooting EWF
Added information about the purpose of Enhanced Write Filter (EWF) and linked to EWF performance considerations and topics to help you verify that your system meets system requirements and that it has sufficient RAM to store overlay data in memory.