Dell Wyse 3020 Wyse ThinOS Version 8.5 INI Reference Guide - Page 9

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

Get Dell Wyse 3020 PDF manuals and user guides View all Dell Wyse 3020 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

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 Connect is the Only Required Parameter As stated earlier, if you are using an INI file, 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 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. 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 Values of parameters containing white spaces must be placed inside quotation marks. We recommend you use common-practice nesting rules. 7 Separate Lists by using Semicolons or Commas Use semicolons or commas for list separators. 8 {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. 9 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. 10 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= parameter in the wnos.ini file. Although not required, We recommend that these parameters end with the parameter Exit=all. Getting Started: Learning INI File Basics 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
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
Connect is the Only Required Parameter
As stated earlier, if you are using an INI
file,
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
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.
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
Values of parameters containing white spaces must be placed inside quotation marks. We recommend you use common-practice
nesting rules.
7
Separate Lists by using Semicolons or Commas
Use semicolons or commas for list separators.
8
{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.
9
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.
10
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.
Getting Started: Learning INI File Basics
9