Reference Guide

NOTE:

User prole parameters found in the {username}.ini le, generally override the identically named global parameters found in the

wnos.ini le, however, some global parameters do not allow this. For hierarchical precedence of one variable over another, refer to the

parameter descriptions in Table 7: Connection Settings: wnos.ini les, {username} INI, and $MAC INI Files can be used in a

{username}.ini le.

If both PNAgent/PNLite and a user prole are being used in the environment, the username must be dened 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 les follow currently accepted standard INI le formatting conventions. The INI les consist of Wyse parameters. If

you are using an INI le, the only parameter you must use is the Connect parameter, see Connect in Table 5: 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 les have the same meaning that is, a parameter named WyseXYZ in a wnos.ini le and

named WyseXYZ in a {username}.ini le 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 les:

1 Global Connect Parameters First

Global connect parameters should be listed before other connect parameters in a wnos.ini le.

2 Connect is the Only Required Parameter

As stated earlier, if you are using an INI le, the only parameter you must use is the Connect parameter. 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.

3 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 le

easier to read.

NOTE

When you require string concatenation, you can use a backslash without a space before or after it to concatenate with the rst

set of characters from the previous line; for example the strings snow and ball may be concatenated to give snowball.

4 Blank Lines Make Files Easy to Read

Using blank lines is recommended for making code easier to read.

5 Comment by using a # Sign

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.

6 Values with White Spaces Require Quotation Marks

Getting Started: Learning INI File Basics