Dell Wyse ThinOS Version 8.5 Hotfix INI Reference Guide

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:

   When you require string concatenation, you can use a backslash without a space before or after it to concatenate with the first set of characters from the previous line; for example the strings snow and ball may be concatenated to give snowball.

3. Blank Lines Make Files Easy to Read

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

4. 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.

5. Values with White Spaces Require Quotation Marks

   Values of parameters containing white spaces must be placed inside quotation marks. We recommend you use common-practice nesting rules.

6. Separate Lists by using Semicolons or Commas

   Use semicolons or commas for list separators.

7. {username}.ini Files must be Write-Enabled

   All {username}.ini files must be write-enabled to allow the thin client to place the encrypted user passwords in the files.

8. Use the wnos.ini File to Set the Maximum Number of Connection Entries Allowed

   The combined number of connection entries defined in a {username}.ini file and a wnos.ini cannot exceed a defined total maximum number of connections. The maximum number of connections has a default limit of 216, but can be set from 100 to 1000 using the wnos.ini file.

9. Use of the {username}.ini and {mac}.ini Parameters

   The {username}.ini and {mac}.ini parameters can appear in the wnos.ini file. However, these parameters must be below the include=$un.ini parameter or the include=<$mac.ini or {username}> parameter in the wnos.ini file. Although not required, We recommend that these parameters end with the parameter Exit=all.

   NOTE:

   No parameter should ever be executed twice. Some ThinOS hardware configuration parameters require a reboot to become active, and if the same parameters are defined more than once, the thin client may then go into an infinite reboot cycle.

   NOTE:

   We recommend you place the include=<$mac.ini or {username}> statement on the last line of the wnos.ini file to verify that all parameters are processed properly for terminal-specific settings.

10. Use of System Variables with Some Options of the Connect Parameter

    Some options of the Connect parameter can use the system variables shown in System Variables to map the string. All combinations of the variables are supported. For options that support use of system variables, see Connect Parameters Options.