Using opsi-wInst
Document Actions
The name "wInst" was created as an acronym for "windows installation (tool)". It has been kept whereas the software is now running in a linux environment, too.
wInst is a piece of Delphi software. Its linux counterpart is compiled with Kylix.
The program is called by the opsi-preLoginLoader service at every boot of a preLoginLoader managed PC. For other installation requirements or for test purposes it can be run independently. E.g., we take advantage of it for installing the preLoginLoader package beforehand.
Its main features are:
- It implements an installation script language for defining and controlling a completely unattended ("silent") setup process.
- wInst scripts are basically extended ini files so that they are easily read and edited.
- An installation script written in "wInst language" may therefore serve as a piece of human readable information on the planned steps of an installation process.
- All events (failures as well as successful executed commands) that occure while wInst is interpreting a script can be logged up to fine grades. The log data may be written to log files on a central server.
- Every basic step of a setup process - checking ressources, file copying, registry handling (on windows), configuring the start menu and the desktop - can be done by native wInst commands.
- It is also possible to include arbitrary calls to external installers (or other external programs). E.g. wInst may request the MS installer service to execute some msi file (which should be parametrized to proceed without user interaction). Or an AutoIt script may be used to call a setup program of some software package, and fill in the requested user responses automatically.
The following section comments on the real circumstances under which wInst proves to be a big help in building software distribution packages.
Additional information
The opsi-wInst program and the wInst script language are documented in the wInst manual.
