Last updated:
Corrections have been made to the Everyplace
Client for Pocket PC 2002, Windows Mobile 2003, and Windows Mobile 2003 Second
Edition. This document describes those corrections and how to install and
configure the fix pack.
This Readme includes the following information:
This fix pack includes corrections for the
following problems found since Everyplace Client Version 5.0 for Pocket PC
2002, Windows Mobile 2003, and Windows Mobile 2003 Second Edition was released.
For Fix Pack 2
PQ96485 Device
generates assert exceptions and hangs if calendar has an overlapping
reoccurring entry
PQ97426
Cancel sync returns improper response and leads to client crash
PQ99199
SyncML client does not parse session ID URI correctly
PK00190
Device agent does not check registry key correctly
PK01507
Unique code for transportation industry customer
PK04672 NLS characters in header field cause
deletion of email to fail
PK05867 ID setup screen after installation of WM 2003 client has unlabeled edit box
PY00006 Package to support WM2003SE bootstrap installation
You can use the Device Management portlets to
deploy the software for your PPC2002, WM2003, and WM2003 Second Edition
devices.
Before you complete the steps in this section,
install WebSphereŽ Everyplace Access 5.0 Fixpack 2.
Complete the following steps on the Everyplace
Access Services server to complete the prerequisites for this release.
ˇ
Delete the Pocket PC
2003 and Pocket PC 2002 5.0.1.1 (or prior) Device Manager Server packages using
the WEA DMS Portlets. Because of a
change to Device Manager Server (DMS) for Windows Mobile 2003 Second Edition, a
refresh of the Device Agent is required for Pocket PC 2002 and Windows Mobile
2003.
ˇ
Upload the new 5.0.1.2
and 5.0.2.1 Device Manager Server packages to the WebSphere Everyplace Access
server using the WEA DMS Portlets.
o
The
WEA5012_ppc2002.zip package resides in the \CD\Client\PPC2002\dms\ directory
o
The
WEA5012_ppc2003.zip package resides in the \CD\Client\WM2003\dms\ directory
o
The
WEA5021_ppc2003.zip package resides in the \CD\Client\WM2003SE\dms\ directory
To install this fix pack:
To configure the Everyplace Client, start the
Everyplace Client and you will be prompted immediately for the necessary
configuration information.
After you have installed and configured the Everyplace
Client for Pocket PC 2002, Windows Mobile 2003, and Windows Mobile 2003 Second
Edition Fix Pack 2, you can verify the version by following these steps:
1.
Launch Everyplace
Client on your device by selecting Start->Programs->Everyplace Client.
2.
On the Welcome screen, tap About to display the build information.
Note: You
can also find the build information at the bottom of the My Settings panel.
Verify that the build
version is
2.1.
IBM Everyplace Client V5.0.1.2 – Build
200505240842 (for Pocket PC 2002)
2.2.
IBM Everyplace Client V5.0.1.2 – Build
200505240842 (for Windows Mobile
2003)
2.3.
IBM Everyplace Client V5.0.2.1 – Build
200505231539 (for Window
To uninstall Everyplace Client for Pocket PC 2002,
Windows Mobile 2003, and Windows Mobile 2003 Second Edition Fix Pack 2 follow
these steps:
To restore the Everyplace Client to the previous
version it will be necessary to reinstall the previous version using the instruction
in the Everyplace Client 5.0 User's Guide.
Only portrait mode is supported for Windows
Menu icons do not display in the Sametime client for Windows Mobility
2003, Second Edition
In previous versions of the client, icons appear on the command
bar and some of the associated menus and menu items. For example, when the
client is connecting to the Sametime server, a small, graphic symbol appears
next to the word connecting.... Similar graphics appear for the status
of the connection and for the status message selected by the user for others to
see. These icons do not display in this release of the Pocket PC client when
running on Windows Mobility 2003, Second Edition. Users should read the text
labels in the menus.
Invalid pop up message appears when the Everyplace Client starts
the WebSphere Everyplace Connection Manager connection
When the Everyplace Client starts the WebSphere Everyplace
Connection Manager connection, an invalid pop up message might appear. The
popup message requests the user to make a choice between some connection
alternatives. Users should NOT select any of the choices presented. Instead,
they should dismiss the pop up by either tapping on the Hide link or by
tapping elsewhere on the screen. Users can also
run the Connection Manager from the Start menu rather than from within the
Everyplace Client. The invalid popup message only appears when WebSphere
Everyplace Connection Manager is activated from within the Everyplace Client.
Extra,
vertical border appears on the Everyplace Client category screens
If users are
viewing the Home Page, the My Tools Page, or any page that they might have
created, an extra border appears along the left margin of the screen.
Everyplace Client Installer Incorrect Message
The Device Management Agent used for Windows Mobile 2003 Second Edition is the same as that used for Windows Mobile 2003. So when you use the WEA Portal to install the Everyplace Client, you may see the following message on a Windows Mobile 2003 device: “Everyplace Client V5.0.2.1 Base for WM2003SE”. Alternately, you may see the following message when installing on a Windows Mobile 2003 Second Edition device: “Everyplace Client V5.0.1.2 Base for WM2003”. In either case, the correct version will be installed to the device. This is only a documentation problem.
The following are trademarks or registered trademarks
of the IBM Corporation in the United States, other countries, or both:
Other company, product and service names may be
trademarks or service marks of others.
(c) Copyright International Business
Machines Corporation 1994, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.