Administrator Guide

Parameter Description
102 — Enable upgrade only, but have a popup message that identies the
rmware version, and then prompts with OK and Cancel buttons
appearing before the process; completion message appears after process.
201 — Enable a forced rmware upgrade/downgrade process, but have a
popup message with OK button appearing before process although
process will begin in 20 seconds in any case; completion message appears
after process.
202 — Enable a comparison/non-forced upgrade only process, but have
a popup message with OK and Cancel buttons appearing before the
process; completion message appears after process.
The option LoadPkg species how to update the external packages. If set
to 0, this disables checking for packages. If set to 1 it enable packages
upgrade/downgrade process, and if set to 2, it enables upgrade only. If
LoadPkg is not in the statement, it will inherit the value of AutoLoad.
For example, if the value is 0, and if AutoLoad=0, 1, and if AutoLoad=1, 101
or 201, and 2 if AutoLoad=2, 102 or 202.For example, if you set
AutoLoad=1 LoadPkg=0, the rmware is checked, but the packages are
not checked. From ThinOS Lite 2.3, the external packages update
mechanism is changed. Some packages are default, and loaded according
to value of LoadPkg. For example RTME. Some packages need additional
parameter AddPkg to add. For example, FR and TCX.The option AddPkg
is for adding packages. It depends on the value of LoadPkg.
The packages check comes after rmware check.The option DelPkg is for
deleting packages. It does not depend on the value of LoadPkg. The
packages specied in DelPkg are always deleted when loading the ini
le.The value of AddPkg and DelPkg is one package name or a package
name list. For example, AutoLoad=1 AddPkg="FR, TCX" DelPkg=RTME.
NOTE
: The AddPkg and DelPkg options depend on platforms
which supports external packages. So far only Z/D and U class
support it. The other legacy platforms does not support it.
The option VerifySignature species to verify the signature or not when
updating the rmware and/or packages. It is introduced in ThinOS Lite 2.4
and above versions to make sure the security and integrity of the
rmware and packages. If you set VerifySignature to no, it will not check
the signature so that theo that the downgrade of the rmware and/or
packages can happen which did not support signature. The default value
is yes.
The option UpgradeOrder is a control mechanism to enable BIOS and
rmware upgrade in a specic order. If parameter is set to no, the default
order is set to upgrade ThinOS rmware rst, and then the BIOS. For the
parameter UpgradeOrder you can set a single entity to upgrade or a list in
order, (support value—bios and wtos)
Example:
AutoLoad=1 UpgradeOrder=bios Upgrades only the BIOS
AutoLoad=1 UpgradeOrder=bios,wtos Upgrades BIOS rst, then the
ThinOS rmware
AutoLoad=1 UpgradeOrder=wtos,bios Upgrades ThinOS rmware rst,
then the BIOS
AutoLoad=1 UpgradeOrder=wtos Upgrades only the ThinOS rmware.
AutoSelectSingleCert={yes, no}
Yes/no option to select the single client certicate available.
Creating and Using xen.ini Files 179