WarpIN basically consists of two parts:
  1. The "back end" (BE), which is portable (i.e. not OS/2-specific) and consists of a single C++ class called WIArchive, making it annoyingly easy to use. For details, please refer to the WarpIN source code.

  2. The "front end" (FE) has everything that's operating-system specific. This includes all PM dialogs you see on the screen, the global database, system configuration (CONFIG.SYS, WPS objects and classes), script handling, and such. This is developed by me, Ulrich M”ller. There are actually two "front-ends" right now, which both interface with the back end:

    1. WIC.EXE, the "WarpIN Archive Creator". This uses the back end to create archives.

    2. WARPIN.EXE then is the real installer. This uses the back end to unpack archives, read the install script and react accordingly.