
                             EXTRA INFORMATION



UPGRADES - *** Important note ***

If you are installing this software and you already have an existing
version installed, this version will automatically overwrite and upgrade
the existing version. It will NOT be placed in a new directory.
If you wish to keep the existing version, you should back up all the files
from the application directory before installing this version.
This does not affect first-time installations.

NOTE: From HelpBuilder version 2.02.001, the LLLIB Licensing Library system
      has been used. This licensing system is incompatible with the system
      previously used. If you upgrade an older version of HelpBuilder with
      this version it will revert to a 30-day limited license.
      To release this limit, please contact GPP Software to obtain your free
      upgrade license number (you must quote your existing license number
      otherwise a full license charge will apply) which you should enter via
      the License Administrator program.



INSTALLING THE HELP COMPILER

In order to compile Help files, HelpBuilder requires the Microsoft Windows
Help Compiler (HC31.EXE or HCP.EXE). These have now been placed in the
Public Domain by Microsoft and HCP.EXE is supplied with HelpBuilder, however
you are not being charged for this in your registration fee.
HC31.EXE is supplied with both the Microsoft and Borland C++ compilers,
Visual Basic and probably many other software development tools, so you
will probably already have a copy of it. HelpBuilder can create projects
without HC31.EXE but you will not be able to compile them without it.

The HelpBuilder Setup program assumes that you wish to use the copy of
HCP.EXE supplied and will place it in the same directory as the
HelpBuilder executeables but you can change this to point to your own copy
of HCP.
To configure HelpBuilder, you can either edit HELPBLDR.INI (Not with
HelpBuilder itself) or create a help project and select the Project/Settings
menu option, then select the 'Compiler Installation' section. From here you
can install the compilers of your choice. This is the recommended method.
Note that each help project will contain the name of the compiler
required to compile it to assist in portability.

If you wish to use a help compiler other than HC31.EXE or HCP.EXE you can
use this same technique to configure HelpBuilder as above. Note however,
that your alternative compiler must be HC31 compatible (HelpBuilder does not
produce input files compatible with HC30.EXE at present).
Please note that HC31.EXE and HCP.EXE also require the file 'HC31.ERR' or
'HCP.ERR'. If this is missing the compiler will fail to run.

HelpBuilder uses the HECOMP.PIF file to enable it to run the Help Compiler.
This is placed in your \WINDOWS directory. If you have installed Windows
on any other drive other than C: you will need to use PIF Editor to
edit HECOMP.PIF and change the drive letter of the 'Program File Name' to
the drive on which Windows has been installed.



PAYMENT FOR SOFTWARE

Please see the HelpBuilder help file 'Payment for and Registration of
Software' section for information on how you can pay for your copy of the
HelpBuilder software.



MORE INFORMATION

If you require any further information, please see the HelpBuilder help
file 'Contacting GPP Software' section for information on how to contact
GPP Software.



NEW FEATURES TO VERSION 2.00.000 (Major Upgrade)

     -     Complete re-write to use a database engine to drive
           the entire HelpBuilder product.
     -     Topics can now all be stored in a single .TOP file instead of
           lots of individual .TXT files although you can have one topic
           per .TOP file. You can have as many .TOP files as you like.
     -     Topic Locator window renamed to 'Project Files' and now stays
           open all the time, providing an 'expanding list' feature to
           navigate the topics and files in a project.
           Items in the list can be clicked on to open them. Bitmaps/icons
           etc are passed to the Windows Shell Functions such that
           the currently defined 'file association' is used to edit them.
     -     Significant performance enhancements throughout.
     -     Header files are now easier to maintain such that HelpBuilder
           will maintain all help files in a project and you can switch
           between the file to be maintained. The concept of a 'Main Header'
           has been dropped.
     -     Context ID definition totally rewritten such that checks are
           now performed to stop duplicate IDs being created (works
           across all header files in a project) and to stop an ID
           being assigned to more than one topic.      
     -     All topics MUST have context IDs defined. HelpBuilder no
           longer supports 'generic' text being typed for context IDs
           such as numbers.                       
     -     Build process now lists actual IDs defined in header files
           which have not been assigned to topics. This saves a huge
           amount of time debugging a help file!
           It also lists topics which are using IDs that have not been
           defined in any header files.
     -     Entire data model for a project tightened up so that items
           cannot be deleted to create 'dangling references'.      
     -     Build tags feature dropped because build tags conflict with
           the new data model of a help file: build tags require topics
           to be allowed to have duplicate context IDs which this version
           of HelpBuilder no longer allows.
           Suggested workaround is to maintain two .PRJ files with
           each including the appropriate topic files. A new 'Output'
           field has been added to the Project Attributes dialog so
           that the two projects can create the same .HLP file.
     -     Insert Special Character dialog added.
     -     SpellChecker supplied as standard.

NEW FEATURES TO VERSION 2.01.000

03/06/98 - Year 2000 compliance completed.
05/06/98 - Option to auto-load last project added.
         - Project Attributes dialog converted to a proper 'Tab Dialog'.
         - Rebuilt with new DBLIB library with CSortedIndex classes.
         - Bug fix: If an attempt was made to open the currently open
                    project and error occured and sometimes this caused
                    corruption of the open project. Now fixed: attempting
                    to open the currently open project now does nothing.
         - Target file name of created help file can now be specified and
           the file can be in a completely different directory to the .PRJ
           file.
         - Text underlining facility added via menu option and toolbar
         - Expandable file list now grouped into file types
         - 'Next Id in File' button added to Context Ids dialog. This
           button gives the next Id in the currently selected header file.
19/06/98 - Bug fix: When topics were written to the RTF at compile time
                    they were always written with a trailing CRLF which
                    caused an extra blank line to appear at the end of a
                    topic. For most topics, this was not noticeable, but
                    for popup links, it caused the blank line to appear
                    below the text and the popup window to appear higher
                    by one line more line than the number of actual text
                    lines. This looked wrong and is now fixed.
30/06/98 - Bug fix: When a new topic is created a check should be made to
                    ensure that the title is unique within the project.
                    The code for this check was erroneously left out.
                    Now fixed.
         - Bug fix: When importing a topic file, topic titles were not
                    being checked for duplicates. They now are.
         - Bug fix: $TOPICDATE$ and $TOPICTIME$ text macros were getting
                    their values from the date and time of the .TOP file.
                    They should have been getting their values from dates
                    and times stored for each individual topic which are
                    updated each time each individual topic is changed.
                    Now fixed.                    
20/08/98 - Bug fix: Increased OFFSET field size from 6 to 8. This stops
                    field overflow errors when a .TOP file is larger
                    than 6 digits ie >=1Mb

NEW FEATURES TO VERSION 2.02.000 (Released 10/10/1999)

23/09/99 - Menu options to edit header files check to see if the project
           contains header files before allowing headers dialog to open.
         - Menu option to create a new topic checks to see if the project
           contains any topic files before allowing the New Topic dialog
           to open.
         - Expandable 'Project Files' list appearance improved
         - Bug fix: When a project is opened and one is currently already
                    open, an error occured reporting duplicate context
                    Ids. This occured because the database tables were
                    not being cleared out. Now fixed.
         - Updated help file
         - Recompiled with updated DBLIB database library - this fixes a
           number of problems and also improves performance.
         - Style sheet facility added. This includes a new field in the
           Topic Properties dialog and some extra menu options to enable
           creating, opening and inserting of style sheet files in topics.
14/10/99 - External file output formats extended to include VB 4/5/6
21/10/99 - Topic Link dialog modified: macro field did not scroll
           horizontally.

NEW FEATURES TO VERSION 2.03.000 (Released 06/03/2000)

04/01/00 - Converted to use the LLLIB Licensing Library system
         - Samples re-done to include VB3, VB4/5/6 samples
           

NEW FEATURES PLANNED FOR FUTURE RELEASES

         - Allow files to be attached to a project via the [BAGGAGE]
           section of a .HPJ file
         - Make Find and replace operate across entire project
         - Make SpellCheck operate across entire project


KNOWN PROBLEMS/SOLUTIONS

Please see the HelpBuilder online Windows Help File section 'Commonly
Reported Problems'.
