When you use the 1004 battery API test case in the Windows CE Test Kit for Windows Embedded CE 6 R2 to test the BatteryGetLifeTimeInfo function, you receive an incorrect result.

Back to the top

This problem occurs because of a problem in the test case. If you call the BatteryGetLifeTimeInfo function by using NULL as a parameter, the function returns 0. However, the test case expects the return result to be 87.

Back to the top

Software update information

A supported software update is now available from Microsoft as Windows CE 6.0 Platform Builder Monthly Update (April 2008). 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:For 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:

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 clean the platform, click Clean on the Build menu. To build the platform, click Build Platform on the Build menu. 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-080408-kb950628-armv4i.msi	444,928	09-Apr-2008	00:58
Wincepb60-080408-kb950628-mipsii.msi	449,536	09-Apr-2008	00:58
Wincepb60-080408-kb950628-mipsii_fp.msi	449,536	09-Apr-2008	00:58
Wincepb60-080408-kb950628-mipsiv.msi	450,560	09-Apr-2008	00:58
Wincepb60-080408-kb950628-mipsiv_fp.msi	451,072	09-Apr-2008	00:58
Wincepb60-080408-kb950628-sh4.msi	443,904	09-Apr-2008	00:58
Wincepb60-080408-kb950628-x86.msi	445,440	09-Apr-2008	00:58

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
Batapitest.dll	19,968	05-Apr-2008	21:02	pb\cepb\wcetk\ddtk\armv4i
Batapitest.dll	24,576	05-Apr-2008	18:40	pb\cepb\wcetk\ddtk\mipsii
Batapitest.dll	24,576	05-Apr-2008	23:28	pb\cepb\wcetk\ddtk\mipsii_fp
Batapitest.dll	25,088	06-Apr-2008	04:18	pb\cepb\wcetk\ddtk\mipsiv
Batapitest.dll	25,088	06-Apr-2008	01:53	pb\cepb\wcetk\ddtk\mipsiv_fp
Batapitest.dll	17,920	06-Apr-2008	06:40	pb\cepb\wcetk\ddtk\sh4
Batapitest.dll	16,896	06-Apr-2008	08:58	pb\cepb\wcetk\ddtk\x86

Back to the top

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

Back to the top

The following is the 1004 battery API test case:

   BEGIN TEST: "BatteryGetLifeTimeInfo", Threads=0, Seed=31702
      Calling BatteryGetLifeTimeInfo(x, x, x)
      Calling BatteryGetLifeTimeInfo(NULL, x, x)
      GetLastError is 0.
      ERROR:  The error code returned is 0, while the expected value is 87.
      Calling BatteryGetLifeTimeInfo(x, NULL, x)
      GetLastError is 0.
      ERROR:  The error code returned is 0, while the expected value is 87.
      Calling BatteryGetLifeTimeInfo(x, x, NULL)
      GetLastError is 0.
      ERROR:  The error code returned is 0, while the expected value is 87.
   END TEST: "BatteryGetLifeTimeInfo", FAILED, Time=0.004

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

Back to the top