Product
Support
Everything Else
TS1048: Helix Client (5.0-5.2) via TCP/IP configuration notes
Category

Configuration Note

Problem

Dynamic popup menus do not become active on an entry view.

Solution

A number of problems using Helix Client via TP/IP may be solved by adjusting the file "CLIENT_TCP_CONFIG" found in the same folder as your Helix Client application. Open the file with a text editor and change the lines listed below to the following values...

// CLIENT SEND BUFFERS (TASK TIME)
INITIAL_SMALL_DATA_BUFFERS : 5120
..
STASHED_SMALL_DATA_BUFFERS : 2048

Because you are increasing two internal buffers by a total of 6 MB, you will also need to increase the Client memory allocation by 6 MB. If memory is tight, you may be able to use smaller increments, but they must always be multiples of 1024.

Status

This bug has been fixed in Helix 5.3.

Update June 2004: In Classic Mode, Helix Client crashes when it attempts to read the CLIENT_TCP_CONFIG file. Helix Client 5.2.1 ignores that file. If you are running Helix Client 5.2.1 and encounter this situation, use these instructions (ResEdit required) to adjust these settings.

  • If you don't have a resource editor, click here first.
  • Download the ResEdit template.
  • Double click the template to open it (ResEdit automatically opens)
  • Select Open from ResEdit's File menu, and open your Helix Client
  • Open the CONF resource
  • Open the only line in the CONF resource. It is labelled ID #1
  • Find and change the two fields listed below to these values:
    INITIAL_SMALL_DATA_BUFFERS: 5120
    STASHED_SMALL_DATA_BUFFERS: 2048
    Do NOT change any other fields
  • Save and Quit ResEdit
History

This bug was introduced in Helix 5.0 and fixed in Helix 5.3.

This note is obsolete: Helix 6.0 and later do not use the CONF resource at all.

Scope

Helix Client