Article ID: 835774 - Last Review: May 27, 2005 - Revision: 1.4 FIX: Incorrect destination results are produced when you use the memcpy() function or the memmove() functionOn This PageSYMPTOMSThe memcpy() function and the memmove() function may produce incorrect destination results on ARM920T-based microprocessors. Sometimes, when you are working with menus and icons, areas of incorrectly colored pixels appear on video display output. CAUSEThis problem occurs because the Logical Disk Manager (LDM) does not work correctly in some revisions of the ARM 920T processor core. This problem may also occur on the ARM922T processor core. This problem may be caused in the Microsoft Windows CE implementation of the memcpy() function and the memmove() function by the use of hand coded assembly language. RESOLUTIONHotfix InformationA supported software update is now available from Microsoft as Windows CE 4.2 Core OS QFE 835774. 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
(http://support.microsoft.com/kb/837392/
)
How to locate core operating system fixes for Microsoft Windows CE Platform Builder products PrerequisitesThis fix is supported only when all previously issued fixes for this product have also been installed.Restart RequirementAfter you install this update, you must clean and build the whole platform. You do not have to restart your computer after you apply this fix.Hotfix Replacement InformationThis fix does not replace any other fixes.File InformationThe English version of this package has the file attributes (or later) that are listed in the following table.Date Time Version Size File name ----------------------------------------------------------------------------------- 16-Mar-2004 23:50 4.2.4.316 2,484,976 Wincepb42-040316-kb835774-armv4.exe 16-Mar-2004 23:50 4.2.4.316 2,489,072 Wincepb42-040316-kb835774-armv4i.exe Date Time Version Size File name -------------------------------------------------------------- Path: Public\Common\Oak\Lib\ARMV4\Debug 06-Mar-2004 01:36 1,347,078 Ccrtcrtw.lib 06-Mar-2004 01:36 43,702 Ccrtstrg.lib 06-Mar-2004 01:36 1,779,252 Corecrt.lib 06-Mar-2004 01:36 1,855,204 Fulllibc.lib Path: Public\Common\Oak\Lib\ARMV4\Retail 06-Mar-2004 01:34 1,154,358 Ccrtcrtw.lib 06-Mar-2004 01:34 42,500 Ccrtstrg.lib 06-Mar-2004 01:35 1,563,660 Corecrt.lib 06-Mar-2004 01:35 1,638,470 Fulllibc.lib Path: Public\Common\Oak\Lib\ARMV4I\Debug 06-Mar-2004 01:39 1,349,986 Ccrtcrtw.lib 06-Mar-2004 01:39 43,882 Ccrtstrg.lib 06-Mar-2004 01:39 1,783,406 Corecrt.lib 06-Mar-2004 01:39 1,861,906 Fulllibc.lib Path: Public\Common\Oak\Lib\ARMV4I\Retail 06-Mar-2004 01:37 1,157,146 Ccrtcrtw.lib 06-Mar-2004 01:37 42,676 Ccrtstrg.lib 06-Mar-2004 01:37 1,567,756 Corecrt.lib 06-Mar-2004 01:37 1,645,146 Fulllibc.lib STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
