Microsoft© eMbedded Visual Tools 3.0 Readme

April 2000

For more information about the eMbedded Visual Tools, please visit our website located at http://www.microsoft.com/windows/embedded/ce.

To locate material in these Release Notes, select one of the general categories under Contents, or choose Find from the Edit menu of the browser.

Contents

Supported SDKs

This release supports the following SDKs:

Requirements

To use Microsoft eMbedded Visual Tools 3.0, you need to have the following:

Installation

International Setup Issues

Installing the WWE version of eMbedded Visual Tools requires that SP5 is installed if you are using NT4 and that IE 5.1 is installed. When installing the eMbedded Visual Tools on Japanese or German OSes, you are prompted with a message in English asking you to upgrade these two products. If possible, you should upgrade both of these products using the version that matches the language of your OS.

Using German installed folder names causes the uninstall wizard to fail. Do not install eMbedded Visual Tools on a pathway with German characters.

Side-by-Side Visual Studio 6.x Installation Issues

To develop for HPC Pro and Palm-size PC 1.2 devices, you must install the new Windows CE SDKs for those platforms, which are included with eMbedded Visual Tools. To develop for the Pocket PC, you must install the new Windows CE SDK for this platform as well.

If you install VBCE 6.0 after installing eMbedded Visual Basic 3.0, the new HPC Pro SDK will be replaced with the old one. You will have to re-install the new HPC Pro SDK.

If you uninstall VBCE 6.0 after installing eMbedded Visual Basic 3.0, the HPC Pro SDK will be removed. To develop for this platform, you must re-install the new HPC Pro SDK.

Known Issues

Platform Manager and Remote Tools

Changing the Configuration values for PPP or TCP/IP does not prompt a reconnection to the device. If you change the settings in Platform Manager using the Platform Manager Configuration dialog box, you must disconnect your target device and then reconnect the device. Otherwise, your new settings will be ignored.

Pressing the Title bar on the Downloading dialog box during a download may cause the download to halt. Within both IDEs, if you build and download an application to a device, clicking on the title bar of the Downloading dialog box causes the operation to fail.

The remote tools included with eMbedded Visual Tools do not work with Japanese SH4 Jupiter devices. The remote tools have a problem connecting to SH4 H/PC Pro Japanese devices.

Disconnect from the emulator before closing the Remote Tools. If you close the emulator while a remote tool has an existing connection, the tool will stop responding. Always disconnect your remote tool from emulation before you shut down emulation. If a Remote Tool does cease to function, close the Tool using the Task Manager and restart the Tool.

If you have an active connection to a device with File Viewer and the connection is interrupted temporarily, the File Viewer Tool will not recover. Close the File Viewer using the Task Manager and restart it.

If double backslashes (\\) are used in the Platform Manager Open Executable dialog when debugging from the IDE, a Server Busy dialog box appears. The IDE has to be closed to exit from this state.

SDK issues

If uninstalling an eMbedded Visual C++ SDK, always uninstall the eMbedded Visual Basic SDK that is from the same platform. Then reinstall just the eMbedded Visual Basic portion of the SDK. Removing only eMbedded Visual C++ portion of rolled SDK does not remove references to that SDK from the eMbedded Visual C++ IDE. A fatal error results if you try to build the project for the uninstalled SDK in the eMbedded Visual C++ IDE.

HTML Help Collection

In the HTML Help window, the following options on the Help menu do not function: MSDN Library Help and MSDN Online.

UnInstalling eMbedded Visual Tools

Following a complete uninstall of Microsoft eMbedded Tools (including all SDKs), your drive may still contain a utility file under the directory path "Windows CE Tools\bin". You may safely delete this utility file and the directory path without problems.

APIs That Behave Differently Under Emulation

The SipShowIM function requires an undocumented flag, SIPF_DOCKED, to work properly under emulation. Use a C bitwise OR operator to combine the SIPF_DOCKED flag with the SIPF_ON flag to display an input panel, and combine SIPF_DOCKED with SIPF_OFF to hide an input panel. This combination of flags works both for emulation and for Windows CE-Based devices.

GWES: File cannot be saved over an existing file without disconnecting from the service.

In PMail, if a user receives an email with a file attachment, and tries to save the attachment, the save operation will fail if a file by the same name exists in "My Documents". User will receive a Critical Inbox error modal: "Unable to copy this attached file." If user disconnects from the service, the save operation will succeed.

GWES: CreateBitmap expects applications to specify colors in the order blue, green, and red.

If you create a color bitmap by using the CreateBitmap function, specify the colors in the order blue, green, and red, rather than in the order red, green, and blue.

Kernel: Value for the dwProcessorType member of the SYSTEM_INFO structure changed

The PROCESSOR_PPC_821 value that is used in the dwProcessorType member of the SYSTEM_INFO structure in Windows CE 2.12 and earlier has been changed to PROCESSOR_MOTOROLA_821 in Windows CE 3.0.

Technical Support

You can obtain technical support by visiting MSDN Online Support. This site provides resources ranging from self-help tools to direct assistance from a Microsoft technical engineer. These resources include:

Additional Documentation

If you have accepted the default directories when installing Microsoft eMbedded Visual Tools, additional documentation can be found in the following locations:

Subject Area Default Path and File Name
Installation and Setup C:\Program Files\Microsoft eMbedded Tools\README.HTM
eMbedded Visual Basic C:\Program Files\Microsoft eMbedded Tools\EVB\releasenotes.htm
eMbedded Visual C++ C:\Program Files\Microsoft eMbedded Tools\EVC\releasenotes.htm
SDK: H/PC Pro C:\Windows CE Tools\hpcproreadme.htm
SDK: Palm-size PC 1.2 C:\Windows CE Tools\pspc12readme.htm
SDK: Pocket PC C:\Windows CE Tools\pocketpcreadme.htm

Legal Information

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person 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.

© 2000 Microsoft Corporation. All rights reserved.

Microsoft; MS-DOS; Windows; Windows NT; eMbedded Visual Basic; eMbedded Visual C++; SDK for Windows CE, Handheld PC Professional Edition 3.0; SDK for Windows CE for the Palm-size PC 1.2; and Windows Platform SDK for Pocket PC are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.