Specifications

Understanding WTOS INI Files 9
Figure 2 Network Setup dialog box
10.{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.
Note
For {username}.ini Files Only - If the Password parameter is present in the
{username}.ini file, it must be the first parameter in the file. The Password
parameter is created and updated by the thin client; it is not inserted by the
administrator. When the user selects the Change Password check box in
the Log-in dialog box, the user is prompted for a new password. The thin
client checks to ensure that both copies of the password are the same,
encrypts the password, places it at the beginning of the {username}.ini file
(replacing any previous password), and writes the file back to the file server.
If the user forgets the password, the administrator can edit the appropriate
INI file or delete the Password parameter, and then save the file. The next
time the user attempts to log in, no value should be entered in the Password
text box of the Log-in dialog box. Because the password is encrypted using
a one-way algorithm, the original password value cannot be recovered from
the INI file and a new password must be created.
11.Number of Connection Entries Allowed
The combined number of connection entries defined in a {username}.ini file and a
wnos.ini file 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.
12.Use of the {username}.ini and {mac}.ini Parameters
The {username}.ini and {mac}.ini parameters should only appear in the wnos.ini file.
These parameters must be below the include=$un.ini parameter or the
include=$mac.ini parameter in the wnos.ini file. Although not required, it is
recommended that these parameters end with an Exit=all parameter.
Caution
No parameter should ever be executed twice. Some WTOS 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.