Welcome to Mobility Client Version 5.1.0.2 for Windows(R) and Windows CE, a component of IBM(R) WebSphere(R) Everyplace(R) Connection Manager This README file contains information you need for installing and running the Mobility Client. It also contains information that was not available for our publications. ___________________________________________________________________________ Table of contents 1.0 Software requirements 2.0 Hardware requirements 3.0 Getting help 4.0 Installing from CD 5.0 Installing from diskettes 6.0 New features 7.0 Product information 8.0 Fixed Authorized Problem Analysis Reports (APARs) 9.0 Late-breaking information 10.0 Trademarks and Copyright ___________________________________________________________________________ 1.0 Software requirements One of the following operating systems is required: - Microsoft(R) Windows 2000 - Microsoft Windows XP - Microsoft Pocket PC 2002 - Microsoft Windows Mobile 2003 - Microsoft Windows Mobile 2003 Second Edition - Microsoft Windows CE .NET 4.2 Also required is Microsoft ActiveSync Version 3.1 or later (for Mobility Client for Windows CE only) ___________________________________________________________________________ 2.0 Hardware requirements The Mobility Client for Windows CE provides support for the following devices: Pocket PC 2002, Windows Mobiles 2003-based Pocket PC, Windows Mobile 2003 Second Edition, and selected Windows CE .NET 4.2 devices. ___________________________________________________________________________ 3.0 Getting help Online help is available in the Mobility Client product. See the IBM WebSphere Everyplace Mobility Client User's Guide for more information about the types of help that are available and instructions on how to access help. The guide is in portable document format (PDF) and you will need Adobe Acrobat Reader Version 5.0 or greater to display or print it. This guide is located on the web at http://publib.boulder.ibm.com/pvc/wecm/51/ ___________________________________________________________________________ 4.0 Installing from CD If your workstation has a CD drive, you can install the Mobility Client on Windows and Windows CE directly from CD. Follow the instructions in "Installing and configuring the Mobility Client" in the WebSphere Everyplace Mobility Client for Windows User's Guide to install from CD. For instructions on downloading the Mobility Client code for all platforms, see "Applying Maintenance" in the WebSphere Everyplace Mobility Client for Windows User's Guide. ___________________________________________________________________________ 5.0 Installing from diskettes From any workstation that has a CD drive, you can create diskettes of the Mobility Client for Windows to install on a client system. You will need three high-density, formatted diskettes. Use a utility that can split a large file into smaller files that fit onto multiple diskettes, such as the IBM-created utility CHOPPER. Follow the instructions for CHOPPER at http://www.pc.ibm.com/qtechinfo/DSHY-44QSCB.html These diskettes can then be taken to a target system and using the same CHOPPER utility, recombined into the original single file. When CHOPPER splits a file into smaller files, it will copy itself onto the first diskette as UNCHOP.EXE. The filename_to_be_transferred is the package-for- the-web file in the Win32 or WinCE directories on the installation CD. To install Mobility Client from diskettes: Recombine the single package file onto the client system or a desktop system, then click Start --> Run and specify the package file to extract the files and install the Mobility Client. __________________________________________________________________________ 6.0 New features for version 5.1 -- Added support for Windows Mobile 2003 Second Edition -- Removed support for Microsoft Windows 98, Windows Me, Windows NT(R), and Handheld Pocket PC -- The Mobility Client can be configured to check that certain programs are running, like antivirus or personal firewall software, before allowing the connection to start. -- The Mobility Client can be configured to automatically start one or more programs after the initial connection successfully completes. -- Mobility Client configuration files can be exported and imported which gives an administrator the ability to set or change Mobility Client options, and then distribute the new configuration to the client. The user imports the new configuration and accepts the changes. -- An aid in problem determination, the Mobility Client trace viewer is a facility the user can use for first failure data capture, especially useful during a connection attempt. -- Removed support for wireless transport layer security (WTLS) encryption. -- The Mobility Client now receives most network tuning parameters from the Connection Manager at connect time which eliminates configuration tasks on the Mobility Client. The client transmits characteristics of the connection to the Connection Manager so the configuration data is appropriate for the type of connection being used. -- The Mobility Client automatically adjusts network and IP stack maximum transmission unit (MTU) sizes based on the type of IP interface used to communicate to the Connection Manager. -- The Mobility Client automatically adjusts the network MTU size to avoid network black holes. 6.1 New feature for version 5.1.0.1 -- Added support for limiting the Mobility Clients that are permitted to log on to the Connection Manager by device class. This capability is a security feature of the connection profile that is assigned to the mobile network connection (MNC) to which the client logs in. 6.2 New feature for version 5.1.0.2 -- Added support for the Mobility Clients on the CE .NET operating system using Psion 7535 devices. Do not install the Mobility Client for Windows CE .NET on the same desktop machine that has the Mobility Client for PocketPC 5.1.0.1 or earlier installed. Upgrade the Mobility Client for PocketPC to 5.1.0.2 or later. Otherwise, the PocketPC version may be incorrectly installed to your .NET device when you run ActiveSync. By default the Mobility Client for Windows CE .NET is installed into a folder on the device named \Program Files\Mobility Client. If you elect to install into a folder other than this default the Windows CE Installer will select a destination folder named "IBM Mobility Client for .NET". The installer may fail to create this directory resulting in a hang during the install process. To ensure the install completes successfully change the destination program folder to "Mobility Client" when installing into a folder other than the default. To install the Mobility Client on a CE .NET device: First, attach a supported Windows CE .NET device to a desktop computer running Windows 2000 or Windows XP and initiate an Active Sync connection. On the desktop computer: 1. Download and save the WC5102CEDotNET.exe file from the Support web site. 2. Click Start -> Run, then enter: WC5102CEDotNET.EXE. 3. Follow the setup wizard through the installation process. Choose the components to install when you are prompted to "Select Components". 4. After the installation completes and if the target device is connected via ActiveSync you are prompted to install the Mobility Client. The base package is installed. 5. Note that additional language, network, and encryption support files are not automatically installed with the base package. Return to ActiveSync and tap Tools -> Add/Remove Programs to install additional support files. Install additional support files individually. Selecting multiple files from the Add/Remove Programs list causes the device to stop responding. Make sure when you select the additional support files that you choose the ones labelled "for .NET". 5. After the application downloading is complete, click OK, then click Finish to complete setup. 6. Check the device to see if any further steps are necessary. On the Windows CE device: If you chose to install the Mobility Client in a directory other than the default, select that destination and click OK. The installation files are copied from the desktop computer and installed onto the CE .NET device. For each package there are three cab files that are installed as part of the setup wizard process, one for each processor: StrongARM (ARM), XScale Thumb (ARMV4I), and X86 (X86). Base - Core program with IP-based network support wecm.NETARM.CAB wecm.NETARMV4I.CAB wecm.NETX86.CAB Brazilian Portuguese language support wecm_bp.NETARM.CAB wecm_bp.NETARMV4I.CAB wecm_bp.NETX86.CAB Dataradio network support wecm_dataradio.NETARM.CAB wecm_dataradio.NETARMV4I.CAB wecm_dataradio.NETX86.CAB DataTAC network support wecm_datatac.NETARM.CAB wecm_datatac.NETARMV4I.CAB wecm_datatac.NETX86.CAB German language support wecm_de.NETARM.CAB wecm_de.NETARMV4I.CAB wecm_de.NETX86.CAB Dial network support wecm_dial.NETARM.CAB wecm_dial.NETARMV4I.CAB wecm_dial.NETX86.CAB Spanish language support wecm_es.NETARM.CAB wecm_es.NETARMV4I.CAB wecm_es.NETX86.CAB FIPS encryption support wecm_fips.NETARM.CAB wecm_fips.NETARMV4I.CAB wecm_fips.NETX86.CAB French language support wecm_fr.NETARM.CAB wecm_fr.NETARMV4I.CAB wecm_fr.NETX86.CAB Italian language support wecm_it.NETARM.CAB wecm_it.NETARMV4I.CAB wecm_it.NETX86.CAB Japanese language support wecm_jp.NETARM.CAB wecm_jp.NETARMV4I.CAB wecm_jp.NETX86.CAB Korean language support wecm_kr.NETARM.CAB wecm_kr.NETARMV4I.CAB wecm_kr.NETX86.CAB Mobitex network support wecm_mobitex.NETARM.CAB wecm_mobitex.NETARMV4I.CAB wecm_mobitex.NETX86.CAB Norcom network support wecm_norcom.NETARM.CAB wecm_norcom.NETARMV4I.CAB wecm_norcom.NETX86.CAB Simplified Chinese language support wecm_sc.NETARM.CAB wecm_sc.NETARMV4I.CAB wecm_sc.NETX86.CAB Traditional Chinese language support wecm_tc.NETARM.CAB wecm_tc.NETARMV4I.CAB wecm_tc.NETX86.CAB __________________________________________________________________________ 7.0 Product information Windows Platforms ----------------- -- If you are installing a modem driver for the first time on Windows 2000 or Windows XP, you may be prompted to enter a country code and area code for your computer. This is normal, even if the modem is a wireless modem that does not make use of this information. Enter the information when prompted. -- When installing the Mobility Client on Windows XP, an "IKernel.exe - Application Error" might be encountered. This error is associated with InstallShield's kernel engine. Try re-installing the Mobility Client. If the error persists, refer to InstallShield's Consumer Central web-site: http://consumer.installshield.com/kb.asp?id=Q108190 for further instructions. The Document ID associated with this problem is Q108190. -- When upgrading from a version prior to 2.1.1.11, you must stop the client prior to upgrading. If you do not, you may leave the client in a corrupted state. Should this happen, contact IBM support for recovery directions. Windows CE Platforms -------------------- -- If you are using any of the Socket Communications Serial I/O Cards (Serial I/O, Dual Serial I/O) on Windows CE to connect to a Mobitex, DataTAC, or Dataradio serial modem, the Mobility Client cannot accurately detect when the modem is not responding or is disconnected because the I/O card does not always report write failures. As a result, the client may display timeout error messages, but might not shut down as it would normally do when unable to write to a modem. -- If you are using the built-in serial port on a Windows CE device to connect to a modem, be sure to choose the modem named "Hayes Compatible on COM1:" when setting up your Mobility Client connection. Do not choose "Serial Cable on COM1:" since the Mobility Client will not work in this case. Also, be aware that when using the built-in serial port, you will need to use a NULL modem adapter or cable to connect to your external modem. _________________________________________________________________________ 8.0 Fixed Authorized Problem Analysis Reports (APARs) Problems resolved with version 5.1.0.1: IY63649 eMsg_Shutdown not always sent to API clients IY63883 Reqesting Motorola PMR modem status during initialization leads to ab end IY64191 Some messages are being displayed even when they are not in ARTPOPUP.TXT Problems resolved with version 5.1.0.2: IY59204 When 5.1.0.1 Client connects to 5.1.0.0 Gateway, secondary auth may abend IY65254 Context help not displayed for the Japanese Mobility Client IY65633 When WiFi is set at a lower priority than GPRS, GPRS suspends IY65644 Default route is not restored after Mobility Client disconnects IY66034 Mobility does not recognize RF MODEM902M IY66338 Mobility Client not using proper interface for logins. IY66121 Buffer overrun while roaming using Mobility Client IY67098 Client does not properly reset an interface that has been excluded, then included, in the roaming GUI _______________________________________________________________________ 9.0 Late-breaking information 9.1 The Sierra Wireless AirCard 555 for Verizon creates two network connections on a Pocket PC: "-Express Network" is a connection which should be able to be driven by the Mobility Client as well as Pocket IE. However, neither application is able to use this connection. The second connection called "Sierra Aircard" is an NDIS interface. This connection can only be connected using the Sierra Wireless Watcher program. Therefore, when using the Mobility Client for Pocket PC with the Aircard 555, specify either "Sierra Aircard" or "Default Local IP Interface" when you define your connection and use the Sierra Wireless Watcher program to start and stop the 1xRTT connection. 9.2 For the Intermec WiFi adapter and the Symbol WiFi adapter, the Mobility Client installs two status DLL files in the installation directory which enables client roaming when using these interfaces on Pocket PC 2002 and Windows Mobile 2003. Because the files are hidden, view them from File Explorer by tapping and holding in a blank part of the window until a message displays to view all files. The files are named IntermecWiFiStatus.dll and Symbol8056WiFiStatus.dll. The Mobility Client can have knowledge of network connectivity events for these adapters because the DLL can retrieve modem-specific information and pass it to the Mobility Client. For example, the Mobility Client can be aware when a given network is no longer available. Edit the artour.ini file and in the Interface section associated with your adapter, set StatusDLL=dllname.dll, where dllname is one of the two files in the installation directory. 9.3 On the Siemens SX56 PocketPC 2002 device you must disable the AT&T Wireless Tools optimizations in order for the Mobility Client to automatically connect to the GPRS network. Click Start -> Wireless Tools -> Optimization Settings and clear the Use Optimization box. 9.4 On the Psion 7535 CE .NET device, clicking the question mark (?) in the title bar of a dialog box, then clicking an item in the the dialog box does not display the What's This help for the item. Instead, the browser displays the top of the Help topics file. ________________________________________________________________________ 10.0 Trademarks and Copyright Everyplace, IBM, and WebSphere, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. Copyright International Business Machines and others, 1994, 2005. All rights reserved.