Contents

Release Notes for Windows Embedded Compact 2013 ........................................................................... 2

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Release Notes for Windows Embedded Compact 2013

This document describes known issues in Windows Embedded Compact 2013.

Installation Requirements
Install the Customer Technology Preview of Windows Embedded Compact 2013 on a non-production computer without a previous installation of Windows Embedded Compact. This computer must meet the following requirements:

Operating System
Your computer must have one of the following operating systems installed. Windows 7 (x86-based and x64-based) and any available service packs Windows 8 (x86-based and x64-based) and any available service packs Windows Server 2008 R2 (x64-based) and any available service packs. Windows Server 2012 (x64-based) and any available service packs.

Software
Your computer must have the following software installed, and installed in the following order: 1. Microsoft Visual Studio 2012 Update 2. You can download Microsoft Visual Studio 2012 Update 2 from the Microsoft Download Center (http://go.microsoft.com/fwlink/p/?LinkId=301756). 2. Microsoft .NET Framework 3.5, Service Pack 1. You can download the installation file from the Microsoft Download Center (http://go.microsoft.com/fwlink/p/?LinkId=252977). 3. Application Builder for Windows Embedded Compact 2013. You can download the installation file from the Microsoft Download Center (http://go.microsoft.com/fwlink/p/?LinkId=301580).

Hardware
Your computer must meet the following hardware requirements: 100 GB (NTFS) of available hard disk space 2.4 GHz processor 2 GB of RAM 5400 RPM hard drive A Microsoft DirectX 9-capable video card running at 1024 x 768 or higher display resolution An optical drive that supports DVD-ROM

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Known Issues and Troubleshooting

Known issues and troubleshooting hints for this release are noted in the following sections.

Platform Builder
Issue Workaround

On a computer running Windows Server Manually add the following inbound/outbound rules to 2012, Platform Builder is unable to see Windows Firewall: bootme files from Windows CE devices on 1. Inbound: Program - %ProgramFiles% the same subnet. Thus, you cannot discover (x86)\Microsoft Platform a device by using Platform Builder and are Builder\8.00\CoreCon\BIN\cesvchost.exe - allow blocked from downloading to the device. connection - domain/private/public 2. Outbound: Program - %ProgramFiles% (x86)\Microsoft Platform Builder\8.00\CoreCon\BIN\cesvchost.exe - allow connection - domain/private/public Project solution files for OS designs created in Visual Studio 2008 cannot be opened in Visual Studio 2012. Platform-specific Macro in the SDK properties is no longer supported. Delete the solution files (.sln, .suo, .ncb) and open the OS Design (.pbcXml) file directly.

The Development languages list is now based on the Sysgen variables that you have included in your OS design. For example, if you want to enable managed application development, you need the NetCF Sysgen in your OS project. Restart Visual Studio. If that doesn't work, go to c:\users\[username]\AppData\Local\Microsoft\Embedded Tools\Corecon and rename or delete the 11.0 folder.

When using the Connectivity Options dialog box, sometimes this error message will appear: "Platform Builder was unable to read the device settings from the Data Store." If you are using a USB connection to a device and want to reset the target device, dont use .reset command from the Target Control window or from the Reset Device option on the Target menu

To reset the device, use the Detach Device and Target - Attach Device option on the Target menu.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Remote Tools
Issue Workaround

Remote Tools do not work if Platform Builder is not installed on the C:\ drive. All Remote tools fail with unhandled exception at 0x67814EB5 (ComMan2.dll) when attempting to connect to an invalid connection. Incorrect "Full Path" shown for modules in the Remote Process Viewer. For example, the full path for plcrt.dll points to \windows\msvcrt.dll instead of \windows\lpcrt.dll. TCP/IP connection to Remote Tools fails if a remote tool is called by using KITL, and KITL connection to Remote Tools fails if Remote Tool is called by using TCP/IP. If the Remote Profiler and Remote Registry Editor are both open, you cannot use the Save or Save File from Registry Editor As menu options. Remote Tools will not open while Remote Profiler is capturing the profile data.

Install Platform Builder on the C:\ drive.

Do not connect to an invalid connection.

None.

Use only one transport type per session, either TCP/IP or KITL.

Workaround: To save items, close the Remote Profiler if you are using the Remote Registry Editor.

Close and reopen the Remote Tools Shell. If that doesnt work, perform an end task on RemoteToolsShell.exe, reset the device, and then close and re-open Visual Studio. Close and reopen the Remote Tools Shell. If that doesnt work, perform an end task on RemoteToolsShell.exe, reset the device, and then close and re-open Visual Studio. Set SYSGEN_REMOTETOOLS if you want to use Remote Tools with the image.

Remote Tools Shell may not respond after opening and closing several Remote Tools.

Remote Tools will fail with an exception if SYSGEN_REMOTETOOLS is not set on the image. If you have Compact 7 and Compact 2013 devices both created and deployed via Platform Builder (versions 7 and 8, respectively), you cannot use the Compact 2013 version of the Remote Tools to open a Compact 7 image, even though the Compact 7 image is listed in

Only images built with Compact 2013 can use the Compact 2013 version of the remote tools. Do not select an image built with Compact 7.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Issue Workaround

the UI. If you have Compact 7 and Compact 2013 devices both created and deployed via pb (versions 7 and 8, respectively), you cannot use the Compact 2013 version of the Remote Tools to open a Compact 7 image, even though the Compact 7 image is listed in the UI. Closing the Resource Consumer displays a "Connection to the device <device name> failed" error message. Remote Tools cannot connect to a localized image. If you have Platform Builder installed, opening Remote Tools from the Visual Studio Tools menu will fail if you are not in an OS Design project. Timeline viewer does not import .csv file data correctly. Only images built with Compact 2013 can use the Compact 2013 version of the remote tools. Do not select an image built with Compact 7.

After closing Resource Consumer, restart Visual Studio and reset the device.

None.

Open Remote Tools from the Windows Start menu instead of from Visual Studio.

None.

Assembler Compiler
Issue Workaround

Error A2092: improper program syntax; missing ENDP directive or nested function definition is raised if you have a macro mismatch in your assembly file.

If this message displays, you have a mismatched macro LEAF_ENTRY/LEAF_END or NESTED_ENTRY/NESTED_END that you need to address in your assembly file.

Software Development Kit (SDK)

Issue Workaround

Installing an SDK that shares a name with an

Do not reuse an SDK name; otherwise, uninstall the existing SDK that has the same

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Issue Workaround

existing SDK will overwrite the existing SDK. Unbuildable SDK created when Solution Explorer is collapsed or closed.

name before installing the new one. Open Solution Explorer, make it the active window, and then point to "Add New SDK entry."

Board Support Packages (BSPs) and Drivers

Issue Workaround

A cloned BSP does not display in the BSP selection page of the OS Design Template when creating a new OS Design. An "Access Violation" exception is raised for an AMD G Series board if neither VGA or DVI is connected. TI 4470: The GPIO line used for debugging is not compatible with the Tablet2 hardware platform which can cause disruptions with the USB PHY. The disruption will result in USB connection errors and failure to recognize the USB device. TI 4470: Text corruption may occur when using ClearType with Screen rotation. This is a bug in the Display Driver. TI 4470: The Texas Instruments AAC Audio

Close and reopen Visual Studio 2012.

Force the AMD display driver to load by setting the "NOEDID" registry key to 1 (it is set to zero by default) in the following reg key file:
\platform\GSeries\src\AMDDrivers\GSeriesHD6xxx\wec\ongfx.reg

Contact Texas Instruments for an update.

Contact Texas Instruments for an update.

Contact Texas Instruments for an update.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Issue Workaround

Decoder Filter set through the BSP_TI_MULTIMEDIA setting, does not function correctly when using the Graph Builder. TI 4470: OpenGL cannot be used because the PowerVR component in the 4470 BSP does not build correctly. Contact Texas Instruments for an update.

New board support packages Windows Embedded Compact 2013 combines the functionality of CEPC BSP and Virtual CEPC BSP into one CEPC BSP. The new CEPC BSP also supports Hyper-V. For a list of participating BSP and driver providers, see the Windows Embedded Connect Site (http://go.microsoft.com/fwlink/p/?LinkID=279030&clcid=0x409). ICOP eBox 3300 Freescale i.MX27 Freescale i.MX31 NEC NE1TB Capricorn Samsung SMDK6410 Sigma Designs 8654 (mips) TI 3530

Board Support Packages that are no longer included

Hyper-V
Issue Workaround

The bootloader, when run under Hyper-V emulation, may hang during boot.

Reset the device.

Types.h renamed Cetypes.h

If you include the Types.h file under %_WINCEROOT%\public\common\sdk\inc, you need to change the statement to include Cetypes.h.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Application Development: Managed code and designer

Issue Workaround

Controls that are on the Visual Studio design surface overlap when a menu control is docked to Top and Left. When you double-click an OpenFileDialog or SaveFileDialog object on the design surface to add an event handler for the FileOk default event in the code-behind file, the event handler is not added.

Manually move the controls after adding them to the design surface.

Manually add the event-handling method and associate it with the FileOk event.

Adding controls to a collection property by using Add the controls to the collection in code. the collection editor for a Control Library project does not add the controls correctly, and the file does not compile. Automatic scaling is turned off by default in the project templates. Set the Autoscaling property manually if automatic scaling is required; for example:
In Visual Basic: Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Dpi

In C#: this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Dpi;

Using the Table Collection Editor to add a DataTable object to a DataSet control does not add the DataTable correctly, and the code does not compile. When you reference a Control Library project from a Device Application project and build the solution, the user control does not appear in the Toolbox. In addition, when you manually add the user control to the Toolbox, it is not displayed.

Add the DataTable object in code.

Add the control to the Device Application project manually in code.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013

Application Development: Native code (C++)

Issue Workaround

Using the CreateProcess function fails at compile time because it is not a Unicode API. Resource template (.rct) files that are created and added to the resource template directory (<installDir\Program Files\Microsoft Visual Studio 11.0\VC\VCResourceTemplates\1033) are not displayed in Visual Studio when you choose the Add Resource command. The subproject template for Compact 2013 applications does not automatically add .rc files to the build.

Manually add a #define Unicode statement to the code file. None.

Open the sources file by double-clicking on the subproject in your OS design, then add the name of the .rc file with extension to the SOURCES macro, for example SOURCES=subproject1.cpp subproject1.rc. Use the standard fonts provided with Compact 2013.

XAML for Windows Embedded does not support AC3 font compression. You must clear the Sysgen variable SYSGEN_AC3_FONT when using XAML for Windows Embedded. In addition, XAML for Windows Embedded does not work with pluggable font engines like Monotypes iType.

Application Development: Debugging and Deployment

Issue Workaround

The Debug and Release configurations require None. an IP address setting. If you switch between the Debug and Release configurations, you will be prompted for an IP address. When you're debugging a try/catch statement None. in C++, if you set a breakpoint on code that throws an exception and press F10 (Step Over) when the breakpoint is hit, the code continues execution as if you pressed F5 (Start

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013 10

Issue Workaround

Debugging) instead. When you're debugging a native application and you've selected to break only on Microsoft Win32 exceptions (by using Debug > Exceptions > Win32 Exceptions), control goes to external code for first-chance exceptions. On the menu bar, choose Debug > Exceptions, and then select the check boxes in the Thrown column for the following exceptions: Attaching to two processes from a single Visual Studio instance is not supported. The Start Debugging command (F5) will fail for C++ projects if the Remote Directory path in the project's Configuration Properties, on the Deployment tab, is changed to something other than the default path. Some operating system files will be deployed to the default location instead of the specified remote directory. Deploying an application to a device after using a remote tool fails. C++ Exceptions Common Language Runtime Exceptions Win32 Exceptions

Use two different Visual Studio instances to attach to two different application processes. Manually update the Additional Files path to the same location as the Remote Directory path to copy all operating system files to the correct location.

When selecting the Windows Embedded Compact Device, use the Windows CE Application Builder connection, which uses TCP/IP, instead of the Windows Embedded Compact Default Platform. 1. Copy the entire contents of Corecon <drive>\%prog files%\common files\microsoft shared\embedded tools\corecon\11.0\target\wce800\<cpu> to your release directory. 2. Launch all remote tools from the Start menu. Launching from Platform Builder defaults the connection to use KITL, while launching from the Start menu lets you choose to use the Windows CE Application Builder (also known as TCPIP) connection.

Calling Remote Tools from Platform Builder causes application deployment activities to stop.

Resource strings in an application sub-project cannot be retrieved.

The subproject template for Compact 2013 Application does not automatically add .rc files to the build. To work around this, open the

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013 11

Issue Workaround

sources file by double clicking on the subproject in your OS Design, then add the name of the rc file with extension to the SOURCES macro, e.g. SOURCES=subproject1.cpp subproject1.rc.

Debugger
Issue Workaround

When viewing the disassembly of code, the LDRSH instruction is not recognized by the disassembler and shows the instruction as undefined. Furthermore, stepping into or stepping over code with this instruction, where the target register of the load is the program counter, will not work.

For stepping, you can use additional breakpoints instead of step into or step over.

For an application to be debugged, the image Add SYSGEN_APPDEBUG to your OS design if you needs to include SYSGEN_APPDEBUG. want to debug applications. 0x406d1388 exception is raised when trying to debug Native ATL applications on CEPC. Catch the exception, as in the following example:
void Win32BDM::CBaseDebugMonitor::NameDebugThread() { typedef struct tagTHREADNAME_INFO { DWORD dwType; // must be 0x1000 LPCSTR szName; // pointer to name (in user addr space) DWORD dwThreadID; // thread ID (1=caller thread) DWORD dwFlags; // reserved for future use, must be zero } THREADNAME_INFO;

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013 12

Issue Workaround THREADNAME_INFO info; info.dwType = 0x1000; info.szName = "Debugger Event Loop Thread"; info.dwThreadID = GetCurrentThreadId(); info.dwFlags = 0;

__try { RaiseException( 0x406D1388, 0, sizeof(info)/sizeof(ULONG_PTR), (ULONG_PTR*)&info ); } __except(EXCEPTION_CONTINUE_EXECUTION) { } }

Code Map does not work for Compact 2013 projects.

None.

CTK
Issue Workaround

The TI 4470 cpuload policy will disable cpu1 when the system load is low. This will cause the CTK test tux -o d ksmpbvt.dll to fail.

Disable the cpuload policy before running this test. The easiest way to disable the cpuload policy is to exclude SYSGEN_PM (or anything that pulls in SYSGEN_PM) from your image. Restart the test pass if the device reboots.

The CTK disconnects form a devices and exits the test pass if the device reboots.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013 13

Issue Workaround

The CTK in Compact 7 cannot be launched if the CTK in Compact 2013 is running. NDIS6 performance test requires driver installation to run, but the shipped driver is compiled with 32-bit OS and does not work on 64-bit OS machines.

Stop the CTK in Compact 2013 to launch the Compact 7 version of the tool. 1. Run the test on a 32-bit OS. 2. Install a 32-bit virtual machine on a 64-bit machine and install the driver on the 32bit virtual machine to run the test. Perform the following steps in order to run the CTK Wi-Fi authentication tests successfully:

CTK Wi-Fi authentication tests fail with the following errors: Error: Could not find support file: C:\Program Files (x86)\WindowsEmbeddedCompact2013TestKit\tests\8. 0.0\files\eaptls.cfg

1. Copy eaptls.cfg (from C:\WINCE800\public\test\oak\target\x86\ retail) to C:\Program Files (x86)\WindowsEmbeddedCompact2013T Error: Could not find support file: C:\Program Files estKit\tests\8.0.0\files (x86)\WindowsEmbeddedCompact2013TestKit\tests\tar get\x86\apcontrol.exe 2. Copy apcontrol.exe (from C:\WINCE800\public\test\oak\target\NT\r etail) to C:\Program Files (x86)\WindowsEmbeddedCompact2013T estKit\tests\target\x86

International
Issue Workaround

The keyboard layout for Virtual PC hardware only supports US/0409 layout.

If you want to use another keyboard layout in Virtual PC, you must use a SIP. You can enter the keystroke by using the soft keyboard panel edit control (or if the program enables the soft keyboard panel explicitly through SipPreference() or SHSipPreference(), or by setting the "SIP_UP" SYSGEN variable). For more information, see Software-based Input Panel.

Attempting to connect to a device with a localized OS displays a "Parameter Incorrect" error message.

Select both a language and a sub-region when creating a localized OS Design.

2013 Microsoft. All rights reserved.

Release Notes for Windows Embedded Compact 2013 14

Issue Workaround

Locale settings do not apply if you change from Debug to Release or Release to Debug.

None.

Documentation
Issue Workaround

The documentation is no longer provided as part of the installation of Windows Embedded Compact.

Individual users can access the help online or through the Visual Studio 2012 Help> Add or Remove Help Content option. If you are a system administrator and want to make offline content available to your users, follow the instructions in the Help Viewer 2.0 Administrator Guide (http://go.microsoft.com/fwlink/p/?LinkId=298913).

Did the topic above help you? [Yes] [No] [Not what I was looking for]

2013 Microsoft. All rights reserved.