FIX: The video render filter cannot use a custom FourCC color format to render video frames in Windows Embedded CE 6.0

Symptoms

Consider the following scenario.

  • You have a Windows Embedded CE 6.0-based image that supports DirectDraw and Windows Media Player.
  • You define a custom four character code (FourCC) code format in DirectDraw.
  • You try to play a file that is encoded by the custom format.

In this scenario, the video render filter cannot use the color format to render video frames. Instead, the filter uses other formats.

Cause

This problem occurs because the public format table was statically referenced by private Graphical Device Interface (GDI) code. Therefore, the changes to the color format table are not reflected in the version that GDI uses. When the video render filter requests a custom format, GDI cannot respond to the request.

Resolution

Software update information

A supported software update is now available from Microsoft as Windows CE 6.0 Platform Builder Monthly Update (February 2009). You can confirm this by scrolling to the "File information" section of this article. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is:

Product version-yymmdd-kbnnnnnn-processor typeFor example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about obtaining Windows CE Platform Builder and core operating system software updates:

837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder productsNote After you install the hotfix, both public code and private code can share a common reference table.

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this software update, you must perform a clean build of the whole platform. To do this, use one of the following methods:

  • On the Build menu, click Clean, and then click Build Platform
  • On the Build menu, click Rebuild Platform.

You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this software update package has the file attributes or the later file attributes that are listed in the following table.

File name File size Date Time
Wincepb60-090226-kb960707-armv4i.msi 3,138,560 26-Feb-2009 23:07
Wincepb60-090226-kb960707-mipsii.msi 3,008,000 26-Feb-2009 23:07
Wincepb60-090226-kb960707-mipsii_fp.msi 3,009,536 26-Feb-2009 23:07
Wincepb60-090226-kb960707-mipsiv.msi 3,043,328 26-Feb-2009 23:07
Wincepb60-090226-kb960707-mipsiv_fp.msi 3,042,816 26-Feb-2009 23:07
Wincepb60-090226-kb960707-sh4.msi 3,007,488 26-Feb-2009 23:07
Wincepb60-090226-kb960707-x86.msi 2,767,872 26-Feb-2009 23:07

The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name File size Date Time Path
Windows embedded ce 6.0_update_kb960707.htm 8,006 26-Feb-2009 23:03 090226_kb960707
Halcaps.cpp 10,028 13-Feb-2009 23:51 Public\Common\Oak\Drivers\Display\Ragexl\Driver
Ddgpe.h 16,721 13-Feb-2009 23:51 Public\Common\Oak\Inc
Ddrawi.h 37,004 13-Feb-2009 23:51 Public\Common\Oak\Inc
Ddcore.lib 1,735,624 13-Feb-2009 23:44 Public\Common\Oak\Lib\Armv4i\Debug
Ddi_ragexl_lib.lib 2,742,168 13-Feb-2009 23:45 Public\Common\Oak\Lib\Armv4i\Debug
Ddcore.lib 1,158,078 13-Feb-2009 23:44 Public\Common\Oak\Lib\Armv4i\Retail
Ddi_ragexl_lib.lib 2,136,580 13-Feb-2009 23:44 Public\Common\Oak\Lib\Armv4i\Retail
Ddcore.lib 1,709,480 13-Feb-2009 23:45 Public\Common\Oak\Lib\Mipsii\Debug
Ddi_ragexl_lib.lib 2,497,258 13-Feb-2009 23:46 Public\Common\Oak\Lib\Mipsii\Debug
Ddcore.lib 1,136,632 13-Feb-2009 23:45 Public\Common\Oak\Lib\Mipsii\Retail
Ddi_ragexl_lib.lib 1,954,234 13-Feb-2009 23:46 Public\Common\Oak\Lib\Mipsii\Retail
Ddcore.lib 1,709,572 13-Feb-2009 23:47 Public\Common\Oak\Lib\Mipsii_fp\Debug
Ddi_ragexl_lib.lib 2,500,034 13-Feb-2009 23:47 Public\Common\Oak\Lib\Mipsii_fp\Debug
Ddcore.lib 1,136,796 13-Feb-2009 23:46 Public\Common\Oak\Lib\Mipsii_fp\Retail
Ddi_ragexl_lib.lib 1,954,182 13-Feb-2009 23:47 Public\Common\Oak\Lib\Mipsii_fp\Retail
Ddcore.lib 1,738,508 13-Feb-2009 23:48 Public\Common\Oak\Lib\Mipsiv\Debug
Ddi_ragexl_lib.lib 2,541,732 13-Feb-2009 23:49 Public\Common\Oak\Lib\Mipsiv\Debug
Ddcore.lib 1,154,410 13-Feb-2009 23:48 Public\Common\Oak\Lib\Mipsiv\Retail
Ddi_ragexl_lib.lib 1,978,558 13-Feb-2009 23:48 Public\Common\Oak\Lib\Mipsiv\Retail
Ddcore.lib 1,738,600 13-Feb-2009 23:49 Public\Common\Oak\Lib\Mipsiv_fp\Debug
Ddi_ragexl_lib.lib 2,541,596 13-Feb-2009 23:50 Public\Common\Oak\Lib\Mipsiv_fp\Debug
Ddcore.lib 1,154,574 13-Feb-2009 23:49 Public\Common\Oak\Lib\Mipsiv_fp\Retail
Ddi_ragexl_lib.lib 1,975,144 13-Feb-2009 23:50 Public\Common\Oak\Lib\Mipsiv_fp\Retail
Ddcore.lib 1,582,142 13-Feb-2009 23:51 Public\Common\Oak\Lib\Sh4\Debug
Ddi_ragexl_lib.lib 2,291,750 13-Feb-2009 23:51 Public\Common\Oak\Lib\Sh4\Debug
Ddcore.lib 1,082,584 13-Feb-2009 23:50 Public\Common\Oak\Lib\Sh4\Retail
Ddi_ragexl_lib.lib 1,869,812 13-Feb-2009 23:51 Public\Common\Oak\Lib\Sh4\Retail
Ddcore.lib 1,488,092 13-Feb-2009 23:43 Public\Common\Oak\Lib\X86\Debug
Ddi_ragexl_lib.lib 2,160,488 13-Feb-2009 23:43 Public\Common\Oak\Lib\X86\Debug
Ddcore.lib 1,015,320 13-Feb-2009 23:42 Public\Common\Oak\Lib\X86\Retail
Ddi_ragexl_lib.lib 1,866,814 13-Feb-2009 23:43 Public\Common\Oak\Lib\X86\Retail

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates