<WARPIN>
and
</WARPIN>
tags
(similar to the <HTML> ... </HTML>
tags with "real" HTML files).
See the "Installation Scripts"
page for an overview where this tag should be placed.
The opening WARPIN
tag knows the following attributes:
VERSION="major.minor[.revision]"
"major.minor"
must have the major and minor
version codes for WarpIN
(e.g. "0.9"). Optionally, you can specify the revision level (the third
part of the WarpIN version number). If the third part is missing, "0" is
assumed.
If the VERSION
attribute is missing, "0.9.0" is assumed.
Note: Do not use release-level version numbers here (those with even
minor numbers), because this will cause your script to fail with developer's releases.
So instead of "1.0", use "0.9". Instead of "1.2", use "1.1".
OS="operating_system"
"operating_system"
can be one of the following:
Newer versions of OS/2 and eComStation report the following version strings:
CODEPAGE=codepage
If this is not specified, codepage 850 is assumed for the script, which is the one holding most international characters.
The effect of this attribute has slightly changed with V0.9.18. However, the change is backward-compatible. Since WarpIN now processes all character data internally as Unicode, the entire script is converted to Unicode anyway. As a result, this now simply specifies the source codepage for the Unicode translation. This finally allows scripts to be created that will run on any system.