Specifications

2 Understanding WTOS INI Files
This chapter contains the basic information you need to help you understand and use the
WTOS INI files. It contains information on the different WTOS INI files you can use and the
rules and recommendations for constructing the files. In addition, this chapter contains
information on WTOS sample INI files that you can download and modify to quickly get
your file server up and running for your thin client environment.
After you become familiar with the WTOS INI files, you can refer to the parameter details
you need in the following sections of this guide:
• "Parameters for wnos.ini Files Only"
• "Parameters for wnos.ini Files and {username}.ini Files"
• "Parameters for ICA and RDP Connections"
About WTOS INI Files
The WTOS INI files contain the parameters and associated values necessary for the
various functionality you want. You can construct the following INI files for use with thin
clients running WTOS:
• wnos.ini file (see "Working with wnos.ini Files")
• {username}.ini file (see "Working with {username}.ini Files")
Working with wnos.ini Files
A wnos.ini file contains the “global” parameters you want that will affect all thin clients
accessing the file server. Parameters in both Table 2, "Parameters for wnos.ini files only,"
and Table 3, "Parameters for wnos.ini files and {username}.ini files," can be used in a
wnos.ini file.
Note
Parameters in Table 2 can only be used in a wnos.ini file; they cannot be
used in a {username}.ini file.
Working with {username}.ini Files
A {username}.ini file contains the user-specific or “user profile” parameters you want that
will comprise the connection profile for an individual user. These parameters will affect
only the user you specify. Parameters in Table 3, "Parameters for wnos.ini files and
{username}.ini files," can be used in a {username}.ini file.
Note
“User profile” parameters (found in the {username}.ini file) generally override
the identically named “global” parameters (found in the wnos.ini file),
however, some “global” parameters do not allow this (for hierarchical