To help prevent malware from being installed on a Windows Embedded CE powered device, Auto Download and Auto Install are both disabled in Internet Explorer 6 (Urlmon).

When an end user downloads or installs an application on a Windows Embedded CE powered device, a message box appears with a security warning and requests that the end user confirm installation of the application. With Auto Download and Auto Install disabled, Internet Explorer 6 cannot install any software or change settings without the consent of the end user.

A compilation error is generated by the WsdCodeGen utility when the character "." is used in a WSDL file. A WSDL file is also known as a service contract. The WsdCodeGen utility generates output files without an error or warning message because the generated code contains macro definitions that the C++ compiler cannot compile.

To resolve the error, remove the special character "." from the WSDL file before running the WsdCodeGen utility.

This known issue is expected to be resolved in the next release of the Microsoft Windows Software Development Kit (SDK).

After WSDAPI.dll loads, you cannot unload this DLL from a running process on Windows Embedded CE 6.0 R2. WSDAPI.dll can only be unloaded during process termination. Resource overhead is minimal associated with WSDAPI.dll remaining loaded until process termination.

Touch pad tests are manual tests where the user is prompted for input and must follow instructions that are provided on the test screen. Some tests also prompt for pass or fail status from the user, based on the observations of the user.

A device reboot is required after a touch test is run. After the touch test completes, the device no longer responds to touch events. If user input is not received within the time-out period, the touch test times out.

Touch tests are not supported on Device Emulator.

When you run the touch pad tests for touch screen devices, sometimes the test window is not drawn on the touch screen.

By design, test cases 8001, 8002, and 8003 do not draw a test window on the touch screen.

If the test window is not drawn on the touch screen for a test case that should draw a test window, tap directly on the screen.

The Windows Embedded CE certificate validation time displays a seven-hour difference from the validation time of the certificate on the server.

Features are different for Windows Embedded CE 6.0 and Windows Embedded CE 6.0 R2. When you build a run-time image from the command line, the user can specify which release to target for each feature, or Catalog item. In contrast, when you build a run-time image from the Platform Builder user interface, versioning is not a concern because only Catalog items that are updated or new for Windows Embedded CE 6.0 R2 appear in the Catalog. By default, when you build from the Platform Builder user interface, all Catalog items included in a run-time image are for Windows Embedded CE 6.0 R2.

If you build from the command line and use Catalog items from Windows Embedded CE 6.0 that have dependencies on other Catalog items (for example the VoIP Catalog items), verify that the dependent Catalog items target the same release of Windows Embedded CE.

In Windows Embedded CE 6.0 R2, your WSDAPI configuration must not support more than 5 unique device hosts per process and/or 5 unique client-side proxies per process.

When you use asynchronous messaging, be aware that the maximum number of connections per remote HTTP 1.1 server is 2 connections, while the maximum number of connections per HTTP 1.0 server is 4 connections. After the connection limit is reached, any new request is not serviced until an outstanding request is completed.

In RDP 6.0, the Windows Embedded CE Terminal Services Client (CETSC) user interface contains a Help button that starts Help documentation for the RDP user. However, HTML Help support and end-user Help files about RDP are not included with RDP. Therefore, when the user clicks the Help button, Help information is not displayed to the user.

To display Help information as expected, either include your own Help files for the CETSC user interface in the run-time image, or remove the Help button from the user interface. To remove the Help button from the user interface, you must modify the following source files:

• %_WINCEROOT%\PUBLIC\RDP\OAK\CETSC\uires.rc
  
  
• %_WINCEROOT%\PUBLIC\RDP\OAK\CETSC\maindlg.cpp
  
  
• %_WINCEROOT%\PUBLIC\RDP\OAK\CETSC\shapi.cpp
  
  

For WSDAPI, when you use the abort operation together with asynchronous functionality, a client or service might experience a disruption in the operation of other asynchronous threads.

To address the disruption, try one of the following:

1. Do not use the abort operation.
   
   
2. Use synchronous operations instead.
   
   
3. Retry async operations that time out or fail.
   
   
4. When you use the abort operation, ensure that future asynchronous requests are delayed. For example, wait 200 milliseconds before you send more requests after you use the abort operation.
   
   

When a USB CCID compliant Smart Card reader is attached to a Windows Embedded CE powered device with SYSGEN_USB_SMARTCARD set correctly in the run-time image, the Windows Embedded CE 6.0 Test Kit (CETK) still does not correctly detect the presence of the peripheral hardware. Therefore, the CETK incorrectly displays an informational icon that indicates that peripheral hardware was not detected.

You can still test the USB CCID Smart Card reader by using the CETK, even though the CETK user interface indicates that the Smart Card peripheral hardware was not detected.

On busy wireless networks without Quality of Service (QoS), the quality of outgoing VoIP audio may become degraded because of jitter. If distorted audio output occurs, or if a large percentage of late packets are detected, increase the size of the playout buffer, or jitter buffer, on your gateway device. For more information, see your gateway documentation or your IP private branch exchange (PBX) service documentation.

ActiveSync 4.5 fully supports synchronizing contact information and appointment information between Windows Embedded CE powered devices and Windows XP. However, with Windows Vista, some information might not synchronize correctly when you use Windows Mobile Device Center (WMDC). Specifically, Yomi fields for contacts in the Japanese language are not synchronized between Windows Embedded CE powered devices and WMDC.

The Remote Diagnostics Log tool is intended to be used for diagnostics purposes only, and not for commercial purposes such as customer billing for VoIP services. Additionally, although you can use the API of the logging tool to add custom debugging messages to the logger, the API is unsupported. Therefore, we recommend that you not use the API for custom logging.

The Close Window button that appears in the lower-right corner of Install.htm does not close the window when you click it.

To close Install.htm, click on the close icon in the upper-right corner of the window.

A description of the Remote Diagnostics Log for VoIP is not yet included in the Windows Embedded CE 6.0 R2 documentation.

To enable logging in a VoIP run-time image, take one or more of the following approaches:

• Enable event logging by adding SYSGEN_EVENTLOG to the operating system (OS) design. Enabling event logging ensures that all logged events are sent to two log files, both stored in the Windows directory. The log files are treated as a circular file system. When one file fills, logging starts on another file.
  
  
• Enable the VoIP-specific logging features by adding SYSGEN_FPVOIP_VOIPEVENTLOG=1 to the OS design. Setting SYSGEN_FPVOIP_VOIPEVENTLOG=1 routes the files to \Program Files and causes logged events to be echoed to a Telnet session, if such a session exists.
  
  
• Add Telnet capability by adding SYSGEN_TELNETD. We recommend that you also set a custom Telnet password in the registry. For more information, see Telnet Server Registry Settings in the Windows Embedded CE 6.0 R2 documentation.
  
  

If you set up the VoIP telephone run-time image by completing all three of the previous steps for the OS design, Telnet-based logging can be handled in the following way:

1. If logging is not enabled by default, enable logging through the VoIP telephone registry. You can enable logging through the remote provisioning approach described in the Windows Embedded CE 6.0 R2 documentation. The following two registry keys can be set:
   
   
   • HKEY_LOCAL_MACHINE\System\State\VoIP\LogSettings: The MODE value specifies the logging mode for the device.
     
     

     Disable	0x00000000
     Event Log Only	0x00000001 This is the default value
     Telnet and Event Log	0x00000004

   • HKEY_LOCAL_MACHINE\System\State\VoIP\LogSettings: The DIRECTORY value specifies the file directory where the log files will be written.
     
     
2. Telnet into the VoIP telephone (for example, Telnet <IPAddress>) and type the Telnet password.
   
   Events are logged to the Telnet session so that the administrator can save the results to a file on the administrator's computer.
   
   
3. End the Telnet session.
   
   

The following suggestions relate to configuring the STMicroelectronics STi7109 MB442 development platform.

• When you connect a component video cable to the STMicroelectronics STi7109 MB442 development platform, ensure that the component video cables plug into the video output connectors located immediately next to the High Definition Multimedia Interface (HDMI) connector.
  
  
• The default video mode on the development platform is Mode 1 (720p, component video output).
  
  You can change the video mode on the boot loader menu. From the boot loader menu, select option 6 (Set Video Output), and then select option 2 (Graphic Driver Mode). Next, enter the mode that you want. The following options are available:
  
  
  1. 720p, component video output
     
     
  2. 720p, HDMI output
     
     
  3. 1080i, component video output
     
     
  4. 1080i, HDMI output
     
     
  5. 1024 × 768 VGA, use this option only if you compiled the BSP with the environment variable BSP_VGA_OUT=1
     
     
  You can also change the default video mode in the platform.reg registry file. The registry entry is HKEY_LOCAL_MACHINE\Drivers\BuiltIn\STPDEV "VideoMode". Set this registry value to the new default mode, which can be a mode from the previous list.
  
  
• If you made changes to the registry structure, start with a clean registry. To clean the registry, on the boot loader menu, select option 5 (Toggle Clean Registry) to toggle the value to TRUE, and then continue to boot the device.
  
  

To connect to a Windows network projector, the custom device metadata in the registry, which includes strings for Manufacturer and Model, must follow these rules:

• In each string, use the backslash character "\" before you use the following characters :
  
  

  ' " \

• In each string, a backslash character "\" must not come before any other Valid Escape Sequence (such as 0, a, b, f, n, r, t, u, U, x, v) or Invalid Escape Sequence (such as e, g, z, and so on).
  
  
• A device metadata value cannot be empty or a space (" ").
  
  

The WSDAPI Implementation Guide is available at MSDN. The following information might be useful to device manufacturers and other device implementers who create DPWS-compliant devices that interoperate with Windows-based WSDAPI client applications and device hosts without using the Microsoft WSDAPI implementation.

• WSDAPI Specification Compliance: For information about the implementation of WSDAPI relative to the underlying specifications, see this Microsoft Web site. At this Web site, you can find information about the required functionality, optional functionality, and additional functionality not defined in the specification.
  
  
• WSD Device Implementation Recommendations: For recommendations that help reduce the complexity of DPWS-compliant device code and increase the level of interoperability on WSDAPI, see this Microsoft Web site.
  
  

The Audio Drift Test plays a specified audio file and tests whether playback drifts by one or more buffer lengths.

The Audio Loop-back test plays a specified audio file, captures the audio output using a loop-back cable, and saves the captured audio signal to an output file.

To run the VoIP audio quality tests for Windows Embedded CE, you must install the required audio cables. The hardware engineer or hardware technician is responsible for constructing the audio cables. The VoIP audio quality tests can help verify specific aspects of audio quality on your Windows Embedded CE powered device.

The following two cables are required for the VoIP audio quality tests:

1. Loop-back cable: This cable feeds the audio output of the device-under-test (DUT) back into its audio input.
   
   
2. Development workstation connection cable: This cable connects the DUT to the development workstation that plays or records test audio.
   
   
   • The development workstation connection cable can be separated into two cables, one for each direction (development workstation-to-DUT, DUT-to-development workstation).
     
     

To construct the audio cables:

1. Assemble the Loopback audio cable according to the following steps.
   
   
   1. Obtain a headset plug for the device under test. This may be a wired headset that is disassembled for the creation of the loopback cable.
      
      
   2. Create a resistive voltage divider between the right output audio wire and the ground wire: connect a 1 KB ohm resistor (R1) and a 10 ohm resistor (R2) in series between right output audio wire and ground wire. Optionally, replace one of these resistors with a potentiometer for easier configuration.
      
      
   3. Connect the microphone wire to the voltage divider, with a 220 uF capacitor (C1) in between them. That is, connect the microphone wire to one end of the capacitor and the other end to the net between R1 and R2.
      
      
   4. Add a 2 KB ohm resistor (R3) between the microphone wire and ground wire.
      
      
   5. Leave the left output wire unconnected.
      
      
2. Assemble the desktop workstation connection cable according to the following steps.
   
   
   1. For DUT-to-desktop workstation, no voltage divider is required since the output of the device is typically not biased. Connect the Left and Right audio wires from the DUT connector to the Line In left and right channels, with a 220 uF capacitor in between for filtering.
      
      
   2. For desktop workstation-to-DUT, a voltage divider is required since the microphone is typically biased. Use only the Right output channel on the desktop workstation, and connect to the microphone wire on the DUT. Notice that this step is similar to the previous loopback cable step. Create a resistive voltage divider between the right output audio wire on the desktop workstation and the ground wire: connect a 1 KB ohm resistor (R1) and a 10 ohm resistor (R2) in series between the right output and ground. Optionally, you can replace one of these resistors with a potentiometer for easier configuration.
      
      
   3. Connect the microphone wire to the voltage divider, with a 220 uF capacitor (C1) in between. That is, connect the microphone wire to one end of the capacitor and the other end to the net between R1 and R2.
      
      
   4. Add a 2 KB ohm resistor (R3) between the microphone wire and ground wire.
      
      
   5. Connect the ground wire from the desktop workstation-in, desktop workstation-out, and DUT connectors together.
      
      
3. Adjust resistor values to calibrate audio gain.
   
   
   • Play back and record a full-scale sine wave at -1 to -3 dB. For the playback procedure, see Audio Quality Test in the Windows Embedded CE 6.0 R2 documentation.
     
     
   • If the recorded peak of the sine wave from the audio file is less than -10 dB, increase the gain by decreasing the value of R2 or by increasing the value of R1.
     
     
   • If the recorded sine wave from the audio file is clipping, decrease the gain by increasing the value of R2 or by decreasing the value of R1.
     
     

The VoIP_PXA270 platform requires that you add SYSGEN variables to the IP Phone Advanced OS design.

The VoIP_PXA270 device is a Wi-Fi–enabled handheld device with a portrait display and requires additional functionality to operate correctly. To support this additional functionality, you must add the following SYSGEN variables to your IP Phone Advanced OS design:

• SYSGEN_PM_PDA – adds Windows Mobile–style power manager framework.
  
  
• SYSGEN_BATTERY – adds battery driver support.
  
  
• SYSGEN_ETH_80211 – adds wireless LAN support and automatic configuration.
  
  
• SYSGEN_QVGAP – adds support for Quarter VGA resources (portrait mode) to the OS shell.
  
  
• SYSGEN_VOIPPHONE_PHONEIME – adds triple-tap functionality that enables users to enter text by using a numeric keypad.
  
  
• SYSGEN_FPVOIP_RESOURCE_PORT – adds VoIP sample portrait-mode resources for phone suite.
  
  

After installing Windows Embedded CE 6.0 R2, the first time that you click any link titled Microsoft Web Site or Web Site in the Windows Embedded CE 6.0 R2 documentation, sometimes a delay of up to 2 minutes can occur before the external Web page is displayed in Microsoft Document Explorer.

For subsequent clicks of any link titled Microsoft Web Site or Web Site, any delay is minimal.

The VoIP user interface assumes that it has access to a contacts database.

To add support for the contacts database, you must include SYSGEN_POOM in the run-time image. If the VoIP phone does not have a contacts database, all references to Contacts in the UI should be removed by the OEM. Remove the main menu item for Contacts from the Navigation .xml file and remove Save to Contacts from the menu bars defined in the DialogMenus_Land.rc or DialogMenus_Port.rc resource files.

The Device Emulator in Windows Embedded CE 6.0 does not receive multicast messages, which is a challenge if you want to create WSDAPI services and test the services by using the Device Emulator. Without multicast support, services are not discoverable, WS-Discovery Probe and Resolve messages cannot be received, and client-side proxies cannot receive WS-Discovery Hello and Bye messages.

This known issue applies to customers with Windows Embedded CE 6.0 R2 documentation that is localized to the Japanese language. For this localized documentation, recently updated information exists for Web Services on Devices Security that is not provided in the localized version of the documentation.

VoIP three-way conferencing is a feature in Windows Embedded CE 6.0 R2. Previously, the Real-Time Client (RTC) relied on media servers to perform audio mixing to achieve three-way conferencing.  When global media mixing is enabled in RTC, it mixes audio locally and thus achieves three-way or n-way conferencing without assistance from the media server.

Platform Manager (SYSGEN_PLATFORM) is no longer available in the Catalog. This Catalog item is not supported in Windows Embedded CE 6.0. If you include the Catalog item in an OS design, a build error occurs. This change does not affect the CETK.

In Windows Embedded CE 6.0, SYSGEN_USB_SMARTCARD included the SCM Microsystems SCR300 USB Smart Card driver. In Windows Embedded CE 6.0 R2, SYSGEN_USB_SMARTCARD includes both the SCR300 driver and the new CCID USB Smart Card driver. To exclude a driver, you can modify the Platform.bib file for the OS design during the OS design phase. For more information, see How to Create a Device Driver in the Windows Embedded CE Help documentation.

After you build a run-time image based on an OS design, you can check the Catalog item dependencies in your OS design at any point during the development process. For more information, see How to Check the Dependencies of a Catalog Item in the Windows Embedded CE Help documentation.

Windows Embedded CE 6.0 R2 represents the last release in which the MIPS16 Application-Specific Extension (ASE) to MIPSII ISA architecture is supported. Later releases do not support MIPS16 architecture. However, later releases continue to support other MIPS architectures.

The process to connect to a remote server to establish a Terminal Services session has changed from RDP 5.2 to RDP 6.0. For RDP 6.0, this process now involves interaction with CredUI and Network Level Authentication. To provide an encrypted channel, the step that establishes a connection to the remote server has changed. This step is highlighted in bold font in the following processes.

For more information about CredUI and Network Level Authentication, see the topic, RDP Security in the Windows Embedded CE 6.0 R2 documentation.

With RDP 6.0, ActiveX Control mode is the only mode of operation. Windows mode is no longer supported. Therefore, the following functions are no longer useful for creating a virtual channel based on RDP 6.0:

• VirtualChannelCloseEx
  
  
• VirtualChannelEntryEx
  
  
• VirtualChannelInitEventEx
  
  
• VirtualChannelInitEx
  
  
• VirtualChannelOpenEventEx
  
  
• VirtualChannelOpenEx
  
  
• VirtualChannelWriteEx
  
  

An updated version of the Remote Desktop Connection client is available with RDP 6.0. It also uses new settings in the .rdp file. In Windows Embedded CE 6.0 R2, the updated version of the Remote Desktop Connection client is automatically included with SYSGEN_RDP.

For more information, see Windows Embedded CE Terminal Services Client (CETSC) and Terminal Services Client Configuration through the .rdp File in the Windows Embedded CE 6.0 R2 documentation.