ThinPrint Clients

Installing

• Unpack the archive file thnuclnt-7.0.xy-linux.tar.gz and copy its contents into a local directory of the Linux computer.
• Open the Terminal application and change to this directory.
• Start the installer as root with:

./setup.sh (top arrow in Illus)

Installing ThinPrint Client

The installer setup.sh automatically identifies the processor architecture (bottom arrow) as well as the Linux distribution and then installs the software compilation that fits best.

Starting

• Copy the config file thnuclnt.conf from the software’s download ZIP from Con­fig Files\tcpip or create a new one.
• Move this file to the (hidden) subdirectory .thnuclnt (of the user’s home direc­tory) – i.e., to ~/.thnuclnt.

Config file thnuclnt.conf in the directory ~/.thnuclnt

This file should have the following content:

# BEGIN SYSTEM CONFIG autoupdate = 15 automap = true autoid = 0 updatecount = 1 editcount = 1 connector tcpip { protocol = listen interface = 0.0.0.0 setdefault = true } # END SYSTEM CONFIG

For more on this, see the Parameters section.

Contents of config file thnuclnt.conf for TCP/IP (example)

• The users start the ThinPrint Client with:
  thnuclnt

Starting ThinPrint Client as an application

The printers created in CUPS will be mapped automatically into a Remote Desktop session if a ThinPrint Engine is installed on the machine on which the session is running.
(The printer mapping is done by AutoConnect, which is a part of ThinPrint Engine.)

CUPS printers mapped into the Remote Desktop session

The printer list of the ThinPrint Client can also be retrieved using AutoConnect or the Management Services.