Each archive should contain exactly one installation script. If it does not, WarpIN will complain when it is started with this archive as a parameter.

An installation script is a plain text file in an HTML-like syntax which describes the archive (and the packages therein). When WarpIN is started with an archive as a parameter, it first reads the script from the archive to find out more about the archive. What is displayed in the WarpIN dialogs depends on this script.

The script allows you to specify the package titles, dependencies between the packages, packages that are required to be installed already, version information, de-install information, CONFIG.SYS changes, WPS classes to be registered and so forth.

Installation scripts use an HTML-like syntax. Note that this applies only to the syntax, not the semantics. WarpIN does not use many "real" HTML tags, just the overall style with the angle brackets to indicate tags.

The whole script must be enclosed in <WARPIN> ... </WARPIN> tags.

Within these tags, there is a <HEAD> ... </HEAD> block (which declares the packages in the archive) and a <BODY> ... </BODY> block, which describes the pages to be displayed to the user.

Here's an overview with links to the tags reference information:

<WARPIN VERSION="1.0">
  <HEAD>
    <PCK INDEX=... TARGET=... >Package title 1</PCK>
    ...
  </HEAD>

  <BODY>

    <!-- here comes page 1 -->
    <PAGE INDEX=1 TYPE=... >
      <NEXTBUTTON TARGET=2>~Next</NEXTBUTTON>
      <TEXT>
        Text of page 1
      </TEXT>

    </PAGE>

    <!-- here comes page 2 -->
    <PAGE INDEX=2 TYPE=... BACK=1 NEXT=3>
        .....

  </BODY>
</WARPIN>