# Quick Beginnings

# Planning to Install Personal Communications

Personal Communications supports a wide range of workstations. There are hardware and software requirements, as well as memory and storage requirements, to consider when planning the installation of Personal Communications.

The following sections describe and list support for monitors, adapters, and keyboards.

For detailed instructions on installing Personal Communications, refer to CD-ROM Guide to Installation.

## Workstation Hardware

Personal Communications supports workstations with the following hardware:

Table 5. Workstation Hardware Support

System units | The recommended system unit has an Intel Pentium(R) microprocessor and access to a CD-ROM drive. A minimum of 125 MB of fixed drive space is required. Additional space might be required, depending on the installation options selected.
Display monitors | All VGA resolution or above display monitors supported by Windows.
Video adapters | All VGA resolution or above video adapters supported by Windows.
Keyboards |

- Enhanced keyboard (101-key, 102-key, 104-key) (Only the 101-key for Japanese)
- Space-saving keyboard
- Microsoft Natural keyboard
- 5576-001/002/003/A01/B01/B05 (Japanese)

Printers | All printers supported by Windows when a PDT file is not used. For more details about printers supported in PDT mode, refer to Emulator User's Reference.
Communication adapters | LAN, SDLC, coaxial, twinaxial, WAC, COM Port, OEM, and Multiprotocol communication adapters.
Modems | All asynchronous modems that use the Hayes AT(R) command set and are supported by Windows. Synchronous (SDLC) modems attached to a multiprotocol adapter (MPA), SDLC or WAC adapter.

### Workstation Memory Requirements

For Personal Communications the amount of memory you need depends on several factors, including the operating system you are running on, the attachment type, number of sessions, and the use of programming interfaces such as Emulator High-Level Language Application Programming Interface (EHLLAPI) and Dynamic Data Exchange (DDE).

Table 6. Recommended System Memory

Supported Operating System | Minimum | Recommended
--- | --- | ---
Windows 2000 Professional | 64 MB | 128 MB
Windows 2000 Advanced Server | 128 MB | 256 MB
Windows 2000 Server | 128 MB | 256 MB
Windows XP | 64 MB | 128 MB
Windows Server 2003 | 128 MB | 256 MB

## Workstation Software

Personal Communications is supported for the following operating systems and platforms:

- Windows 2000 (Professional, Server, and Advanced Server)
- Windows XP (Professional, Home Edition, and Tablet PC Edition)
- Windows Server 2003
- Windows Terminal Server Version 4 and Windows Terminal Services for 2000 and XP
- Citrix MetaFrame 1.8 for Windows Terminal Server 4.0 and Windows 2000 Server. (Citrix is a third-party application for specific Windows platforms.)
- Citrix MetaFrame XP Presentation Server (Versions s, a, e) for Windows
- IBM Communications Server for Windows V6.1 and V6.1.2 API Client
- Microsoft SNA Server Client
- IBM Communications Server for Linux V6.2 Client on Windows
- IBM Communications Server for Linux on zSeries V6.2 Client on Windows
- Microsoft XP

Personal Communications communicates with the following types of servers or gateways:

- IBM Communications Server for Windows V6.1 & V6.1.2
- Microsoft SNA Server V4 SP4
- Microsoft Host Integration 2000 Server V5

Host Requirements
Refer to Emulator User's Reference for information about software and hardware requirements for host systems. For all supported Windows operating systems, Java Runtime Environment 1.4.2 is installed.

### Windows x64 Platform Support

The x64-based versions of Microsoft Windows Server 2003 and Microsoft Windows XP Professional x64 Edition are optimized to run native 64-bit programs, but do not support 32-bit drivers or 16-bit applications.

For these platforms, Personal Communications does not install the following features and libraries.

- IBM SNA protocols
- DOS EHLLAPI
- 16-bit API support:
  - Standard EHLLAPI 16-bit interface
  - WinHLLAPI 16-bit interface
  - PCSAPI 16-bit interface
  - SRPI 16-bit interface
- Coax drivers

## Application Data

Application Data is generally defined to be files that contain user preferences or configuration information; an application may need some or all of these files to run properly. Personal Communications uses multiple configuration files: User Class files can be stored individually by user profile, while System Class files are stored in a common location.

Table 7 lists the classifications of some of the most common Personal Communications file extensions.

Table 7. Application Data File Types

User Class | System Class
--- | ---
Extension | File Type | Extension | File Type
.ws | Workstation Profile | .acg | SNA Configuration
.bch | Multiple Sessions | .mlg | Default Message Log
.ini | Session Size and Location | .trc | Unformatted Trace
.pmp | Popup Keypad Configuration | .tlg | Formatted Trace
.kmp | Keyboard Configuration |  |
.srl | File Transfer List |  |
.ndc | iSeries Connection Configuration |  |
.upr | iSeries, eServer i5, or System i5 User Profile |  |
.tto | iSeries Data Transfer Request (Receive) |  |
.tfr | iSeries Data Transfer Request (Send) |  |
.bar | Toolbar Setup |  |
.mac | Macro |  |
.mmp | Mouse Setup |  |
.xlt | Translation Table |  |
.xld | DBCS Translation Table |  |
.cert | Certificate |  |
.sth | Password Stash |  |
.adu | Automatic Dial Utility |  |
.kdb | Certificate Management Database |  |

### Application Data Locations

The location for Application Data is specified during installation of Personal Communications. The following tables list the default Application Data locations, based on operating system.

If the [UserProfile]\Application Data location was selected at installation, the following profile paths are used:

Operating System | User Class Directory (Current User) | System Class Directory
--- | --- | ---
Windows 2000, Server 2003, XP | C:\Documents and Settings\ %USERNAME%\Application Data\IBM\Personal Communications | C:\Documents and Settings\All Users\Application Data\IBM\ Personal Communications

If the All Users\Application Data location was selected at installation, the following profile paths are used:

Operating System | User Class Directory (Current User) | System Class Directory
--- | --- | ---
Windows 2000, Server 2003, XP | C:\Documents and Settings\All Users\Application Data\IBM\ Personal Communications | C:\Documents and Settings\All Users\Application Data\IBM\ Personal Communications

If the classic Private directory location was selected at installation, the following profile paths are used:

Operating System | User Class Directory (Current User)1,2 | System Class Directory
--- | --- | ---
Windows 2000, Server 2003, XP | C:\Program Files\IBM\Personal Communications\Private | C:\Program Files\IBM\Personal Communications\Private
1If the User Preference Manager (UPM) was set to a directory other than the default directory, Personal Communications will utilize that directory to store the user-class files. System-class files are always stored in the Private directory. 2For the classic Private directory locations, C:\Program Files\IBM\Personal Communications is the drive where Personal Communications is installed.

Note:
  For installations on Windows x64 platforms, the directory path `Program Files` is replaced by `Program Files (x86)`.

## Installation and Limitations of Personal Communications on ChineseStar and RichWin

This section describes how to install Personal Communications on ChineseStar (CStar) and RichWin, and the limitations of running Personal Communications on CStar and RichWin.

### Installing Personal Communications on ChineseStar and RichWin

Before installing Personal Communications, you must make sure that CStar or RichWin is installed and running on the English version of Windows. Once CStar or RichWin is installed and running, install Personal Communications by following the steps described in the CD-ROM Guide to Installation.

### Limitations of Personal Communications on ChineseStar and RichWin

Running Personal Communications on CStar and RichWin has the following limitations:

- Personal Communications supports only the GBK code page.
- RichWin does not support 3270 APL functions.
- CStar and RichWin support single Input Method Editor (IME) only.

  For example, if you open IME in multiple windows, IME behavior is synchronized in those windows. This is a platform limitation and it applies to Personal Communications as well.

- Although CStar and RichWin provide many true type fonts, Personal Communications supports only fixed pitch fonts.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]