The transfer protocols are the same as the ones for updating the firmware, e.g. HTTP and HTTPS. An INF
file which in turn references a tar archive zipped using bzip2 must be referenced as the target.
The structure of the INF file is as follows:
[INFO], [PART]
| Header information |
file="test.tar.bz2"
| File name of the compressed tar archive |
version="1"
| Version number - a higher version results in an update if Update automatically is enabled. |
The files to be transferred must therefore be zipped in a tar archive which is then compressed using bzip2. This file is referenced in the INF file which is the target of the URL.
The tar archive can be created under Windows, e.g. with the open source program 7-Zip (www.7-zip.de). This program also allows bzip2
compression. Under Linux, tar and bz2 files can be created using onboard resources.
The procedure makes it possible to replace the file(s) on the server with a new version which the thin client loads the next time it is booted. The Version
parameter in the INF
file must be increased for this purpose.