Q-100.305
Tips regarding Remote TLDs under NetWare


Frage
Problem What should be done during the installation of Remote TLDs, in case not only the faxfunctionality is going to be used?
Produkt TLD (allgemein)
Priorität normal
Effekt normal
Datum 7.03.2005

Antwort
Suppose a system-environment with two NetWare Server, both with Volume SYS:

Requirements for faxfunctionality:

On the remote server the following directories and files must be created:

  • »SYS:DAVID\TLD\CODE\CAPI\TLD.NLM«
  • »SYS:SYSTEM\DAVIDLIB.NLM«
  • »SYS:SYSTEM\TOBITLIB.NLM«
  • »SYS:SYSTEM\TGRAPHIC.NLM«
  • »SYS:DAVID\CODE«
The »DAVID\CODE« directory can be empty, but must exist otherwise the following error message will appear:TLD.NLM: TLD.INI could not be read
The Transport Layer Driver initialization file (TLD.INI) for this port
is not located in the specific port directory (\DAVID\TLD\PORT\001).
Please check the port configuration or run \DAVID\INSTALL\INSTALL.EXE
to reconfigure the port.

Requirements - Voice Functionality (T2S)
For Text2Speech (T2S) the following directories and files must be available on the remote-server:

  • »SYS:DAVID\CODE\TAUDIO\TAUDIO.NLM«
  • »SYS:DAVID\CODE\DAVID.DAT«
Configuration example:
Two NetWare Server, David has been installed on Volume DATA. Additional to procedure for fax-functionality in the first part, should a file called DAVIDLIB.INI be created in the »\DAVID\SYSTEM« directory on the Remote Server. The DAVIDLIB.INI should contain the following entry "volume=data".

In case an error message "Wrong DCC file... Only Fax TX/RX" appears after start of the TLD, this can only be solved by creating the same volume on the Remote Server as on the DvISE Server. On the volume the following directories should be created:

  • »DATA:DAVID\CODE\DAVID.DAT« in order to get the TLD running
  • »DATA:DAVID\TLD\CODE\TAUDIO\TAUDIO.NLM« for T2S functionality