Reference Guide

NOTE: Parameters in Connection Settings: wnos.ini files only can only be used in a wnos.ini file; they cannot be used in
a {username}.ini file.
Working with $MAC.ini Files
A $MAC.ini file can be used for device-specific configurations. If the thin client locates a wnos.ini file, then the wnos.ini file is processed
and if the Include=$MAC.ini statement is included, then the $MAC.ini file is processed. The $MAC.ini file is stored in the same directory as
a wnos.ini file if you are not using a WNOS.INI file, otherwise the files should be stored in the INC directory.
NOTE: The placement of the include=$MAC.ini parameter within the wnos.ini file will dictate which value will take
priority for a same specific parameter that is contained in both the wnos.ini file and the $MAC.ini file but is defined
differently, that is different values for the same parameter.
For example, if the wnos.ini file has parameterA=valueRED, and the $MAC.ini file has parameterA=valueBLUE, then:
• If the parameter include=$MAC.ini is added in the wnos.ini file before the parameterA=valueBLUE statement, then
parameterA=valueRED is discarded and parameterA=valueBLUE is used.
• If the parameter include=$MAC.ini is included in the wnos.ini file after the parameterA=valueBLUE statement, then the
parameterA=valueBLUE is discarded and parameterA=valueRED is used.
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
General Settings for wnos.ini Files, {username} INI,
and $MAC INI Files.
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 precedence of one
variable over another, refer to the parameter descriptions in Connection Settings: wnos.ini files, {username} INI, and
$MAC INI Files can be used in a {username}.ini file.
If both PNAgent/PNLite and a user profile are being used in the environment, the username must be defined in the
Windows domain, and the password used must be the same for both the Windows domain and the user.
Rules and recommendations for constructing the
INI files
In general, ThinOS INI files follow currently accepted standard INI file formatting conventions. The INI files consist of Wyse parameters. If
you are using an INI file, the only parameter you must use is the Connect parameter, see Connect in General Settings for wnos.ini Files,
{username} INI, and $MAC INI Files. Any of the rest of the parameters can be used if you desire, but are not necessary unless you want
changes from client and other defaults, for example, other can be the default resolution of your monitor.
Every parameter (and their options) has a name and a value, with the name appearing to the left of the equals sign (name=value). All
parameters with the same name in the various INI files have the same meaning that is, a parameter named WyseXYZ in a wnos.ini file and
named WyseXYZ in a {username}.ini file will have the same meaning.
Number signs (#) indicate the start of a comment. Comments can begin anywhere on a line. Everything between the # and the End of
Line is ignored. Along with these general formatting conventions, use the following guidelines when constructing the INI files:
1. Global Connect Parameters First
Global connect parameters should be listed before other connect parameters in a wnos.ini file.
2. Continue Lines by using a Space and Backslash
Placing a space and backslash ( \) at the end of a line indicates line continuation; that is, the backslash means that the line and the
following line are, for the purposes of reading code, the same line. No white space can appear after the backslash; the requirement of
white space between parameter entries is maintained by the use of the space before the backslash. In addition, starting all parameters
at the left margin and placing at least one leading space or tab at the beginning of all (and only) continuation lines makes an INI file
easier to read.
NOTE:
6 Getting Started: Learning INI File Basics