Bootloaders for all other platforms need to be rebuilt to function correctly on Windows Vista. This applies to all bootloaders (Eboot.*) except CEPC and Device Emulator bootloaders.

Once the bootloader is rebuilt, customers need to reflash their device with the updated bootloader, which is usually located in the flat release directory with the name Eboot.bin or Eboot.nb0.

The CEPC bootloader does not need to be rebuilt. However, it does need to be reflashed.

To boot a pre–Windows Embedded CE 6.0 Device Emulator image on Windows XP, do the following:

1. At a command prompt, change directories to <Windows Embedded CE 6.0 install directory>/corecon/bin/.
   
   
2. Run Regsvr32 download_DEmulator.dll.
   
   
3. Install the Virtual Machine Network Driver for Microsoft Device Emulator from this Microsoft Web site.
   
   

To boot a pre–Windows Embedded CE 6.0 Device Emulator image on Windows Vista, do the following:

1. Open a command prompt as an administrator.
   
   
2. Change directories to <Windows Embedded CE 6.0 install directory>/corecon/bin/.
   
   
3. Run Regsvr32 download_DEmulator.dll.
   
   
4. Download the driver (Netsvwrap.msi) from this Microsoft Web site, and save it locally.
   
   
5. Open a command prompt as an administrator.
   
   
6. Run msiexec/i netsvwrap.msi.
   
   

Platform Builder and related desktop tools are not supported on 64-bit versions of the desktop Windows operating system, including Windows XP 64-bit and Windows Vista 64-bit.

Use Add/Remote Programs to uninstall the Microsoft Smart Devices Remote Tools Framework before installing Windows Embedded CE 6.0 Platform Builder Service Pack 1. If you install Windows Embedded CE 6.0 Platform Builder Service Pack 1 without removing Microsoft Smart Devices Remote Tools Framework or if you install Microsoft Smart Devices Remote Tools Framework after installing Windows Embedded CE 6.0 Platform Builder Service Pack 1, Remote Tools Framework included with Windows Embedded CE 6.0 Platform Builder Service Pack 1 may not work. To fix problems, use Add or Remove Programs to uninstall the Microsoft Smart Devices Remote Tools Framework, and then use Add or Remove Programs to repair the installation of Windows Embedded CE 6.0 Platform Builder Service Pack 1.

In Platform Builder for CE 6.0, if you load a device image that resides in a read-only directory (such as a network), you cannot connect a remote tool to it. This is because the device-side binaries need to be copied to that path.

You can instead use a special mode of the KITL Bootstrap Server. The following procedure shows how to configure your remote tool connectivity when the device image is hosted on a read-only folder.

1. In Platform Builder for Windows Embedded CE 6.0, select Open on the File menu, and then select Project.
   
   
2. Open the *.bin directly from a read-only folder.
   
   
3. Attach the device, and wait for the device to launch completely.
   
   
4. In the remote tool, select Configure Windows CE Platform Manager on the Connection menu to bring up the Device Properties dialog box.
   
   
5. Select Windows CE Default Platform, and then Default Device.
   
   
6. Click Properties.
   
   
7. For the Startup server, ensure that you are using KITL Bootstrap Server.
   
   
8. Click Configure.
   
   
9. In the CESHX Configuration Settings dialog box, select Alternate Folder, and enter a local path (for example, c:\temp\KITLBootstrap).
   
   
10. Click OK.
    
    
11. In the Device Properties dialog box, click Test to make sure that you can get a proper connection.
    
    
12. If successful, click OK, and try to reconnect the remote tool.
    
    —OR—
    
    If unsuccessful, make sure the folder path you specified is a on a drive that has sufficient free space and that it is a folder to which you have write access.
    
    

If you select Launch in the Remote Call Profiler, and select Finish collection on exit, Remote Call Profiler does not stop collecting data when the specified application exits. You must manually watch for the application to exit, and click Stop to stop data collection.

If you start Remote Kernel Tracker and select Default device while Platform Builder is not connected to any device, and then close Remote Kernel Tracker, Kerneltracker.exe is still running in the background.

You can close the kernel tracker process by opening Task Manager, selecting the Kerneltracker.exe process, and clicking End Process.

You may see the following build-time error message while building a Remote Tools Framework plug-in:

"Projects targeting .NET Compact Framework 1.0 require version 1.1 of the .NET Framework, which is not detected on this machine."

If you have Visual Studio 2005 (the original release) and see this message, make sure that you have the .NET Framework 1.1 installed, including the proper .NET Compact Framework 1.0 support necessary to build Remote Tools Framework plug-ins. To download the desired version, go to this Microsoft Web site or this Microsoft Web site.

Searching with the Find and Replace dialog box fails, commonly with the message: "The operation could not be completed. No such interface supported." This is usually because the Look in box is set to Current Project, which is not supported for Windows Embedded CE runtime images (*.bin; *.nb0; *.dio; *.lst) projects.

Set the Look in box to All Open Documents, Current Document, or Current Window, as desired.

You must select the node in the Plug-in Explorer or the device/plug-in tree view in the Remote Tools shell before right-clicking to display the context menu for that node. If you try to show the context menu by right-clicking without first selecting the node, the context may not be what you expect.

A fix for this issue will be considered for a future release.

In Platform Builder, the Target menu sometimes persists for some time after clicking on other menus or other parts of the desktop. When this problem occurs, you may not be able to bring up other menus, such as the Debug menu, and it may take up to 15 minutes for the Target menu to disappear.

When you try to export executable (*.exe) files from the desktop to a device using Remote File Viewer (from Platform Builder 6.0) to a device, if the executable files are not built for the target CPU (for example, you are copying a DOS .exe to a ARMV4 device), the export operation fails without any error message. This is a known issue in Platform Manager. However, this issue is not fixed in Windows Embedded CE 6.0 Platform Builder Service Pack 1.

As a workaround, use the Visual Studio 2005 version of the Remote File Viewer, which can be launched from Start > All Programs > Microsoft Visual Studio 2005 > Visual Studio Remote Tools. This version of the Remote File Viewer uses Core Connectivity, which does not have this issue.

Remote Tools Framework plug-ins that use managed device-side code require the full .NET Compact Framework component to be installed on the device (SYSGEN_DOTNET on Windows CE 5.0, or SYSGEN_DOTNETV2 on Windows Embedded CE 6.0). The headless framework available Windows Embedded CE 6.0 (SYSGEN_DOTNETV2_HEADLESS) is not sufficient. Remote Tools Framework plug-ins that have managed device-side code cannot run on Windows Embedded CE 6.0 devices that include only the headless .NET Compact Framework component.

The x86 emulator does not work with earlier versions of Windows Embedded CE or Windows Mobile if you have them installed with Windows Embedded CE 6.0 Platform Builder Service Pack 1.

The workaround is to install Emulatortransport_500.dll to %ProgramFiles%\common files\microsoft shared\corecon\5.01\bin.

if you have Windows CE 5.0 , copy it from %ProgramFiles%\windows ce platform builder\5.00\corecon\bin

if you have Windows Mobile Version 5.0 , copy it from %ProgramFiles%\Platform builder for windows mobile\5.00\corecon\bin.

After disconnecting a Remote Tools Framework plug-in from a device, you may have a problem reconnecting the same plug-in if you try to reconnect too quickly. This is more likely to happen on physical devices and appears to be an internal issue with Core Connectivity. The workaround is to wait a few seconds after disconnecting a Remote Tools Framework plug-in before reconnecting it.

CETK cannot connect to networks under the following conditions:

• The computer is running Window Vista.
  
  
• The computer is joined to a domain that has an IP security policy that cannot be locally overridden.
  
  
• The domain has an IP security policy stating, "Accept no communication unless it is IP security protected."
  
  
• The domain has a rule stating, "Try IP security on outbound connection, and go clear if the peer cannot do IP security."
  
  

When a remote tool makes a connection to a device, it runs some code on the device. To successfully run the device-side code, the run-time image on the target device must include some features. If the operating system (OS) design that your runtime image is based on lacks any one of these features, the remote tool cannot connect to the device.

The following table shows the features that a runtime image must include to provide support for the remote tools that are included with Platform Builder.

You cannot step into an ASM function when debugging ARM applications that have ASM files compiled into them. The ARM assembler does not generate debugging information for source-level stepping.

When you install Windows Embedded CE 6.0 Platform Builder Service Pack 1 on a machine that already has Windows CE .NET 4.0, Windows CE .NET 4.1, or Windows CE .NET 4.2 installed, you may experience some issues in remote tools connectivity:

• Remote tools for Platform Builder for Windows Embedded CE 6.0 install an additional startup service (KITL Bootstrap Service), and this may be set up as the default startup server for Windows Embedded CE Platform Manager Connectivity Options. Make sure that you use a startup server other than KITL Bootstrap Server. To check your current Platform Manager connectivity options, use the following procedure:
  
  
  1. Start any remote tool from the Platform Builder Tools menu, or in Visual Studio 2005/Platform Builder for CE 6.0 select Remote Tools on the Target menu.
     
     
  2. Select Connection, and then Configure Windows CE Platform Manager.
     
     
  3. Select the default device, and click Properties.
     
     
• Due to conformance to binary distribution requirements, the Remote Performance Monitor and Remote Call Profiler remote tools accessible from Platform Builder 4.x and 5.0 are removed during the installation of Windows Embedded CE 6.0 Platform Builder Service Pack 1. Therefore, you cannot run these two remote tools. The workaround is as follows:
  
  
  1. Run the repair for your older Windows Embedded CE installation(s) (in chronological order, for example, 4.0, and then 5.0).
     
     
  2. Back up the contents of the C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin and C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\wce420 folders on your computer.
     
     
  3. Install (or repair) Windows Embedded CE 6.0.
     
     
  4. Copy back CePerfMon.exe and Msic.exe into the respective folders under C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin and C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\wce420.
     
     

When you run the System Information remote tool and open a .csi file while some previously captured system information is displayed, the UI does not reflect the contents of the .csi file that you just opened. This is a known issue and will be addressed in a future release.

The workaround is to close the System Information remote tool and rerun it. (You do not necessarily need to connect to a device at this point.) Then open the .csi file from the File menu.

The Zoom-in remote tool may report an error due to out-of-memory conditions when run on a large device image. When you use the Zoom-in remote tool on a large device image, it may display the error message "Connection to the device was lost."

If you are running Zoom-in from Platform Builder, you may also see a message such as the following in the debug output window:

"Unable to create dib section...errorcode = 8"

This error comes while attempting to allocate a memory buffer to hold the bitmap DIB bit values. However, this may not be the only out-of-memory condition that you encounter. This type of error indicates that the device-side code for Zoom-in (Cezcli.exe) ran out of memory.

The workarounds are as follows:

• Terminate other applications running on the device to free memory.
  
  
• If you can modify the OS design, free memory so that your device has enough memory to allocate the necessary buffers for the bitmap data.
  
  

When you run the remote tool Kernel Tracker for a prolonged period of time, the amount of memory that it uses on the desktop computer may rise to a very large amount. Instead of running Kernel Tracker for a prolonged period of time, you may want to run it in Limited Buffer Mode, or terminate and restart Kernel Tracker to show events only as needed.

When using the Registry Editor remote tool while programmatically modifying registry keys from another application running on your device, refreshing the view (F5) on Registry Editor may not show the modifications made by the other application if the currently selected node is not a top-level node (for example, HKEY_LOCAL_MACHINE). Instead, before you refresh the view, select one of the top-level nodes. The view should refresh with the latest state of the registry.

The following Platform Manager sample SDK projects do not build successfully as installed. However, with a few simple steps, you can fix them in Visual Studio 2005.

• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\Hello\Hello.vcw
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\KTSubSample\KTSubSample.dsp
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Publisher\hellopublisher.vcp
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Subscriber\hellosubscriber.dsp
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Test\PubSubTest.vcproj
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\timeviewer\desktop\timeviewer.dsp
  
  
• C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\timeviewer\device\timeviewerce.vcp
  
  

Follow these steps to build the samples in Visual Studio 2005:

Hello.vcw

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\Hello\Hello.vcw in Visual Studio 2005 , and let Visual Studio 2005 convert the project.
   
   
2. Save Hello.sln to the same path as the VCW file.
   
   You will see two new files: CallCap\CallCap.vcproj and FastCap\FastCap.vcproj.
   
   
3. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\Hello\Fastcap\Fastcap.cpp, and move the int i declaration out of the first for loop in DoMultiThread to the previous line.
   
   
4. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\Hello\Callcap\Callcap.cpp, and move the int i declaration out of the first for loop in DoMultiThread to the previous line.
   
   

• Build Hello.sln.
  
  Both debug and release configurations should build without errors.
  
  

KTSubSample.dsp

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\KTSubSample\KTSubSample.dsp, and let Visual Studio 2005 convert the project.
   
   
2. Save KTSubSample.sln to the same path as the DSP file.
   
   
3. Open a command prompt, and change directories to C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\include.
   
   
4. Assuming that Visual Studio 2005 folders are in your %PATH% environmental variable, run MIDL CEPUBSUB.IDL, and then MIDL KTSUB.IDL.
   
   
5. Open KTSubSample.cpp, and comment out the following line:
   
   

   Enable3dControlsStatic();// Call this when linking to MFC statically

6. Build KTSubSample.sln.
   
   Both debug and release configurations should build without errors.
   
   

Hellopublisher.vcp

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Publisher\Hellopublisher.vcp, and let Visual Studio 2005 convert the project.
   
   
2. Save Hellopublisher.sln to the same path as the VCP file.
   
   
3. On the Project menu, click Properties.
   
   
4. Click Configuration Properties, Linker, and then General Property.
   
   
5. Change the following items:
   
   
   • Output file: from ..\..\bin\Target\armv4\HelloPublisher.dll, to ..\..\bin\Target\armv4i\HelloPublisher.dll.
     
     
   • Additional library directories: from ..\..\..\target\armv4, to ..\..\..\target\armv4i.
     
     
   Remember to do this step for both debug and release configurations. You may also have to repeat this step for other solution platforms (or device SDKs) that you have installed in your Visual Studio 2005 configuration. In that case, the processor-specific part of the library paths may differ.
   
   This library was compiled with updated Visual Studio for Devices compilers/linkers. You need an upcoming Visual Studio 2005 service pack to obtain these compilers/linkers. Go to the Microsoft Download Center for the latest service packs for Visual Studio 2005. If you are using Visual Studio 2005 (original release), you will get the following linker error: "Error LNK2001: unresolved external symbol __GSHandlerCheck." Once you make these changes, the link is created without an error. However, you may see the following warning messages during the debug configuration build:
   
   
   • RComHelperCE.lib(MajRegistryhelper.obj) : "Warning LNK4204: C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Publisher\Pocket PC 2003 (ARMV4)\Debug\vc80.pdb is missing debugging information for referencing module; linking object as if no debug info."
     
     
   • LIBCMTD.lib(gshandler.obj) : "Warning LNK4099: PDB Libbmtd.pdb was not found with C:\Program Files\Microsoft Visual Studio 8\VC\ce\lib\ARMV4\LIBCMTD.lib or at c:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Publisher\Pocket PC 2003 (ARMV4)\Debug\libbmtd.pdb; linking object as if no debug info."
     
     
   Both of these can be ignored because the libraries that are being linked are release build libraries. You cannot debug with them.
   
   
6. Build Hellopublisher.sln.
   
   Both debug and release configurations should build (with a service pack of Visual Studio 2005) without errors.
   
   

Hellosubscriber.dsp

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Subscriber\Hellosubscriber.dsp, and let Visual Studio 2005 convert the project.
   
   
2. Save Hellosubscriber.sln to the same path as the DSP file.
   
   
3. Open HellpSub.cpp.
   
   
4. In CHelloSub::Open, change the following line:
   
   

   m_file = ::CreateFile(OLE2T(const_cast<unsigned short *>(filename)),GENERIC_WRITE,0,NULL,CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);

   To:
   
   

   #ifdef UNICODE m_file = ::CreateFile(T2CW_EX_DEF(OLE2CT(filename)),GENERIC_WRITE,0,NULL,CREATE_ALWAYS,FILE_ATTRIBUTE_NORMAL, NULL); #else m_file = ::CreateFile(OLE2T(filename),GENERIC_WRITE,0,NULL,CREATE_ALWAYS,FILE_ATTRIBUTE_NORMAL, NULL); #endif

5. Open Stdafx.cpp, and comment out #include <statreg.cpp> and #include <atlimpl.cpp>.
   
   
6. If you are building one of the release configurations (for example, Release MinDependency, Release MinSize, Unicode Release MinDependency, Unicode Release MinSize), you must set up a linker option to ignore Atlmincrt.lib. Do the following:
   
   
   1. In Solution Explorer, select the HelloSubscriber (project) node, and right-click.
      
      
   2. Select Properties.
      
      
   3. Make sure the Configuration is set to one of the release configurations.
      
      
   4. Select Configuration Properties, Linker, and then Input.
      
      
   5. Set Ignore Specific Library to Atlmincrt.lib.
      
      
   You do not need to do this for any of the debug configurations.
   
   
7. Open a command prompt, and change directories to C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\include.
   
   
8. Assuming that Visual Studio 2005 folders are in your %PATH% environmental variable, run MIDL CEPUBSUB.IDL.
   
   
9. Build Hellosubscriber.sln.
   
   Both debug and release configurations should build without errors.
   
   

PubSubTest.vcproj

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\PubSub\Test\PubSubTest.vcproj, and let Visual Studio 2005 convert the project.
   
   
2. Save the PubSubTest.sln to the same path as the .vcproj file.
   
   
3. Select Properties on the Project menu.
   
   
4. Select Configuration Properties, C/C++, and then General.
   
   
5. Change Additional Include Directories from \..\..\platman\include to \..\..\include.
   
   
6. Select Configuration Properties, Linker, and then Input.
   
   
7. Change Additional Dependencies from Rts.lib to \..\..\lib\dsktop\rts.lib.
   
   Remember to do this step for both Debug and Release configurations.
   
   
8. If you have not done so already, open a command prompt, and change directories to C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\include.
   
   
9. Run MIDL CEMGR.IDL, and then MIDL CEMGRUI.IDL.
   
   
10. Build PubSubTest.sln.
    
    Both debug and release configurations should build without errors.
    
    

Timeviewer.dsp

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\timeviewer\desktop\Timeviewer.dsp, and let Visual Studio 2005 convert the project.
   
   
2. Save Timeviewer.sln to the same path as the DSP file.
   
   
3. Open TimeViewer.cpp.
   
   
4. Modify some of the string functions called from ConnectToDevice to use the safer versions (with an _s in the function name), as follows:
   
   
   • Change:
     
     

     stRet = wcstombs(szDeviceName, pszName, sizeof szDeviceName);

     To:
     
     

     size_t _PtNumOfCharConverted; stRet = wcstombs_s(&_PtNumOfCharConverted, szDeviceName, pszName, sizeof szDeviceName);

   • Change:
     
     

     strcpy(szTitle, "TimeViewer : ");

   • To:
     
     

     strcpy_s(szTitle, "TimeViewer : ");

   • Change:
     
     

     strcat(szTitle, szDeviceName);

     To:
     
     

     strcat_s(szTitle, szDeviceName);

   • Change:
     
     

     wcscpy(wszDeviceExe, L"\\Windows\\TimeViewerCE.exe");

     To:
     
     

     wcscpy_s(wszDeviceExe, L"\\Windows\\TimeViewerCE.exe");

5. Build Timeviewer.sln.
   
   Both debug and release configurations should build without errors.
   
   

Timeviewerce.vcp

1. Open C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce600\samples\timeviewer\device\Timeviewerce.vcp, and let Visual Studio 2005 convert the project.
   
   
2. Save Timeviewerce.sln to the same path as the VCP file.
   
   
3. Build Timeviewerce.sln.
   
   Both debug and release configurations should build without errors.
   
   

In the Spy remote tool, the ability to spy on window messages has been disabled in Windows Embedded CE 6.0 Platform Builder Service Pack 1 due to OS security policies. If you start Spy, and then try to capture messages on any child window of the desktop window (handle != 0x00000000), the messages window does open in the client. The following message is displayed in the Visual Studio 2005/Platform Builder Debug Output Window:

119985 PID:5b2002e TID:5b4002e ######### CeSpy - Message intercept and display not supported in this OS #########

If a log file that you are viewing with Kernel Tracker contains an event without a timestamp (for example, WaitForMultipleObjects), subsequent events appear shifted by 10 ms. This is an arbitrary delay that is added so that the event does not appear at the same time as the previous timestamped event.

• Remote Tools Framework does not connect if you are using a kernel-level transport while the flat release directory is read-protected.
  
  
• Only one remote tool can be connected to a device at a time.
  
  

If an eXDI1 version driver is selected and then loads by clicking Target Connectivity, and then clicking Debugger, exceptions could occur in Platform Builder if you try to attach the debugger.

When you delete a device from the Devices panel in Bundle Input Editor, the screen fails to refresh the displayed information in the Selected device configuration section. The information for the deleted device information is still displayed. This only occurs in the user interface (UI), and the data saved in the .cebundleinfo file is correct. This UI behavior will be fixed in a future release.

Use the following procedure to create a debugger extension:

1. Void WDBGAPI WinDbgExtensionDllInit (PWINDBG_EXTENSION_APIS lpExtensionApis, USHORT MajorVersion, USHORT MinorVersion).
   
   lpExtensionApis specifies a pointer to a structure that contains exported functions from Platform Builder.
   
   MajorVersion is not used. The intent of this structure is to communicate the version of the operating system.
   
   MinorVersion is not used. The intent of this structure is to communicate the version of the operating system.
   
   
2. Export an ExtensionApiVersion function, as follows:
   
   

   LPEXT_API_VERSION WDBGAPI ExtensionApiVersion(void)

   When the debugger calls the ExtensionApiVersion function, the function returns a pointer to EXT_API_VERSION. The version number of the debugger extension DLL must match with the version of the debugger.
   
   DECLARE_API( XXX ) expands to void WDBGAPI XXX(HANDLE hCurrentProcess, HANDLE hCurrentThread, ULONG dwCurrentPC, ULONG dwProcessor, PCSTR args).
   
   hCurrentProcess specifies a handle of the current process.
   
   hCurrentThread specifies a handle of the current thread.
   
   dwCurrentPC specifies current instruction that the device is halted.
   
   dwProcessor is not used.
   
   args specifies the arguments of the command that the user inputs into the Target Control window to invoke the extension function.
   
   

The following debugger extension functions are not yet implemented:

• CheckControlC
  
  
• GetDebuggerData
  
  
• ReadControlSpace
  
  
• ReadPhysical
  
  
• SetThreadForOperation
  
  
• WritetoSpace
  
  
• WritePhysical
  
  

The input/output control (Ioctl) function has the following usage:

ULONG Ioctl(
   USHORT IoctlType,
   PVOID lpvData,
   ULONG cbSizeOfData)

The following are some of the Ioctl functions available:

• IG_GET_BOOTABLEDEVICE
  
  Obtains the CoreCon device ID for the currently booted device. As a parameter, takes a pointer to a buffer that can store a GUID. Ioctl writes a GUID into this buffer.
  
  
• IG_GET_EXDI2_CCSERVICE
  
  Obtains the ICcService interface of the current eXDI2 debugger driver. As a parameter, takes a pointer to a buffer that can store a pointer. Ioctl copies out a COM pointer with refcount set to 1 into this buffer.
  
  
• IG_GET_EXDI2_GENERIC
  
  Obtains the IeXdi2Generic interface of the current eXDI2 debugger driver.
  
  
• IG_GET_OSACCESS_CCSERVICE
  
  Obtains the ICcService interface of the operating system awareness service.
  
  
• IG_GET_OSACCESS_GENERIC
  
  Obtains the IOsAxsGeneric interface of the operating system awareness service.
  
  

The following known issue applies to the documentation for Windows Embedded CE 6.0 Platform Builder Service Pack 1:

• In the SimplePluginManagedAsync Sample topic, the Required Operating System Dependencies section should specify .NET Compact Framework 1.0.
  
  

The following changes have been made to the CETK:

• Updated the CETK to work on Windows Vista.
  
  
• Updated Perf_winsock Test to have better timeout and logging capabilities.
  
  
• Updated NDIS Wireless LAN test to enable/disable wzcsvc before and after the test runs.
  
  
• Updated Bluetooth test.
  
  
• Updated Apcontrol.exe to work with Internet Explorer 7.
  
  
• Updated the Real-time clock tests to allow more delay when fetching the time from RTC.
  
  
• Updated USB Stress test to handle null command-line parameters gracefully.
  
  
• Updated kernel tests.
  
  
• Updated OAL test to remove internally available NTP server list from the Compare RTC to NTP drift test.
  
  
• Added Apcontrol.exe as desktop binary for Authentication Matrix.
  
  
• Updated file system tests.
  
  
• Added new OAL test for Iltiming IOCTL.
  
  
• Added new OAL tests for Instruction Cache.
  
  

A sample .clg file is now installed at C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\sdk\wce###\samples\KTLogFiles\sample.clg. For Windows Embedded CE 6.0 Platform Builder Service Pack 1, the wce### is "wce600". You can open this log file in Kernel Tracker and see interesting thread behaviors.

The following interfaces, along with all their methods, are now deprecated:

• ICcConnection
  
  
• ICcConnection::CloseProcessHandle
  
  
• ICcConnection::ConnectDevice
  
  
• ICcConnection::CreateStream
  
  
• ICcConnection::DeleteDirectory
  
  
• ICcConnection::DeviceId
  
  
• ICcConnection::DisconnectDevice
  
  
• ICcConnection::DownloadPackage
  
  
• ICcConnection::EnumerateProcess
  
  
• ICcConnection::GetFileInfo
  
  
• ICcConnection::GetProcessExitCode
  
  
• ICcConnection::GetSystemInfo
  
  
• ICcConnection::IsConnected
  
  
• ICcConnection::LaunchProcess
  
  
• ICcConnection::MakeDirectory
  
  
• ICcConnection::ReceiveFile
  
  
• ICcConnection::RegistryCreateKey
  
  
• ICcConnection::RegistyDeleteKey
  
  
• ICcConnection::RegistyDeleteValue
  
  
• ICcConnection::RegistyQueryValue
  
  
• ICcConnection::RegistySetValue
  
  
• ICcConnection::RemoveFile
  
  
• ICcConnection::SearchFileSystem
  
  
• ICcConnection::SendFile
  
  
• ICcConnection::SetFileInfo
  
  
• ICcConnection::TerminateProcess
  
  
• ICcConnection::VerifyFilesInstalled
  
  
• ICcServer::EnumerateConnections
  
  
• ICcServer::GetConnection
  
  
• ICcServer::GetConnectionFromId
  
  
• ICcServer::GetDatastore
  
  
• ICcServer::Locale
  
  
• IConman
  
  
• IConman::SetLocale
  
  
• IConman::SetRegistryRoot
  
  
• IConman::CreateNewServerGuid
  
  
• IConman::EnumerateServerGuids
  
  
• IConman::get_Datastore
  
  
• IConman::GetDeviceFromServerGuid
  
  
• IConman::GetServerFromServerGuid
  
  
• IConman::GetServerGuidInfo
  
  

In addition, the following APIs are now deprecated:

• ICcCollection
  
  
• ICcCollection::get_Count
  
  
• ICcCollection::get_Item
  
  
• ICcCollection::get_NewEnum
  
  
• ICcDatastore
  
  
• ICcDatastore::get_DeviceContainer
  
  
• ICcDatastore::get_OSImageContainer
  
  
• ICcDatastore::get_PackageContainer
  
  
• ICcDatastore::get_PlatformContainer
  
  
• ICcDatastore::get_PropertyContainer
  
  
• ICcDatastore::get_ServiceCategoryContainer
  
  
• ICcDatastore::get_Version
  
  
• ICcDatastore::RegisterRefreshEvent
  
  
• ICcDatastore::Save
  
  
• ICcDatastore::UnregisterRefreshEvent
  
  
• ICcDevice
  
  
• ICcDevice::ClearOSImage
  
  
• ICcDevice::ClearServiceMap
  
  
• ICcDevice::GetOSImage
  
  
• ICcDevice::GetServiceMap
  
  
• ICcDevice::SetOSImage
  
  
• ICcDevice::SetServiceMap
  
  
• ICcDeviceContainer
  
  
• ICcFile
  
  
• ICcFile::get_FileContainer
  
  
• ICcFile::get_IsCollection
  
  
• ICcFile::MakeCollection
  
  
• ICcFileContainer
  
  
• ICcFormFactor
  
  
• ICcFormFactorContainer
  
  
• ICcObject
  
  
• ICcObject::get_IsProtected
  
  
• ICcObject::get_PropertyContainer
  
  
• ICcObject::ID
  
  
• ICcObject::Name
  
  
• ICcObjectContainer
  
  
• ICcObjectContainer::AddObject
  
  
• ICcObjectContainer::DeleteObject
  
  
• ICcObjectContainer::EnumerateObjects
  
  
• ICcObjectContainer::FindObject
  
  
• ICcOSImage
  
  
• ICcOSImage::SupportedPlatform
  
  
• ICcOSImageContainer
  
  
• ICcPackageType
  
  
• ICcPackageType::FileContainer
  
  
• ICcPackageTypeContainer
  
  
• ICcPlatform
  
  
• ICcPlatform::DeviceContainer
  
  
• ICcPlatform::FormFactorContainer
  
  
• ICcPlatform::ProjectContainer
  
  
• ICcPlatformContainer
  
  
• ICcProject
  
  
• ICcProjectContainer
  
  
• ICcProperty
  
  
• ICcProperty::AddPropertyContainer
  
  
• ICcProperty::Value
  
  
• ICcPropertyContainer
  
  
• ICcServiceCategory
  
  
• ICcServiceCategory::ServiceInfoContainer
  
  
• ICcServiceCategoryContainer
  
  
• ICcServiceInfo
  
  
• ICcServiceInfoContainer
  
  
• ICcTypeToArchitectureMap
  
  

The following structures are now deprecated:

• FileInfo
  
  
• FileVerifyInfo
  
  
• FileVerifyReference
  
  
• FileVerifyResult
  
  
• FileVerifyVersion
  
  
• SystemInfo
  
  

The following enumeration is now deprecated:

• FileCustomAction
  
  

Returns TRUE if the extension handles the command.

If the user enters a question mark (?) in the Target Control window, each extension is passed the command. The extension can display the usage for supported commands using the pfnFmtPuts parameter.