READ ME
Citrix ICA Client for IBM OS/2 Warp (ICA OS/2 Client)
Software Version: 6.0

Last update: Jan 31, 2001

(c) 2001 Citrix Systems, Inc.
-----------------------------------------------------------

Description
============
The ICA OS/2 Client supports the following platforms:

*  OS/2 Warp 3
*  OS/2 Warp 4

Important Note: We recommend upgrading your OS/2 installation with the latest OS/2 Warp FixPak (from IBM) before you install the ICA OS/2 Client. IBM continues to issue FixPaks that fix existing problems in OS/2 Warp platform/s. Upgrading to the latest FixPak may therefore resolve device specific problems that could cause unexpected behavior on the ICA OS/2 Client.


Where to Find Documentation
============================
This document contains late-breaking information about the ICA OS/2 Client software. 
For more information about the ICA OS/2 Client, refer to the Citrix ICA Client Administrator's Guide for the ICA OS/2 Client, available in an Adobe Portable Document Format (PDF) file (ICAOS2.PDF). Please note that for this release, the Administrator's Guide is available in English only.


The file is available on the Citrix Download Web site at 
http://www.citrix.com/download/.  

Use the Adobe Acrobat Reader or Exchange program to view PDF files.  You can download Acrobat Reader for free from Adobe's Web site at http://www.adobe.com.

You can also find documentation on the Web at http://www.citrix.com/support. On the Services Portfolio page click the Product Documentation tab, and choose ICA Clients.


System Requirements
====================
Computers used with the ICA OS/2 Client must meet the following requirements: 
* Standard PC architecture, 80486 processor or greater
* OS/2 Warp 3.0 (FixPak 32 or greater), or Warp 4.0 (FixPak 5 or greater)
* 8MB RAM or greater
* Mouse
* Keyboard
* VGA or higher resolution 
* 2MB free hard disk space 
* Connection to a Citrix server over TCP/IP transport 


Installation
=============
Download the installation package for the Citrix ICA OS/2 Client from the Citrix Download site.

1.  Copy the ICA OS/2 Client image (icaos2.exe) to a temporary directory (for instance, c:\temp) on the client machine.  The file is a self-extracting archive.

2.  Open an OS/2 command window, and change to the directory where the icaos2.exe file was saved:
	
	c:\>cd temp

3.  Extract the contents of the archive by running icaos2.exe:
	
	c:\temp>icaos2

Contents of the archive are extracted to c:\temp.

4.  To install the OS/2 Client, run install.exe:	

	c:\temp>install

The installation program will begin installing the ICA OS/2 Client. Follow the prompts until installation is complete.


Important Note: Transfer of TS CAL Licenses used by Win16 Clients to OS/2 Clients
==================================================================================

The ICA Win16 Client is designed to work on Microsoft platforms, and the ICA OS/2 Client is designed to work on IBM OS/2 Warp platforms.  There is a fundamental difference in the way the two clients are allocated TS CAL licenses from the Terminal Server.  As a consequence of this, you may have a situation where instead of re-using licenses that were used by Win16 clients, the server allocates new licenses to ICA OS/2 Clients.  The net result may be that extra licenses have to be allocated.

Customers who plan to replace their existing ICA Win16 installed base with the new ICA OS/2 Client need to plan ahead for the transfer of existing Terminal Services (TS) Client Access License (CAL) used by Win16 client devices to OS/2 client devices.

Microsoft Corp. makes provision for this transfer under the TS CAL End User License Agreement (EULA). 

Information describing the prescribed process for working with Microsoft to transfer the existing licenses is available on the Microsoft Support website at http://support.microsoft.com/support/kb/articles/Q248/4/30.asp.



Known Problems/Limitations (in this release):
==============================================

1.   Display problems experienced with GRADD drivers
------------------------------------------------------
At the time of this release, it has been ascertained that GRADD drivers exhibit major issues in terms of reliability and compatibility. However, this could change in future releases. IBM continues to encourage development of GRADD drivers and there will most likely be improvements in the future. 

Correct behavior has been recorded on some video chipsets, when the client desktop is set to 16bit and 24bit color depths. 

Note that SciTech Display Doctor drivers are GRADD based, and exhibit completely different effects depending on the video chipset on which they are installed. 

As an example, SciTech Display Doctor 7.04 drivers work correctly with a Matrox G400 card and the OS/2 client desktop set to 24-bit color depth.  In comparison, the same configuration shows major corruption (drawing and color corruption) when run at 256 colors. 

However, when non-GRADD Matrox 2.36 OS/2 drivers were used, there were no display problems in either video mode.


2. Failure auto-mapping two client printers defined for a single port
---------------------------------------------------------------------

If an OS/2 client machine has two client printers defined for the same port, one will be mapped automatically, and the other is ignored.

Currently, having multiple printers defined for a single printer port on the local OS/2 machine is not supported by the Citrix ICA OS/2 client.  We strongly recommend having only one printer, defined per port.


3. Some client printer names are not recognized correctly at the server
-------------------------------------------------------------------------

You may experience this problem if the client printer name contains international characters.

This issue is caused by the fact that, on OS/2 extended characters have been mapped to different character codes as compared to their Windows counterparts, even when the same codepage is used. Therefore, their representation will be different on the client and the server.

Please note that extended characters should not be used to exchange information between the client and server.  The solution is to ensure that client printer names do not contain extended characters.


4. Re-mapping an auto-created printer to a different LPT port on the client
----------------------------------------------------------------------------
If a printer which had been previously auto-created within a MetaFrame session is remapped to a different LPT port on the local OS/2 client machine, it may not work correctly when you logon the next time.  To workaround this problem, delete the printer completely on the client machine, and re-create it with a different name. 


5. Unable to cut and paste a Euro symbol from the server to a client
---------------------------------------------------------------------
The Euro symbol is an extended character. On OS/2, extended characters are mapped to different character codes as compared to their Windows counterparts, even when the same code page is used, therefore their representation is different on the two platforms. This is a basic difference in the implementation of the two operating systems.


6. Code page requirements for Euro symbol and other extended characters
-------------------------------------------------------------------------

If you are unable to generate the euro symbol on an OS/2 client, it may be that the code page being used is incorrect.  You should use code page 850 to enable generation of extended characters.

To set the code page on OS/2, open an OS/2 window and type the following command:

   c:\>chcp 850

To get the current system code page setting, type:
   
   c:\>chcp


7. Citrix server connections take longer than usual to time-out
-------------------------------------------------------------------
The "Connecting to ..." message remains on the screen and the Cancel button doesn't seem to work

This problem occurs only when an existing server (listed in the ICA browser) is currently not functioning. OS/2 sets a default timeout limit of 75 seconds for TCP/IP connections. This is a global setting that cannot be changed without affecting other applications running at the time.


8. Applications launched from Netscape are terminated when you quit Netscape
------------------------------------------------------------------------------

If you launch ICA sessions via the Netscape web browser, or using NFuse, and then close Netscape, all ICA sessions will be disconnected. 

This is due to the OS/2 specific implementation of Netscape, that is, all child processes (launched ICA connections, in this case) are terminated when the user exits the parent process (Netscape).


9. Problems upgrading Beta ICA OS/2 Client software to Version 6.0
--------------------------------------------------------------------

If you installed the Beta release of the ICA OS/2 client software on a client desktop, then you will experience problems upgrading to software Version 6.0.  

The solution is to uninstall the Beta version, using the original Beta distribution files, before installing the Release version. To remove the Beta version of the software:

a) Run the installer and proceed to the "Installation options" dialog.

b) Select the "Delete the installed product and re-install" option.

c) Proceed to the "Install" dialog and press the "Cancel" button.


Tips and Tricks
=================

1. Assigning a unique client name for an OS/2 box using the CLIENTNAME variable
--------------------------------------------------------------------------------
To manually assign a name to an ICA Client running on an OS/2 device, you can set the CLIENTNAME environment variable via the command prompt, or through an entry in the CONFIG.SYS file, on your OS/2 machine.

    c:\ set CLIENTNAME=YOUR_DESIRED_NAME
    

This setting might be required because on OS/2, the ICA client name is not derived from the client machine's host name (this is the name allocated to the device for use with TCP/IP transport).

The order of priority in which the ICA OS/2 Client determines what the client name should be is as follows:

 a) Gets the CLIENTNAME environment variable, if one has been set. 
	
 b) Checks the OS/2 LAN Services configuration for a machine name. 
 
 c) If the above methods fail, then a random name is generated.

Please note, unlike the Windows clients, the OS/2 client does not utilize the "wfcname.ini" file for client name determination.