Specifications

22 Chapter 3
client; the ICA client is fully contained in the thin client system and can only
be updated by changing that entire system. The RDP client is also not
replaceable.
Caution
Interrupting power during the update process can corrupt the FLASH on the
thin client. Thin clients with corrupted FLASH must be shipped to Wyse for
service.
Understanding the Software Update Processes
After a thin client has booted from the image stored locally in flash memory and has made
its anonymous connection to your file server, the following processes occur for the default
AutoLoad value = 1, cases where no wnos.ini file is found, and cases where a wnos.ini
file is found which does not contain the keyword.
Note
All thin client units using a particular file server are identically updated. There
is no distinction between thin clients in this regard. If Autoload is enabled
(value = 1 or 2), an update cannot be prevented from occurring. The software
update process is governed by the AutoLoad value as follows.
AutoLoad value = zero - no update checking is done; the version (image/
software) is never updated.
AutoLoad value = 2 - the software update process identifies code which is
newer than the one which is installed on the thin client. The code identifier is
split into 4 parts, the major release identifier, the minor release identifier, the
build number identifier, and the sub-build number identifier (if the sub-build
number is 0, it will not be displayed). Each part is compared against the
current code internal identifier in the same format. If the file identifier is
greater, the update is performed. If the file identifier is less, the update is
abandoned. If the file identifier is equal, the next term is examined until the
build identifiers are found to be equal and the update is abandoned. This
comparison process using the build number can be important in cases where
you are using a beta release, or in cases where you need to reinstall a
release with the same major and minor numbers but with an updated build.
Model SX0, Product S10:
1. If called for, the thin client first searches in the wnos directory for RCA_wnos. If this file
exists with a different internally encoded version number than the image currently in
flash memory, and depending on the wnos.ini file AutoLoad setting (the default
AutoLoad value is 1), the thin client will load this image into flash and reboot.
2. The thin client will then (regardless of any circumstance in step 1) check for a file
named xperess.rom and again updates if appropriate. If an update is done, the thin
client will again reboot.