Reference Guide

Option Value
$IP IP Address used.
$DN Sign-on domain name used.
$UN Sign-on name used.
$PW Sign-on password used.
$TN Terminal name.
$PLATFORM Model of the thin client.
NOTE: If Auto Login in enabled then $PW returns null, so with auto logins enabled do not use $PW as value for any
parameter.
Placing the INI Files into the Folder Structure on
the Server
You must need an FTP server to download your INI files and the path to download is specified in the INI page on the thin client. Under the
C:/ inetpub/ftproot folder for FTP or C:/inetpub/wwwroot folder for HTTP/HTTPS and place your INI files. Other necessary
files inside the structure as noted that this list describes the folder structure, starting with the root directory.
ThinLinux will set the default path as /wlx2 instead of traditional /wlx because some of the INI parameters are not compatible with old INI
parameters from the older Linux Clients. The default path to search is /wlx2 first, if /wlx2 directory is not found then you can search
for /wlx directory.
NOTE: There is no mixed path of /wlx2 and /wlx.
Table 2. INI files details
Parameters Description
/wyse/ The root directory. It stores the wlx2 folder and the addons folder
/wyse/wlx2 The main INI configuration folder. It stores the following:
• wlx.ini file or MAC.ini file
• bitmap folder
• certs folder
• ini folder
/wyse/wlx2/bitmap The folder where you can place custom images you plan to use.
/wyse/wlx2/certs The folder where you can place the CA certificates that can be
imported to a thin client.
NOTE: To import the certificates to the thin clients, use
the Certs and ImportCerts INI parameters.
/wyse/addons The folder where you can place the add-ons you want to use. It
also stores the directory file and the *.deb packages available to be
installed on the thin client. The directory file should list all available
add-ons. The directory file is required in the addons folder to
guarantee that add-ons are properly located.
Getting Started and Learning INI File Basics 7