5/29/2008

This document describes known issues for Windows Embedded NavReady 2009.

To view the latest, up-to-date release notes at MSDN Library, see this Microsoft Web site.

Windows Embedded NavReady provides the following new features that you can implement on a portable navigation device (PND):

Contents

System Requirements

To run Windows Embedded NavReady, the development workstation must meet the following specifications:

  • 400-MHz Pentium II or later processor; 1-GHz processor is recommended.

  • Microsoft Windows 2000 Professional with Service Pack 4 or later, or Windows XP Professional with Service Pack 1 or later.

  • Microsoft .NET Framework, version 1.1.

  • 256 MB of RAM; 512 MB of RAM is recommended.

  • 1.7 GB of available hard-disk space for a typical single microprocessor installation; approximately 17 GB for installation of the entire product, including the Platform Builder for Microsoft Windows CE 5.0 toolset.

  • VGA or higher-resolution monitor; Super VGA is recommended.

  • Microsoft Mouse or similar pointing device.

  • Serial port or Ethernet card for debugging support; a LAN hub is recommended.

  • CD-ROM or DVD-ROM drive.

Installing Windows Embedded NavReady

Windows Embedded NavReady is an addition to the Windows CE 5.0 operating system (OS). To install Windows Embedded NavReady, follow the installation steps below.

To install Windows Embedded NavReady

  1. Install Platform Builder with ARMV4I architecture for Windows CE 5.0.

  2. After you install it for the first time, launch Platform Builder for Windows CE 5.0 once, and then close it.

  3. Install all current updates for Windows CE 5.0 at this Microsoft Web site.

  4. Install Windows Embedded NavReady by double-clicking Windows Embedded NavReady.msi.

  5. Install all current updates for Windows Embedded NavReady at this Microsoft Web site.

Repairing Windows Embedded NavReady

To repair Windows Embedded NavReady, follow the steps below.

To repair Windows Embedded NavReady

  1. Click Start, click Control Panel, and then double-click Add or Remove Programs.

  2. In the Currently Installed Programs box, click Windows Embedded NavReady and then click Change.

  3. You can either Repair or Remove Windows Embedded NavReady.

Uninstalling Windows Embedded NavReady

To uninstall Windows Embedded NavReady, follow the steps below.

To uninstall Windows Embedded NavReady

  1. Click Start, click Control Panel, and then double-click Add or Remove Programs.

  2. In the Currently Installed Programs box, click Windows Embedded NavReady and then click Remove.

Copyright Information for Windows Embedded NavReady

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, Active Desktop, Active Directory, ActiveSync, ActiveX, ClearType, Direct3D, DirectDraw, DirectInput, DirectShow, DirectSound, DirectX, IntelliMouse, IntelliSense, JScript, MSDN, MSN, MS-DOS, NavReady, Outlook, the PlaysForSure logo, PowerPoint, SideShow, Tahoma, Visual Basic, Visual C#, Visual C++, Visual InterDev, Visual Studio, Windows, Windows Live, Windows Media, Windows NT, Windows Server, Windows Vista, and Win32 are trademarks of the Microsoft group of companies.

Portions of this software are based on NCSA Mosaic. NCSA Mosaic was developed by the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign. Distributed under a licensing agreement with Spyglass, Inc.

Contains security software licensed from RSA Data Security, Inc.

All other trademarks are property of their respective owners.

License Terms

The license terms for Windows Embedded NavReady and shared source can be accessed from <SYSTEM DRIVE>:\Program Files\Windows CE Platform Builder\5.00\Windows Embedded NavReady_License.rtf.

Technical Support and Community

To learn more about available support and community options for this release, see Windows Embedded Community on this Microsoft Web site.

To view the latest, up-to-date content at MSDN Library, see the documentation for Windows Embedded NavReady at this Microsoft Web site.

Known Issues for Windows Embedded NavReady

Connection Manager APIs

A2DP Driver Selection

Ignoring an Incoming Hands-free Device Connection

Bluetooth Dial-up Networking (DUN) Takes Time To Set Up the Connection

Built-in BCSP Driver Does Not Support On/Off

Bluetooth Audio IOCTL Usage

Connection Manager APIs

The Connection Manager does not perform strict validation on its parameters for some of the less-frequently used APIs. For example, if ConnMgrQueryDetailedStatus is called with NULL parameters, the behavior is not defined.

To avoid unexpected behavior, be careful to pass valid parameters to the Connection Manager APIs.

A2DP Driver Selection

Unlike in Windows Embedded CE 6.0 and Windows Mobile 6, in Windows Embedded NavReady the Advanced Audio Distribution Profile (A2DP) driver is not set as the default wave driver when active.

Applications that require A2DP audio output must manually open the A2DP wave device instead of the default wave device.

Ignoring an Incoming Hands-free Device Connection

Ignoring an incoming connection request from a hands-free device may result in subsequent incoming connections being dropped, as the first connection is not properly disconnected.

To reject an incoming connection request, first activate and then deactivate the phone using the following functions:

HRESULT HFPActivatePhone( BT_ADDR* pbta, HHFPPHONE* phPhone );
HRESULT HFPDeactivatePhone( HFPPHONE hPhone);

Bluetooth Dial-up Networking (DUN) Takes Time to Set Up the Connection

Bluetooth Dial-up Networking (DUN) can take some time to set up the connection.

You can decrease the time required by adding the following registry keys:

[HKEY_LOCAL_MACHINE\Comm\PPP\Parms]
   "IPV6Disable"=dword:00000001

[HKEY_LOCAL_MACHINE\Comm\PPP\Parms]
   "DHCPMaxTries"=dword:0

Built-in BCSP Driver Does Not Support On/Off

The Bluetooth BCSP driver shipped with Windows Embedded NavReady, bthcsr, does not support turning the hardware off and on at runtime. Invoking IOCTL_SERVICE_STOP or IOCTL_SERVICE_START on BTD0 with this driver in use will result in undefined behavior.

Obtain the updated driver from CSR at this Web site.

Bluetooth Audio IOCTL Usage

The Bluetooth hands-free service uses the following WODM_BT_SCO_AUDIO_CONTROL IOCTL on WAV1 with the following parameters in the MMDRV_MESSAGE_PARAMS structure to control the routing of SCO audio:

Parameter1 Parameter2 Description

0

FALSE

Route wave output to speaker (SCO audio disabled).

0

TRUE

Route Bluetooth SCO audio to AG (not used by HF profile).

1

TRUE

Route Bluetooth SCO audio to microphone and speaker.

3

TRUE

Enable Acoustic Echo Cancellation (AEC) hardware (default).

3

FALSE

Disable Acoustic Echo Cancellation (AEC) hardware.

11

TRUE

Disable (mute) microphone.

12

TRUE

Enable microphone.

Set the variables as in the following example:

MMDRV_MESAGE_PARAMS params;
msg.uMsg = WODM_BT_SCO_AUDIO_CONTROL;
msg.dwParam1 = Parameter1;
msg.dwParam2 = Parameter2;
DeviceIoControl( hWavDev, IOCTL_WAV_MESSAGE, &params, sizeof(MMDRV_MESSAGE_PARAMS), NULL, 0, NULL, NULL );