Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The system cannot set the debug zones for a module that is loaded in "boot phase 0" in Windows Embedded CE 6.0 R3

FIX: The system cannot set the debug zones for a module that is loaded in "boot phase 0" in Windows Embedded CE 6.0 R3

Symptoms

Consider the following scenario:
  • You have a Windows Embedded CE 6.0 R3-base image on a device.
  • The image includes a module that is configured to be loaded in boot phase 0.
  • You set the initial debug zones in the registry for the module and then start the device.

In this scenario, you find that the system recognize the debug zones that are set in the registry. Additionally, the system cannot print expected debug information for the module.

↑ Back to the top

Resolution

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Monthly Update March 2012. In the "File information" section, the package file name contains the product version, the date, the Knowledge Base article number, and the processor type. The package file name format is as follows:
Product version-yymmdd-kbnnnnnn-processor type
For example, Wincepb60-110128-kb2492159-armv4i.msi is the ARMV4i Windows Embedded CE 6.0 Platform Builder fix that is documented in KB article 2492159 and that is contained in the January 2011 monthly update.

To resolve this problem immediately, download this Windows Embedded CE 6.0 Monthly Update from the following Microsoft website.

Microsoft Download Center
Windows Embedded CE 6.0

Prerequisites

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

Restart requirement

After you apply this 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 Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
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 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.

Files that are included in this update package
File nameFile sizeDateTimePath
Kmisc.c56,38005-Mar-201222:56Private\Winceos\Coreos\Nk\Kernel
Nkmain.lib2,746,11205-Mar-201222:53Public\Common\Oak\Lib\Armv4i\Debug
Nkprmain.lib2,782,97205-Mar-201222:53Public\Common\Oak\Lib\Armv4i\Debug
Nkmain.lib1,767,37405-Mar-201222:53Public\Common\Oak\Lib\Armv4i\Retail
Nkprmain.lib1,792,80205-Mar-201222:53Public\Common\Oak\Lib\Armv4i\Retail
Nkmain.lib2,588,56005-Mar-201222:54Public\Common\Oak\Lib\Mipsii\Debug
Nkprmain.lib2,624,54605-Mar-201222:54Public\Common\Oak\Lib\Mipsii\Debug
Nkmain.lib1,676,66205-Mar-201222:54Public\Common\Oak\Lib\Mipsii\Retail
Nkprmain.lib1,706,80605-Mar-201222:54Public\Common\Oak\Lib\Mipsii\Retail
Nkmain.lib2,663,40805-Mar-201222:54Public\Common\Oak\Lib\Mipsii_fp\Debug
Nkprmain.lib2,699,67005-Mar-201222:54Public\Common\Oak\Lib\Mipsii_fp\Debug
Nkmain.lib1,736,36405-Mar-201222:54Public\Common\Oak\Lib\Mipsii_fp\Retail
Nkprmain.lib1,766,61605-Mar-201222:54Public\Common\Oak\Lib\Mipsii_fp\Retail
Nkmain.lib2,621,01405-Mar-201222:55Public\Common\Oak\Lib\Mipsiv\Debug
Nkprmain.lib2,657,13205-Mar-201222:55Public\Common\Oak\Lib\Mipsiv\Debug
Nkmain.lib1,701,89005-Mar-201222:55Public\Common\Oak\Lib\Mipsiv\Retail
Nkprmain.lib1,731,93605-Mar-201222:55Public\Common\Oak\Lib\Mipsiv\Retail
Nkmain.lib2,701,12405-Mar-201222:56Public\Common\Oak\Lib\Mipsiv_fp\Debug
Nkprmain.lib2,737,51805-Mar-201222:56Public\Common\Oak\Lib\Mipsiv_fp\Debug
Nkmain.lib1,768,05205-Mar-201222:55Public\Common\Oak\Lib\Mipsiv_fp\Retail
Nkprmain.lib1,798,20205-Mar-201222:55Public\Common\Oak\Lib\Mipsiv_fp\Retail
Nkmain.lib2,183,02405-Mar-201222:56Public\Common\Oak\Lib\Sh4\Debug
Nkprmain.lib2,208,25605-Mar-201222:56Public\Common\Oak\Lib\Sh4\Debug
Nkmain.lib1,520,14205-Mar-201222:56Public\Common\Oak\Lib\Sh4\Retail
Nkprmain.lib1,544,51405-Mar-201222:56Public\Common\Oak\Lib\Sh4\Retail
Nkmain.lib2,174,47005-Mar-201222:53Public\Common\Oak\Lib\X86\Debug
Nkprmain.lib2,202,60205-Mar-201222:53Public\Common\Oak\Lib\X86\Debug
Nkmain.lib1,532,11205-Mar-201222:52Public\Common\Oak\Lib\X86\Retail
Nkprmain.lib1,552,12405-Mar-201222:52Public\Common\Oak\Lib\X86\Retail

↑ Back to the top

References

For more information about how to set initial debug zones in the registry, visit the following Microsoft Developer Network (MSDN) website:
Setting Initial Debug Zones (Windows Embedded CE 6.0)
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

↑ Back to the top

Keywords: kbqfe, kbfix, kbnotautohotfix, kbpubtypekc, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2684184
Revision : 1
Created on : 1/7/2017
Published on : 4/10/2012
Exists online : False
Views : 72