Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
In Windows Embedded Standard 2011, the Distribution share (DS) is a critical element in creating customized Windows images. If you have used Image Configuration Editor (ICE), you would have noticed that packages are well organized into a tree structure that represents the DS. During development, users might need to use other packages in addition to the ones already found in the DS. Examples include new package releases from the Windows Embedded team (security updates, hot fixes, new versions of the same package, etc...) as well as 3rd party supplied packages (e.g. 3rd party driver packages).
Windows Embedded Standard 2011 allows you to maintain the DS (for example you can add a new driver package or an update package) by using one of the supplied utilities that come with the Stnadard 2011 tools, importpackage.exe. This tool enables you to:
As PC users & developers, we are faced with situations where we want to save the current state of the operating system along with its applications. One such situation is when developers have to reproduce a bug in the system/application that is hard to recreate or that occurs only occasionally. The Snapshot feature in Hyper-V is a developer’s dream in this regard- capable of saving the current state of the OS and its applications. Later, a dev can choose to restore to the saved state as many times as possible to work on the hard-to-create OS/Application state.
PC users & developers can now play with installing different applications, tweaking some system settings, editing the registry and easily go back to the previous state of the OS with the cool snapshot feature.
Here are a few scenarios where snapshots are quite handy for Windows Embedded Standard 2011 Developers:
[The following article is authored by one of the Windows Embedded MVPs (Most Valuable Professionals). Our MVPs have a heavy background in Embedded systems and are a great repository of information on Windows Embedded products. We’re providing this space on our team blog as a service to our readers by allowing MVPs to share some of their knowledge with the rest of the community.]
If one is building just a single device, it is certainly not necessary to think about configuration strategies. However, when the device gets rolled out in different versions or if your device is part of a device family, a well designed configuration strategy can help overcome versioning obstacles and save a lot of time.
Separate hardware and software