Packages (Standard 7 SP1)
7/8/2014
Windows Embedded Standard 7 consists of Windows Embedded Core and many packages that contain all functionality available in the Windows 7 Ultimate operating system. A package is a part of the operating system (OS) that contains the files, resources, and settings required for specific functionality.
Note
In Standard 7, a package is the smallest unit of functionality that can be added or removed from an image.
Each package is available for both x86 and AMD64 architectures.
Categories
Standard 7 assigns each package a category that describes the feature area of the package. An example of a category is Diagnostics or Graphics and Multimedia. Standard 7 uses categories to organize and display packages in the Image Configuration Editor user interface.
Package Types
The following table shows the package types available in Standard 7.
Package Type |
Package Contents |
Example |
|---|---|---|
Feature Pack |
A collection of related Standard 7 components that implement a specific OS functionality. |
|
Language Pack |
Resources for a specific language or locale that have been fully or partially localized. |
|
Driver Pack |
Non-core inbox drivers for a device or group of devices. |
|
Embedded Enabling Feature (EEF) |
Files and resources for an Embedded Enabling Feature. |
|
Windows Update |
Software update that contains security or performance improvements for Standard 7. |
|
Packages are contained in .cab files that are digitally signed by Microsoft.
Note
Third-party applications, out-of-box drivers, and Standard 7 service packs are not packages. So, they do not have a package type and are added and removed from images differently than packages.
Feature Sets
Most packages are a member of a feature set. This is a group of packages where all the packages either make up or improve the same functionality. Two examples of a feature set are Internet Explorer and Wireless Networking.
Families
A few packages are a member of a family. This is a set of packages where each package has similar functionality to all the other packages. Two examples of a family are Login Shells or Windows Media Player Skins.
Dependencies
Frequently, a package depends on another package or multiple packages. A package can have a dependency on packages, families, or both. To learn more about package dependencies in Standard 7, see Dependencies.
Working with Packages
Packages can be added or removed from Standard 7 while you are designing the image or after the image has been deployed. Different tools are available to work with packages at different stages, depending on the package type.
Stage |
Tool |
Package Type |
|---|---|---|
Designing Your Image: Image Builder |
Image Builder Wizard |
|
Designing Your Image: Image Builder |
Drvload |
|
Designing Your Image: Image Builder in unattended mode |
Image Configuration Editor |
|
Servicing Your Image: Online |
Lpksetup.exe |
|
Servicing Your Image: Online |
Deployment Image Servicing and Management (DISM) with Image Configuration Editor |
|
Servicing Your Image: Offline |
Deployment Image Servicing and Management (DISM) with Image Configuration Editor and ImageX |
|