home *** CD-ROM | disk | FTP | other *** search
/ OS/2 Shareware BBS: 10 Tools / 10-Tools.zip / lansystk.zip / MPTSUTIL / APPLETS / MPTS50WS.PRO < prev    next >
Text File  |  1998-05-08  |  15KB  |  265 lines
  1. * CASSETUP application profile for MultiProtocol Transports, 1.0
  2. * NOTE: lines that begin with an asterisk (*) and blank lines are
  3. * treated as comments
  4.  
  5. * ALSO NOTE:  The format of this file and the syntax of its elements
  6. * are subject to change.
  7.  
  8. ****************************************************************
  9. *          APPLICATION DESCRIPTION SECTION                     *
  10. ****************************************************************
  11.  
  12.  
  13.                                       * APPNAME is a long descriptive name.
  14.                                       * It can contain blanks. It should be
  15.                                       * unique among all the Application
  16.                                       * Profiles.
  17. APPNAME = Multi-Protocol Transport^Services 5.0 from Warp Server
  18.  
  19.                                       * APPNICK is a short nickname.  It is
  20.                                       * used to identify this application in
  21.                                       * other scripts and profiles. It MUST
  22.                                       * be unique among all the App Profiles.
  23.                                       * Case is ignored for this parameter,
  24.                                       * so KILLER10 and killer10 are
  25.                                       * considered equal.
  26. APPNICK = mpts50
  27.  
  28.                                       * PROGTYPE tells what kind of
  29.                                       * application this is:
  30.                                       *      Operating System (1),
  31.                                       *      Transport (2),
  32.                                       *      Redirector(3),
  33.                                       * or other (4).
  34. PROGTYPE = 2
  35.                                       * ICON is the icon to be displayed to
  36.                                       * represent this application in CASSETUP
  37.                                       * A restriction in Release 1.1 of
  38.                                       * CASSETUP is that this must be a
  39.                                       * bitmap (bmp) file or DLL resource.
  40.                                       * The path is relative to the directory
  41.                                       * where cassetup is installed.
  42. ICON = CASSETUP:#107
  43.  
  44.                                       * OS tells whether the program runs
  45.                                       * under OS/2 (1) or DOS (2)
  46. OS = 1
  47.  
  48.                                       * PACKAGE tells whether it is a complete
  49.                                       * application (1) or a fix (2)
  50. PACKAGE = 1
  51.  
  52.                                       * If it is a fix, FIXTO is the APPNICK
  53.                                       * of the application it fixes.
  54. * FIXTO =
  55.  
  56.                                       * And FIXLEVEL specifies the relative
  57.                                       * fix level.  It can be -1 to indicate
  58.                                       * it is an unsequenced fix.
  59. * FIXLEVEL =
  60.  
  61. ****************************************************************
  62. *                   IMAGE LOAD SECTION                         *
  63. * (elements in this section describe how the application's     *
  64. * install image is put onto a Code Server -- usually by being  *
  65. * copied from install diskettes or CD-ROM)                     *
  66. ****************************************************************
  67.  
  68.                  * The directories below are set up when the application's
  69.                  * install images are loaded onto the code server.
  70.  
  71.                                       * APPDIR is the subdirectory (relative
  72.                                       * to the CID mount point) where
  73.                                       * the app's install images will be
  74.                                       * stored. The directory will be created
  75.                                       * if it does not exist.
  76.                                       * The CID Mount Point is specified
  77.                                       * in the CASSETUP gui.
  78. APPDIR = IMG\mpts50
  79.  
  80.                                       * WORKDIR is a subdirectory (relative
  81.                                       * to the WORK alias) where various
  82.                                       * application-required programs may be
  83.                                       * placed.  It is optional, but almost
  84.                                       * every application will need one.  The
  85.                                       * directory will be created if it
  86.                                       * does not exist.
  87.                                       * Some CID documentation refers to this
  88.                                       * as the EXE directory.
  89.                                       * The WORK alias is specified in the GUI.
  90. WORKDIR = EXE\mpts50
  91.  
  92.                                       * DLLDIR is the directory (relative to
  93.                                       * the DLL alias) where DLLs for
  94.                                       * the product will be placed.  Not all
  95.                                       * applications will need one.
  96.                                       * The DLL alias is specified in the GUI.
  97. DLLDIR = DLL\mpts50
  98.  
  99.                                       * RSPDIR is the directory (relative to
  100.                                       * the RESP alias) where response
  101.                                       * files will be placed.
  102. RESPDIR = RSP\mpts50
  103.  
  104.                                       * LOGDIR is the directory (relative
  105.                                       * to the LOG alias) where log files
  106.                                       * will be placed.
  107. LOGDIR = LOG\mpts50
  108.  
  109.                  * The parameters below describe the methods to be
  110.                  * used to put the applications's images on the Code Server.
  111.  
  112.                                       * METHOD defines whether XCOPY or an
  113.                                       * application-supplied program will be
  114.                                       * used to load the images.
  115.                                       * Methods are 1=XCOPY-is-used
  116.                                       *             2=Application-supplied
  117. METHOD =  2
  118.  
  119.                                       * NUMDSKT is the number of diskettes
  120.                                       * (or CD-ROMS)in the package.  It is
  121.                                       * required when the XCOPY method is
  122.                                       * being used, but optional otherwise.
  123. NUMDSKT = 1
  124.  
  125.                         * The next parameter deals with loading the images
  126.                         * using an application-provided program.
  127.  
  128.                                       * If METHOD==2 the IMAGELOAD keywords
  129.                                       * specify the commands to be run and
  130.                                       * the meaning of their return codes.
  131.                                       * IMAGELOAD.0 specifies the number of
  132.                                       * commands to be run.
  133. IMAGELOAD.0 = 1
  134.                                       * IMAGELOAD.n is a template for the
  135.                                       * nth command that will be executed.
  136.                                       * Templates may contain Symbolic
  137.                                       * Substitution Parameters, which will be
  138.                                       * replaced by actual values when the
  139.                                       * command line is executed.
  140.                                       * The Symbolic Substitutions supported
  141.                                       * for IMAGELOAD are
  142.                                       *     $T      which is replaced by the
  143.                                       *             target path (the path to
  144.                                       *             which code images are to
  145.                                       *             be moved).
  146.                                       *     $S      which is replaced by the
  147.                                       *             source drive (and,
  148.                                       *             possibly, path) from which
  149.                                       *             the code images will be
  150.                                       *             copied.
  151.                                       *     $W      which is replaced by the
  152.                                       *             fully-qualified path of
  153.                                       *             the Work directory.
  154.                                       *     $D      which is replaced by the
  155.                                       *             fully-qualified path of
  156.                                       *             the DLL directory.
  157.                                       *     $F      which applies only to CSDs
  158.                                       *             and is replaced by the
  159.                                       *             fully-qualified path of
  160.                                       *             the Work directory of the
  161.                                       *             application being fixed.
  162. IMAGELOAD.1 = XCOPY $S\CID\SERVER\MPTS $T /s
  163.  
  164.                         * The next parameter deals with commands to be
  165.                         * run _before_ the image loading command.  They
  166.                         * are run regardless of the Method selected.
  167.                         * The work directory, will be put at the front of the
  168.                         * path and dpath during execution of these steps
  169.  
  170.                                       * The SETUP keywords specify steps
  171.                                       * to be performed before image
  172.                                       * loading.  Commands to unpack the
  173.                                       * load image program, for example, might
  174.                                       * go here.
  175.                                       * SETUP.0 says how many steps there
  176.                                       * are
  177. SETUP.0 = 1
  178.                                       * SETUP.n gives the prompt text for
  179.                                       * step n.  If it is blank, then the
  180.                                       * step is done immediately
  181. SETUP.1 =  MPTS 5.0 WARP SERVER CD-ROM
  182.                                       * If there is a diskette prompt, then
  183.                                       * the diskette can be verified either by
  184.                                       * Volume Label or presence of a file.
  185.                                       * These elements are optional.
  186. SETUP.1.0MarkerFile = CID\SERVER\MPTS\MPTS.EXE
  187. * SETUP.1.1Volser = WARP SERVER
  188.                                       * For each step, there can be as many
  189.                                       * commands as needed. SETUP.n.0 parm
  190.                                       * tells how many commands make up
  191.                                       * step n.
  192. SETUP.1.0 =     0
  193.  
  194. ****************************************************************
  195. *                      INSTALL SECTION                         *
  196. * (elements in this section deal with how the application is   *
  197. * remotely installed).                                         *
  198. ****************************************************************
  199.  
  200.                                       * INSTCMD is the template of the
  201.                                       * install command.  Symbolic
  202.                                       * substitution is supported for $T, $S,
  203.                                       * $D and $W as described above, but
  204.                                       * also for
  205.                                       *     $B (boot drive)
  206.                                       *     $M (Maint dir)
  207.                                       *     $R (response file dir)
  208.                                       *     $V (server name)
  209.                                       *     $F (directory for the /S2 parm)
  210.                                       *     $C (client name)
  211.                                       *     $O (boot drive)
  212. INSTCMD = $S\mpts /e:prod /s:$S /t:$B /l1:$L\"client".log /r:
  213.                                       * INSTCMDM is used if we use a
  214.                                       * different install command when running
  215.                                       * under a maintenance system
  216. INSTCMDM = $S\mpts /e:maint /s:$S /t:$B /l1:$L\"client".log /r:
  217.  
  218.                                       * block for the install command line.
  219.                                       * If it is specified then the response
  220.                                       * file (usually /R) parameter in
  221.                                       * INSTPROG must be at the end of the
  222.                                       * string and be empty.  For example:
  223.                                       *    myinstpg /S:something  /R:
  224. DEFRESPFILE = default.rsp
  225.  
  226.                                       * MAINTSYSREQ tells whether the install
  227.                                       * command must be run under a
  228.                                       * maintenance system (1 is yes, 0 no)
  229. MaintSysReq = 0
  230.  
  231.  
  232. ****************************************************************
  233. *              MAINTENANCE SYSTEM SECTION                      *
  234. * (applications that have a PROGTYPE of 1 (OS), 2 (transport)  *
  235. * or 3 (redirector) have associated commands that allow them   *
  236. * to be installed as part of Maintnance Systems.  This section *
  237. * describes those commands.                                    *
  238. ****************************************************************
  239.  
  240.                                       * MSCMD.0 tells how many commands
  241.                                       * follow
  242. MSCmd.0 = 2
  243.                                       * MSCMD.n is the template for the nth
  244.                                       * command.  Symbolic substitution for
  245.                                       * $T, $W, $D and $S is always supported
  246.                                       * and other translation is available
  247.                                       * during processing of Boot Diskette
  248.                                       * Build scripts.
  249. MSCmd.1 = $S\mpts /e:prep /s:$S /t:$M /tu:$B /l1:$L\"client".log /r:
  250. MSCmd.1.0DefRespFile = default.rsp
  251.                                       * MSCMD.n.0CmdName associates a name
  252.                                       * with the nth command.  The name
  253.                                       * should contain only letters and
  254.                                       * numbers, and should be unique among
  255.                                       * all MSCMDs in all Application
  256.                                       * Profiles.
  257. MSCmd.1.0CmdName = mpts_prep
  258.  
  259.                                       * MAINTSYSBUILD is the ordinal(s) of the
  260.                                       * mscmd(s) that define how a
  261.                                       * disk-based maintenance system is
  262.                                       * built with this app.
  263. MSCmd.2 = $S\thinlaps . $T $N
  264. MaintSysBuild = 1
  265.