Remotely administered XPE runtimes do not work correctly (331042)


The information in this article applies to:

  • Microsoft Windows XP Embedded SP1
This article was previously published under Q331042

SYMPTOMS

When you build a runtime for a remotely administered device (also known as a headless device) by using Microsoft Windows XP Embedded Service Pack 1 (SP1), the device does not start correctly. However, because the device is remotely administered, you have no way to know that the device is not starting.

A headless device is a device that does not have any display hardware. There is no hardware to display the status of the device or its operations.

CAUSE

This problem occurs because a remotely administered device does not have a display driver. Microsoft Windows XP-based systems require a display driver to start. Because a remotely administered system has no display hardware, a remotely administered system does not load display drivers. Therefore, Windows XP does not successfully start the device.

RESOLUTION

This problem is resolved by an update to Windows XP Embedded SP1. This update creates a new component that is named Virtual Display Driver. The new component provides the display driver that Windows XP requires. However, the new component does not require underlying display hardware to successfully load and run.

Note The workaround is easier to implement than the update.

WORKAROUND

To work around this problem, add the NetMeeting component to your runtime. This action provides the system with a virtual display driver.

This workaround has a larger runtime footprint than the runtime footprint of the update.

MORE INFORMATION

This problem does not occur with Microsoft Windows XP Embedded.
Modification Type:MajorLast Reviewed:2/24/2004
Keywords:kbQFE kbfix kbprb KB331042 kbAudDeveloper kbAudOEM
©2004 Microsoft Corporation. All rights reserved.