You are on page 1of 14

Contents

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

© 2013 Microsoft. All rights reserved.

You can download Microsoft Visual Studio 2012 Update 2 from the Microsoft Download Center (http://go. Microsoft Visual Studio 2012 Update 2. Application Builder for Windows Embedded Compact 2013.microsoft.microsoft.microsoft. All rights reserved.com/fwlink/p/?LinkId=301756).NET Framework 3. Windows Server 2012 (x64-based) and any available service packs. This computer must meet the following requirements: Operating System Your computer must have one of the following operating systems installed. and installed in the following order: 1.5. Microsoft . You can download the installation file from the Microsoft Download Center (http://go. 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.com/fwlink/p/?LinkId=252977).     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. Hardware Your computer must meet the following hardware requirements:       100 GB (NTFS) of available hard disk space 2. 3.com/fwlink/p/?LinkId=301580). You can download the installation file from the Microsoft Download Center (http://go. . 2.Release Notes for Windows Embedded Compact 2013 2 Release Notes for Windows Embedded Compact 2013 This document describes known issues in Windows Embedded Compact 2013. Software Your computer must have the following software installed. Service Pack 1.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.

if you want to enable managed application development.pbcXml) file directly.allow connection .%ProgramFiles% the same subnet.Attach Device option on the Target menu.domain/private/public 2.%ProgramFiles% (x86)\Microsoft Platform Builder\8. . you cannot discover (x86)\Microsoft Platform a device by using Platform Builder and are Builder\8. All rights reserved. For example.sln. Platform Builder is unable to see Windows Firewall: “bootme” files from Windows CE devices on 1.exe . When using the Connectivity Options dialog box.domain/private/public Project solution files for OS designs created in Visual Studio 2008 cannot be opened in Visual Studio 2012.00\CoreCon\BIN\cesvchost. Thus. connection ." If you are using a USB connection to a device and want to reset the target device. don’t use .suo.allow blocked from downloading to the device. The Development languages list is now based on the Sysgen variables that you have included in your OS design. If that doesn't work.Release Notes for Windows Embedded Compact 2013 3 Known Issues and Troubleshooting Known issues and troubleshooting hints for this release are noted in the following sections. Delete the solution files (. Platform-specific Macro in the SDK properties is no longer supported.ncb) and open the OS Design (.00\CoreCon\BIN\cesvchost. Inbound: Program . go to c:\users\[username]\AppData\Local\Microsoft\Embedded Tools\Corecon and rename or delete the 11.reset command from the Target Control window or from the Reset Device option on the Target menu To reset the device.exe . . you need the NetCF Sysgen in your OS project. use the Detach Device and Target . . sometimes this error message will appear: "Platform Builder was unable to read the device settings from the Data Store.0 folder. Outbound: Program . Platform Builder Issue Workaround On a computer running Windows Server Manually add the following inbound/outbound rules to 2012. Restart Visual Studio. © 2013 Microsoft.

dll instead of \windows\lpcrt. Use only one transport type per session. If you have Compact 7 and Compact 2013 devices both created and deployed via Platform Builder (versions 7 and 8. reset the device. Remote Tools will fail with an exception if SYSGEN_REMOTETOOLS is not set on the image.dll points to \windows\msvcrt. 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. Remote Tools will not open while Remote Profiler is capturing the profile data. you cannot use the Save or Save File from Registry Editor As menu options. Workaround: To save items. either TCP/IP or KITL. Do not select an image built with Compact 7. Do not connect to an invalid connection. the full path for plcrt. Incorrect "Full Path" shown for modules in the Remote Process Viewer.Release Notes for Windows Embedded Compact 2013 4 Remote Tools Issue Workaround Remote Tools do not work if Platform Builder is not installed on the C:\ drive. For example. If that doesn’t work. and KITL connection to Remote Tools fails if Remote Tool is called by using TCP/IP. Install Platform Builder on the C:\ drive. respectively). Remote Tools Shell may not respond after opening and closing several Remote Tools.exe. None. Close and reopen the Remote Tools Shell. perform an “end task” on RemoteToolsShell.exe.dll. you cannot use the Compact 2013 version of the Remote Tools to open a Compact 7 image. Close and reopen the Remote Tools Shell. and then close and re-open Visual Studio. . and then close and re-open Visual Studio. All rights reserved. If the Remote Profiler and Remote Registry Editor are both open. close the Remote Profiler if you are using the Remote Registry Editor. © 2013 Microsoft. Set SYSGEN_REMOTETOOLS if you want to use Remote Tools with the image. If that doesn’t work. reset the device.dll) when attempting to connect to an invalid connection. TCP/IP connection to Remote Tools fails if a remote tool is called by using KITL. perform an “end task” on RemoteToolsShell. All Remote tools fail with unhandled exception at 0x67814EB5 (ComMan2.

Timeline viewer does not import . If this message displays. you cannot use the Compact 2013 version of the Remote Tools to open a Compact 7 image. If you have Compact 7 and Compact 2013 devices both created and deployed via pb (versions 7 and 8.Release Notes for Windows Embedded Compact 2013 Issue Workaround 5 the UI. even though the Compact 7 image is listed in the UI. None. you have a mismatched macro LEAF_ENTRY/LEAF_END or NESTED_ENTRY/NESTED_END that you need to address in your assembly file. Do not select an image built with Compact 7. Assembler Compiler Issue Workaround “Error A2092: improper program syntax. uninstall the existing SDK that has the same © 2013 Microsoft. None. otherwise. Software Development Kit (SDK) Issue Workaround Installing an SDK that shares a name with an Do not reuse an SDK name. missing ENDP directive or nested function definition” is raised if you have a macro mismatch in your assembly file. Open Remote Tools from the Windows Start menu instead of from Visual Studio. Closing the Resource Consumer displays a "Connection to the device <device name> failed" error message. opening Remote Tools from the Visual Studio Tools menu will fail if you are not in an OS Design project. Remote Tools cannot connect to a localized image. After closing Resource Consumer. respectively). Only images built with Compact 2013 can use the Compact 2013 version of the remote tools. All rights reserved. . If you have Platform Builder installed.csv file data correctly. restart Visual Studio and reset the device.

" 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. Contact Texas Instruments for an update. TI 4470: The Texas Instruments AAC Audio Close and reopen Visual Studio 2012. TI 4470: The GPIO line used for debugging is not compatible with the Tablet2 hardware platform which can cause disruptions with the USB PHY. Unbuildable SDK created when Solution Explorer is collapsed or closed. TI 4470: Text corruption may occur when using ClearType with Screen rotation. The disruption will result in USB connection errors and failure to recognize the USB device.Release Notes for Windows Embedded Compact 2013 Issue Workaround 6 existing SDK will overwrite the existing SDK. Open Solution Explorer. Contact Texas Instruments for an update. name before installing the new one. © 2013 Microsoft. and then point to "Add New SDK entry. 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. All rights reserved. make it the active window. An "Access Violation" exception is raised for an AMD G Series board if neither VGA or DVI is connected. This is a bug in the Display Driver.reg Contact Texas Instruments for an update. .

For a list of participating BSP and driver providers.Release Notes for Windows Embedded Compact 2013 Issue Workaround 7 Decoder Filter set through the BSP_TI_MULTIMEDIA setting. New board support packages   Windows Embedded Compact 2013 combines the functionality of CEPC BSP and Virtual CEPC BSP into one CEPC BSP. Contact Texas Instruments for an update. see the Windows Embedded Connect Site (http://go.h. may hang during boot.h If you include the Types. ICOP eBox 3300 Freescale i. .h file under %_WINCEROOT%\public\common\sdk\inc.microsoft. does not function correctly when using the Graph Builder. All rights reserved.MX27 Freescale i. © 2013 Microsoft. The new CEPC BSP also supports Hyper-V. TI 4470: OpenGL cannot be used because the PowerVR component in the 4470 BSP does not build correctly.h renamed Cetypes.com/fwlink/p/?LinkID=279030&clcid=0x409). Types.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. Reset the device. when run under Hyper-V emulation. you need to change the statement to include Cetypes.

Release Notes for Windows Embedded Compact 2013 8 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.Forms. and the file does not compile.Dpi. . Set the Autoscaling property manually if automatic scaling is required.Windows. when you manually add the user control to the Toolbox. Manually move the controls after adding them to the design surface. Add the control to the Device Application project manually in code.Windows. Using the Table Collection Editor to add a DataTable object to a DataSet control does not add the DataTable correctly. © 2013 Microsoft. for example: In Visual Basic: Me. the event handler is not added. Add the DataTable object in code. 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. Manually add the event-handling method and associate it with the FileOk event.Dpi In C#: this. Automatic scaling is turned off by default in the project templates. When you reference a Control Library project from a Device Application project and build the solution. it is not displayed. Adding controls to a collection property by using Add the controls to the collection in code.AutoScaleMode. All rights reserved.AutoScaleMode = System.Forms.AutoScaleMode = System.AutoScaleMode. the collection editor for a Control Library project does not add the controls correctly. and the code does not compile. In addition. the user control does not appear in the Toolbox.

XAML for Windows Embedded does not support AC3 font compression. you will be prompted for an IP address. the code continues execution as if you pressed F5 (Start © 2013 Microsoft. XAML for Windows Embedded does not work with pluggable font engines like Monotype’s iType. You must clear the Sysgen variable SYSGEN_AC3_FONT when using XAML for Windows Embedded. None. In addition.cpp subproject1.rct) files that are created and added to the resource template directory (<installDir\Program Files\Microsoft Visual Studio 11. Open the sources file by double-clicking on the subproject in your OS design. The subproject template for Compact 2013 applications does not automatically add . All rights reserved. When you're debugging a try/catch statement None.rc file with extension to the SOURCES macro.0\VC\VCResourceTemplates\1033) are not displayed in Visual Studio when you choose the Add Resource command. . in C++. an IP address setting. Resource template (.rc. Use the standard fonts provided with Compact 2013.Release Notes for Windows Embedded Compact 2013 9 Application Development: Native code (C++) Issue Workaround Using the CreateProcess function fails at compile time because it is not a Unicode API.rc files to the build. Application Development: Debugging and Deployment Issue Workaround The Debug and Release configurations require None. then add the name of the . if you set a breakpoint on code that throws an exception and press F10 (Step Over) when the breakpoint is hit. If you switch between the Debug and Release configurations. Manually add a #define Unicode statement to the code file. for example SOURCES=subproject1.

rc files to the build. Calling Remote Tools from Platform Builder causes application deployment activities to stop. The subproject template for Compact 2013 “Application” does not automatically add . To work around this. open the © 2013 Microsoft. Copy the entire contents of Corecon <drive>\%prog files%\common files\microsoft shared\embedded tools\corecon\11. choose Debug > Exceptions. which uses TCP/IP. C++ Exceptions Common Language Runtime Exceptions Win32 Exceptions Use two different Visual Studio instances to attach to two different application processes. When selecting the Windows Embedded Compact Device. 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. The Start Debugging command (F5) will fail for C++ projects if the Remote Directory path in the project's Configuration Properties. When you're debugging a native application and you've selected to break only on Microsoft Win32 exceptions (by using Debug > Exceptions > Win32 Exceptions). Launch all remote tools from the Start menu. 2. 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. control goes to external code for first-chance exceptions. All rights reserved. Some operating system files will be deployed to the default location instead of the specified remote directory. is changed to something other than the default path. use the Windows CE Application Builder connection. Resource strings in an application sub-project cannot be retrieved. while launching from the Start menu lets you choose to use the Windows CE Application Builder (also known as TCPIP) connection.Release Notes for Windows Embedded Compact 2013 10 Issue Workaround Debugging) instead. On the menu bar. . on the Deployment tab. instead of the Windows Embedded Compact Default Platform. Launching from Platform Builder defaults the connection to use KITL. 1. Deploying an application to a device after using a remote tool fails.0\target\wce800\<cpu> to your release directory.

g. as in the following example: void Win32BDM::CBaseDebugMonitor::NameDebugThread() { typedef struct tagTHREADNAME_INFO { DWORD dwType. then add the name of the rc file with extension to the SOURCES macro. . // pointer to name (in user addr space) DWORD dwThreadID. where the target register of the load is the program counter. For an application to be debugged. // thread ID (1=caller thread) DWORD dwFlags. 0x406d1388 exception is raised when trying to debug Native ATL applications on CEPC.cpp subproject1. e. stepping into or stepping over code with this instruction.Release Notes for Windows Embedded Compact 2013 11 Issue Workaround sources file by double clicking on the subproject in your OS Design. will not work.rc. want to debug applications. Furthermore. must be zero } THREADNAME_INFO. the LDRSH instruction is not recognized by the disassembler and shows the instruction as undefined. you can use additional breakpoints instead of step into or step over. Debugger Issue Workaround When viewing the disassembly of code. All rights reserved. SOURCES=subproject1. © 2013 Microsoft. For stepping. the image Add SYSGEN_APPDEBUG to your OS design if you needs to include SYSGEN_APPDEBUG. // reserved for future use. // must be 0x1000 LPCSTR szName. Catch the exception.

dwType = 0x1000. info. __try { RaiseException( 0x406D1388. All rights reserved.dwFlags = 0. The CTK disconnects form a devices and exits the test pass if the device reboots.Release Notes for Windows Embedded Compact 2013 12 Issue Workaround THREADNAME_INFO info. The easiest way to disable the cpuload policy is to exclude SYSGEN_PM (or anything that pulls in SYSGEN_PM) from your image. Disable the cpuload policy before running this test. Restart the test pass if the device reboots. 0.dwThreadID = GetCurrentThreadId(). info.szName = "Debugger Event Loop Thread". 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. None. } __except(EXCEPTION_CONTINUE_EXECUTION) { } } Code Map does not work for Compact 2013 projects.dll to fail. info. sizeof(info)/sizeof(ULONG_PTR). © 2013 Microsoft. info. (ULONG_PTR*)&info ). .

Install a 32-bit virtual machine on a 64-bit machine and install the driver on the 32bit virtual machine to run the test. Copy apcontrol. 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(). 1. 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. If you want to use another keyboard layout in Virtual PC.0\files” (x86)\WindowsEmbeddedCompact2013TestKit\tests\tar get\x86\apcontrol. . All rights reserved.0. Run the test on a 32-bit OS. Select both a language and a sub-region when creating a localized OS Design.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. Copy eaptls.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. Attempting to connect to a device with a localized OS displays a "Parameter Incorrect" error message.exe 2. but the shipped driver is compiled with 32-bit OS and does not work on 64-bit OS machines. see Software-based Input Panel.cfg 1.0\files\eaptls. For more information. 0. you must use a SIP.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. © 2013 Microsoft. NDIS6 performance test requires driver installation to run. 2. or by setting the "SIP_UP" SYSGEN variable). Stop the CTK in Compact 2013 to launch the Compact 7 version of the tool.

microsoft. Documentation Issue Workaround The documentation is no longer provided as part of the installation of Windows Embedded Compact.0 Administrator Guide (http://go. Did the topic above help you? [Yes] [No] [Not what I was looking for] © 2013 Microsoft. If you are a system administrator and want to make offline content available to your users.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. Individual users can access the help online or through the Visual Studio 2012 Help> Add or Remove Help Content option. follow the instructions in the Help Viewer 2. .com/fwlink/p/?LinkId=298913). None. All rights reserved.