Skip to main content
Kofax

Which registry keys does my LS1 need?

Summary

3551

Description

Here’s a short list of all the possible registry keys you can find in the Lanlink registry:

For a 32-bit system:
    HKLM \Software\TOPCALL\TCOSS\LINK\LAN<LanLinkNumber>

For a 64-bit system:
    HKLM\Software\Wow6432Node\TOPCALL\TCOSS\LINK\LAN<LanLinkNumber>

Some of these are standard (*) and will be created automatically while others are optional and have to be created manually.

See detailed explanations below.

Key name Key Type Default Value
AutoUpdate REG_DWORD 1
DSPNumber * REG_DWORD 0
EnableMemoryDump REG_DWORD 0
IptoConnect * REG_SZ  
MaxBootBandwidth REG_DWORD 0
Password * REG_SZ  
PorttoConnect * REG_DWORD 5000 (decimal)
Priority REG_DWORD 1
TxOptimization * REG_DWORD 1
Type REG_DWORD 2

List of standard/default registry keys:

  • DSPNumber: The used DSP module on the LS1. On an LS1v2 there’s only 1 DSP module so this key has to point to the first DSP which is “0”. On an LS1v1 up to 4 DSP modules are supported. Every single DSP requires its own LanLink. Supported values of this key are: “0”, “1”, “2”, “3”. (default: 0)
  • IPtoConnect: IPv4 address or ‘Host name’ of the LS1 (xxx.xxx.xxx.xxx). If a ‘host name’ is used, make sure this name can be resolved.
  • Password: An LS1 has a password to verify if the user has a right to connect to it. Type the password here. After the first run of TCOSS it will be encrypted. (no default)
  • PorttoConnect: IP Port of the LS1. It is not allowed to change this value. (default:0x1388 hex)
  • TxOptimization: Implemented since TCOSS 7.86.00 (KCS 8.2). Defines how TCOSS optimizes the transmission of data on the TCP/IP connection. 
    The following three values are supported:
    • “0”.... Use Nagle’s algorithm which tries to avoid small packets. Take care that this mode may cause additional transmission delays.
    • “1”.... (Default) Transmit the data without delay whenever the sending queue gets empty. This mode provides the same performance as mode 2 but avoids series of small network packets.
    • “2”.... Transmit all data packets without delay. (standard way of sending before KCS8.2)

List of optional registry keys:

Your system should function without the presence of these keys.

Only create the following keys if you were instructed to do so by your next level of support!

  • AutoUpdate: If not zero, the program files on the LS1 are automatically kept up-to-date. This registry is reserved for development purposes and should not be changed. (default:1)
  • EnableMemoryDump: Reserved for development purposes and should not be changed. For correct use of this key please look in the current “Line Server Manual” 
    The following values are supported:
    • “0”.... (Default) Memory Dump is disabled
    • “1”.... Memory Dump is always created when booting the LS1, even after a TCOSS restart or if the Dump is corrupted.
    • Other.... Memory Dump is created if the LS1 reboot was not caused by a TCOSS restart, the Dump is not corrupted and the minimum active time of DSP in seconds exceeds this value.
  • MaxBootBandwidth: Defines the maximum bandwidth in bytes per second that is used for loading the program code to the LS1. If set to 0 the bandwidth is unlimited. If the bandwidth limit is used, the entered value must be between 100 (100 Bytes/s) and 1000000 (1 Mbyte/s).
  • Priority: Priority level to connect to the LS1. Set to 2 for primary server of a Tandem System. An LS1 always accepts a connection attempt with a higher priority than the current connection. A priority of “1” is lower than “2”, “3”... Only the first connection attempt with the same priority will be accepted. Set to “1” for secondary server and single server. Set to “2” for primary server of Tandem System. (default: 1)
  • Type: Type of link. (default: 2 for LANLinks)

Applies to

  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2008
  • TC/SP 7.80.04 – Current (Article based on TC/SP 7.86.00)
  • LS1v1, LS1v2

Keywords: KCS, communication server, kofax, topcallLineserver, line, server, LS1, LSone, oneDSP,

  • Was this article helpful?