Microsoft
Windows Embedded Home
Intelligent Systems
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
Resources
HORM imposes the following restriction on volumes –
[OR]
Read More...
Comments Product Updates
Crash dumps can be configured via the control panel or by editing the relevant registry entries as shown below. Additional details can be found in KB article 307973.
Via Control Panel
[Today’s post is provided by guest blogger, Levi Stevens]
In a default installation of Configuration Manager 2007, you cannot use a query to return devices running Windows Embedded operating systems prior to Windows Embedded Standard 2009. You can, however, extend the hardware inventory in Configuration Manager 2007 to collect further information about the operating product suite which can be used to build queries that return all Windows Embedded computers.
Use the following procedure to extend Configuration Manager 2007 hardware inventory to collect information that can be used in queries to identify all Windows Embedded computers:
Many of you must be wondering what SMI settings are and how these settings could be used to configure Windows Embedded Standard 7 image. Let me explain…
Settings Management Infrastructure (SMI) is a schema that is used to define mutable operating system settings. A mutable setting is a variable setting in which the value of the setting can be changed, either by other components or by the user or administrator. For example, user-preferred fonts and font colors are mutable settings.
Mutable settings can reside in any settings store in the operating system, such as the registry, .ini files, or some other public store, such as the IIS Metabase or the WMI repository. These settings are exposed to OEMs and Corporations to enable customization and make deployment of the OS easier.
In Windows Embedded Standard 7, these settings are included with each component in a Feature Package. In ICE, once you select a feature package to be included in your answer file, you will be presented with a list of settings that correspond to every component in the package you selected.
This is the third and final blog in a series of articles which discusses the troubleshooting and diagnosis of driver installation issues in Windows Embedded Standard 7. Previously we presented the format of the SetupAPI.dev.log file and an example driver installation scenario. Now we will begin by enumerating some common driver installation issues you may encounter in Windows Embedded Standard 7.