
           CHIEF'S GENERIC INSTALL for WINDOWS v2.10
           -----------------------------------------

           (c) 1994, Dr. Abimbola A. Olowofoyeku (The African Chief)
           ----------------------------------------------------------


    Files in the package
    --------------------
    1. INSTALL.EXE    (Windows install executable)
    2. WINSTALL.HLP   (basic help file for the installer)
    3. SAMPLExx.INF   (sample INF files for WINSTALL.INF)
    4. INSTALL.TXT    (this file)


    What is CHIEF'S GENERIC INSTALL?
    --------------------------------
    Chief's Generic Install (hereinafter referred to as "Install") is a
    generic program for installation of Windows applications.

    Install is an "off-the-shelf" installation suite. The program will
    copy files from floppy disks (or a directory on a hard disk) to the
    destination directory. If the files are compressed with Microsoft's
    COMPRESS.EXE they will be decompressed automatically.In this respect
    Install uses the routines in LZEXPAND.DLL. If the files are not
    compressed, they will simply be copied.

    Using Chief's Install
    ---------------------
    I have tried to make Install as easy to use as possible. You only
    need to take the following steps;

      1. Create your installation disk set by placing your application's
         files on them (up to 20 installation disks are supported).

     2.  You may or may not compress the files with COMPRESS.EXE (it is
         immaterial whether you do so or not). If the files are compressed,
         they should retain their real names - the names you will want them
         to have when installed. Install does NOT rename files which it
         decompresses (e.g., if you compress your file to "MYPROG.EX_" then
         that is the name it will have when decompressed - the name will NOT
         be changed to "MYPROG.EXE").

      3. Create an installation information file in ASCII format, using a
         text editor. The file should be called WINSTALL.INF, and should be
         in the format described below.

      4. Run the Install program.

    That's it folks!


    Restrictions/Features
    ---------------------
    1. You can only install into ONE destination directory.
    2. Only a maximum of 20 installation disks are supported. Install will
       prompt for the disks as they are required.
    3. Install will offer to put the destination directory into the
       "PATH" statement in AUTOEXEC.BAT
    4. Install will optionally create a Program Manager group file, and
       icons for any supplied executables
    5. Install will optionally run any supplied program immediately after
       the installation is complete
    6. Install will optionally create icons for other items, such as
       README files, help files, etc.
    7. The stipulated format of the WINSTALL.INF file must be followed
       strictly.
    8. Install allows you to supply on-line for the installation.
       You have to create a Windows help file called WINSTALL.HLP. This
       help file can be accessed by clicking on the "HELP" button. A simple
       one is supplied. You can either use that, or create your own.
    9. Install will check whether there is sufficient space on the target
       drive - based on information which you supply as to how much disk
       space your application requires.
    10. Install will NOT make entries in the Windows .INI files.


    The format of WINSTALL.INF
    --------------------------
    WINSTALL.INF is the configuration file for the installation. You need
    to follow the instructions on this file carefully, otherwise, Install
    will not work correctly. The best thing is to edit the sample files
    which I have provided. They contain sufficient comments for you to
    understand them. WINSTALL.INF is a standard ASCII file, in the
    following format;

    1. Any line beginning with a ";", or "[" or "REM" is ignored
    2. Empty lines are ignored

          e.g., these lines will be ignored

              [This line will be ignored]
              ; So will this line

              REM  so will the one just above me, and me as well!


    3. Each line must not contain more than 220 characters
    4. The first thing to do is to specify the disk(s) in the installation
       set, and the file(s) which should be copied from them. Each file name
       or file specification should be separated from the next one by a space.

       You can use the wildcard character "*" in this regard. The format for
       specifying the disk(s) is this;

         DISK n = <filenames(s)>

            where:
             n = numbers from 1 to 20
             <filename(s)> = the file specifications
             the easiest thing to do would be to just specify "*.*" - to
             copy all the files - but you can be more specific

        EXAMPLES:
          DISK 1 = *.*
          DISK 2 = *.DLL *.HLP *.DRV WS*.* EXPAND.EXE COMPRESS.EXE README.TXT
          DISK 3 = HELP.DOC *.FFF

       If you specify a file that does not exist, it will just be ignored.

       * A maximum of 30 file specifications is allowed on each "disk" line -
         but note that each line cannot be longer than 220 characters in total.

    5. After the installation disk set has been specified, the NEXT line
       (ignoring comment lines and REMS - see note 1 above) must contain
       the name or title of your application. This is what will appear in
       the title of the installation program's window - e.g.;
            Great Program v1.20

    6. The next line after this should contain the name of the DEFAULT target
       directory for the installation. The user will be able to change this
       at run time - e.g.,
            C:\MYPROGRAM

       If the target directory does not exist Install will create it - but
       note that it will not create directories recursively.

    7. The next line should contain the amount of disk space which will
       be needed for the installation. The amount should be in BYTES and
       should only contain whole numbers (no spaces, no letters, and no
       decimals).

       This information is used by Install to warn the users of the amount
       of space that they need to have free on their disks, and to show the
       progress of the installation in the "percentage meter". Install will
       check to see that the specified amount of space exists on the
       target drive before installation begins. If there is insufficient
       space, Install will abort with an error message.


       There is no need for the number to correspond exactly with the actual
       required number of bytes - a difference of up to 1% of the size of
       your application (plus or minus) is allowed, and such differences will
       be catered for automatically. In fact, it is always good to add about
       1% to the actual disk space needed - because of the vagaries of disk
       cluster sizes, it may be wise to over-estimate the disk space needed
       (a little bit of trial and error is in order here).

    8. The next line should contain the name of the Program Manager Group
       in which the icons will be created. This can be the name of an
       existing group (e.g., "Accessories", "Main", etc.) in which case,
       the items will just be added to the ones already in that group.

       However, you may specify a completely new group. If this does not
       exist, it will be created (e.g., "MyProgram").

    9. The next line should contain the names of the executables for
       which you want Program Manager icons to be created. There can be
       a maximum of 10. Each name should be separated by a space.

          e.g. MYMAIN.EXE MYSUB1.EXE CONFIG.COM

         in this example, you want to create icons for 3 program files.

    **** ALL THE ITEMS SPECIFIED ABOVE ARE COMPULSORY ****

   10. The next line should contain the name of any program that should be
       run immediately after the installation is completed - e..g.,
            CONFIG.EXE

       Only one program can be supplied on this line.

       If you do not want any program to be run, you must put "NONE" on
       this line.

   11. The next few lines should contain any other Program Manager icons
       that you might want to create - e.g., for README files, help files,
       etc.  - e.g.,
             WINHELP.EXE MYPROG.HLP
             NOTEPAD.EXE ORDER.FRM
             NOTEPAD.EXE REGISTER.TXT
             NOTEPAD.EXE README.TXT

       You can have up to 10 such items (INCLUSIVE of those on no. 9 above)
       each on a line by itself (i.e., if you have 4 executables on no. 9
       above, then you can only have 6 items here).

   12. The LAST line should specify whether you want Install to start up
       maximized or not. If the last line contains the word "MAXIMIZE" then
       Install will start maximized - otherwise it will just start normally.



    LICENSE
    -------

    Chief's Install is released as "ChiefWare". This means that you may use
    and supply it as the installation routine for any of your applications,
    as long as;
       [1] You offer me, by e-mail, a (registered) copy of your application,
           and, if I am interested in it, you send me a free copy. This point
           only applies to shareware and freeware applications
       OR
           You send me a nice and unique postcard from your area

       [2] My name does NOT appear ANYWHERE in your application's
           documentation - I am not interested in answering any questions
           from any of your customers.

    You may also distribute it freely - as long as;
       [1] ALL the files which I have supplied are included, and
       [2] NO ATTEMPT is made to modify or alter ANYTHING in any of the files.
       [3] You do not charge ANYTHING for distributing this package (disk
           vendors may charge a reasonable fee, not exceeding $5 (US) for
           media and duplication).


    Please note the disclaimers below.

    DISCLAIMER
    ----------
    I do NOT warantee ANYTHING concerning any of the programs which
    make up Chief's Install. I accept NO RESPONSIBILITY for ANY LOSS
    OR DAMAGE of ANY kind, including, but not limited to, losses of a
    physical, mental, social, financial, marital, or of whatever nature,
    resulting from the use, or the purported use of Chief's Install,
    for any purpose whatsoever. You use Chief's Install ENTIRELY AT YOUR
    OWN RISK, and you supply it to your customers or acquaintances
    ENTIRELY AT YOUR OWN RISK.

    If these terms are not acceptable to you, then please DELETE all
    the files from your disks immediately.


    BUGS
    ----
    There may be bugs in the program, although I do not know of any extant.
    I welcome bug reports. I will try to fix them if I can. If I can not
    fix them, then sorry.


    Contact address:
    ----------------
    Dr. Abimbola Olowofoyeku
    268 Horwood
    Newcastle
    Staffs, ST5 5BQ
    ENGLAND

    Email: laa12@keele.ac.uk



      ------------------
      Dr. A. Olowofoyeku
      September 1994
      ------------------

