Component
|
Device Driver componentizing
|
Creating driver components
|
Component
|
Bug in componentized security update
|
Deploying Microsoft security updates
1. Make sure all the very latest updates have been installed in your component database from the OEM Secure web site (obtain access through your license distributor).
2. Contact Microsoft Support
|
Component
|
Componentizing an application (your application or a third party's)
|
Creating custom components
|
Component
|
EEF; EWF with HORM
|
Hibernation and EWF
|
Component
|
EEF; EWF or FBWF and Registry Filter (domain joining or Remote Desktop TSCAL license issue)
|
Registry Filter
|
Component
|
EEF; SDI
|
System Deployment Image
Booting from an SDI file
RAM boot using SDI
SDI
|
Component
|
Event Viewer; messages incomplete or cryptic
|
Event Logging
Incomplete Event log messages are typically due to missing Event Log registry keys
|
Component
|
Missing; preventing an OEM or third party app from running correctly
|
Creating custom components
Dependency Walker
PC Magazine InCtrl5
Filemon
Regmon
If your application runs in XP Pro but not Standard 2009, then one or more components may be missing in the Standard 2009 design, that your application depends on. Use Inctrl5, Dependency Walker, FileMon, RegMon etc. as needed to analyze missing binaries and registry entries. Use these tools to monitor your application in both XP Pro and Standard 2009.
|
Component
|
Searching for components
|
Search for the component by name in this document.
Search the companion spreadsheet "Windows Embedded Standard 2009 Components.xls".
Search by component name in Target Designer's leftmost pane.
|
Component
|
WMI
|
Search the companion spreadsheet "Windows Embedded Standard 2009 Components.xls" for all components containing "WMI" or sort on its WMI column.
|
Component
|
WMI; Performance Counters do not work
|
Some performance counters such as processor related counters require that the pagefile be turned on in order to work. Choose one of three options:
1. Turn on pagefile support in your Processor component and rebuild the image.
2. Build image with pagefile turned off and then after image has completed FBA, enable perfos.dll using EXCTRLST.EXE (a tool that comes with the Support Tools on the XP Pro CD)
3. Apply the following hotfix: KB884558. If you are the OEM and this resolves the issue, contact Microsoft support to obtain an OEM redistribution license for this hotfix.
|
Device driver
|
Programmatic starting, stopping and disabling
|
1. Use the Devcon.exe tool, compile the source code available in the Windows Driver Kit.
2. Or obtain Devcon.exe here: KB311212
|
End user
|
An end user of an XPe device has questions or problems.
|
The OEM is responsible for end user support.
Chapter 6. Servicing
|
End user
|
End user Wishes to enhance an OEM device image (such as a Wyse or HP thin client device)
|
Image ownership considerations
End users need to contact the OEM (Wyse or HP) for advice regarding allowed image modifications. Thin clients are still "limited functionality runtime devices" per licensing agreement.
|
FBA
|
Blue screen / hangs
|
Troubleshoot First Boot Agent errors yourself
|
FBA
|
Continuous rebooting
|
First Boot Agent (FBA) reboots repeatedly
|
FBA
|
Fails with error messages
|
Troubleshoot First Boot Agent errors yourself
|
Feature
|
Looking for a specific component feature functionality or availability
|
Search for desired components by keyword or category, in the "Windows Embedded Standard 2009 Components.xls" spreadsheet.
|
Feature
|
Hard fail OS problem; Hard failure, likely due to a Standard 2009 component not functioning / component bug
|
Development Master Checklist
A necessary component is probably missing.
1. Use development procedures to ensure that critical boot devices are properly set up
2. Search for desired components by keyword or category, in the "Windows Embedded Standard 2009 Components.xls" spreadsheet.
|
Feature
|
Intermittent OS problem; Intermittent feature functionality (likely an XP Pro issue)
|
Intermittent issues are typically not caused by missing Standard 2009 components. If possible, see if the issue can reproduce in a full XP Pro environment. In any event, treat the issue as an XP Pro type troubleshooting issue, not Standard 2009.
|
Feature
|
Minlogon vs. Windows Logon tradeoffs
|
Winlogon vs. Minlogon
Introduction to Minlogon
Also search this document for "Minlogon".
|
Getting started
|
Differences between Operating System (OS) platforms and versions
|
How can I identify Operating System version, Service Pack level, and specific XP Embedded platform?
Chapter 2. Overview and Evaluation
|
Headless design
|
Developing and/or servicing a device that uses no video and/or keyboard and/or mouse
|
Headless System
Headless Device Video Driver Processing
|
Disk image
|
Footprint (disk image size) reduction
|
Image Footprint Reduction
|
Disk image
|
Servicing issues or questions
|
Chapter 6. Servicing
|
Disk image
|
Storage media preparation (initializing and formatting)
|
Preparing storage media for EWF
BootPrep
|
Disk image
|
Surprise power loss / image / hard disk corruption
|
File system and/or disk media content corruption issues
|
Disk image
|
Cloning and FBRESEAL problems including machine ident/uniqueness
|
MSDTC and Cloning
System Cloning Tool and FBRESEAL
System cloning / Fbreseal
|
Disk image
|
Image upgrade; CMI errors and/or the design will no longer load.
|
Your design reports CMI Error 0x800A01C9 (or other CMI errors)
Other CMI Errors encountered
|
Disk image
|
Design fails to boot
|
When you boot your Standard 2009 runtime for the first time, you receive an error message
The target Standard 2009 system hangs or produces a blue screen upon first boot
You receive an "NTLDR missing" error message before you receive the operating system selection screen
You receive a "HAL.DLL not found" error message after you receive the operating system selection screen
You receive a "Computer disk hardware configuration" error message after you receive the operating system selection screen
How to avoid receiving a "Missing pci.sys" error message or avoid missing other critical boot devices during initial boot of the runtime
How to avoid the "Stop Error 6B" error during the initial boot of the runtime
How to avoid the "Stop Error 7B" error during the initial boot of the runtime
The embedded device skips the operating system selection menu
The embedded device reboots after you select an operating system
A blue screen occurs, displaying Bugcheck 74 "BAD_SYSTEM_CONFIG_INFO", STOP: 0x00000074
|
License
|
Run time license does not work
|
How do I obtain and configure Licensing PIDs?
How to upgrade your database to the licensed version
|
License
|
Upgrading from eval to licensed
|
How to upgrade your database to the licensed version
|
NT Embedded
|
(Windows NT Embedded is no longer formally supported)
|
-
|
Package
|
MUI or Language Support questions or issues
|
Multilingual User Interface (MUI)
Multilingual User Interface Pack
|
Performance
|
Boot time optimizing
|
Boot time performance
The fastest boot performance can generally be obtained using HORM:
Hibernation and EWF
Minlogin can also shorten the boot time, however User Account functionality is lost which causes many other features that depend on User Accounts, crypto etc. will no longer function:
Winlogon vs. Minlogon
Introduction to Minlogon
|
Performance
|
Run time optimizing
|
Boot time performance
EWF Performance Considerations
Maximizing performance of Remote Boot clients
Growing EWF files when using EWF-RAM
|
Performance
|
Real time performance questions
|
Whether Standard 2009 can accommodate your specific real time performance needs depends on many factors. Worst case latency depends on the latency of the slowest device drivers installed in the system. If quicker response time or more accurate I/O timing is needed, consider third party tools (search the internet using these search terms: "xp embedded" "real time") and/or consider implementing custom hardware with a dedicated microcontroller as a buffering liaison between Standard 2009 and the real world.
|
Post-FBA configuration
|
3rd party Anti-virus
|
Runtimes and Antivirus Software
|
Post-FBA configuration
|
OS Feature settings customization
|
Development Master Checklist
Quality Assurance Checklist
|
Servicing
|
Configuring an image for debuggability, including crash dump (dump files) capability, and configuring an image with necessary debug tools.
|
Debugging
Introduction to the Windows Embedded Standard 2009 Component Manifest
Component development, debugging and testing tools
Hodge Podge Lodge: Remote Debugging, Localization, and Globalization in Windows XP Embedded
How to judge whether a previous DUA command was successful or failed
|
Servicing
|
Deploying SCCM (SMS) or WSUS (SUS)
|
System Center Configuration Manager (SCCM)
Device deployment and servicing options
Systems Management Server (SMS)
Managing Windows XP Embedded Systems with SMS 2003 sp3
Windows System Update Server Version 2.0 (WSUS)
Using SUS with Windows XP Embedded Service Pack 2
|
Servicing
|
Update or Hotfix Request - XP Pro feature specific
|
Can I use Windows XP desktop Updates (hot fixes) in a deployed Standard 2009 runtime?
You can typically download hotfixes (for test purposes only) directly from the web. For example:
Availability of Windows XP COM+ Hotfix Rollup Package 9
|
Tools Installation
|
Problem installing tools and/or database
|
Problems installing Standard 2009 Studio
|
Tools
|
ImageDiff
|
Using Image Difference Engine (ImageDiff)
|
Tools
|
Learning and using Component Designer
|
Component Designer
|
Tools
|
Learning and using Target Designer
|
Target Designer
|
Tools
|
SQL Server; Cannot connect to component database
|
Administering a Shared Database
Note that Standard 2009 accommodates Target Designer and Component Designer running on a different computer than where the Component Database resides. For each computer, edit the Component Database Manager's Database server location in order to reference the computer that contains the Component Database. If only one computer is used, the default Database server location is the name of the computer.
|
Tools
|
Target Analyzer (TAP)
|
Target Analyzer
|
Tools
|
Target Design file (.slx) will not load (CMI errors)
|
Your design reports CMI Error 0x800A01C9 (or other CMI errors)
Other CMI Errors encountered
|
Tools
|
Target Designer; one or more components have a round blue up-arrow icon associated with it.
|
From Target Designer use Configuration->Upgrade Configuration to ensure that the design gets updated with the latest components. Then run Dependency Checker and save the updated design.
|
Tools
|
Target Designer; Dependency check fails with errors
|
This can happen if the design (.SLX) version is out of sync with the Component Database version.
1. If you have made updates to the Component Database, your design (.SLX) is old and needs updating. From Target Designer use Configuration->Upgrade Configuration to ensure that the design gets updated with the latest components. Then run Dependency Checker.
2. If the version of the component database is older than the version of the design (.SLX) or is missing components that are referenced in the design, upgrade the component database to the latest Service Pack and then install the latest Security Updates from the OEM Secure web site. Install your custom components that are referenced in the design. Then try loading your design.
If the above does not apply, the component database is likely corrupted; reinstall.
|
Tools
|
WinPE
|
Deploying images using Windows Preinstallation Environment
RAM boot and WinPE
RAM boot using SDI
|
XP Pro inherited
|
Service; creating, starting, stopping and disabling
|
Using Component Designer to create a Service Resource for a component
How to create a Windows service by using Sc.exe
Controlling a Service using SC
|
Feature
|
Shell / UI configuration
|
Configuring the User Interface (shell)
|
License
|
Requesting an OEM Redistribution license for a Standard 2009 feature intended for end users
|
The OEM (Standard 2009 image developer) should work with their Microsoft Technical Account Manager regarding licensing issues.
|
