<<TopSpeed Support Application -- Bug Reporting Policy>>
 TopSpeed Support Application -- Bug Reporting Policy

In order to assure that suggestions and bug reports are received and
serviced, we ask that you use this electronic reporting method instead of
reporting bugs in a CompuServe messages or by phone. This method will assure
that you receive acknowledgment of your report and have a method to check
its status. Before reporting any problems or suggestions, please check the
TopSpeed Database to see if it has already been reported. This will limit
the number of duplicates; additionally, if the problem has been previously
reported, you may find that a work around has already been logged.


<<Steps to Report a Bug or Submit a Suggestion>>
  Steps to Report a Bug or Submit a Suggestion:

1. Select Set Up from the main menu and complete all the information on
   this screen. PkZip is required and the path must be entered in the Set
   Up form. PkZip.exe is a shareware product available from most any BBS.
   Please include the product registration number found on the first
   install disk your Clarion For DOS. (Note: If you upgraded from an
   earlier release the registration number will be on your original disks.
   A response method is required. TopSpeed Corporation will automatically
   send either a message, fax or letter acknowledging the report. The
   complete database of reported bugs and suggestions will be available for
   download. See also TopSpeed Database

2. Select By User Bug Number from the User Bug Reports menu, Insert
   to add a new bug or suggestion. Press the Steps to Duplicate and
   Workaround buttons to add addition information. If there are example
   files need to demonstrate the bug, press the Select Example Files button.
   Use Pick File to select files and the press the Zip button to zip these
   files into a single file. This file will be called (yourbugnumber.zip).
   Example 1.ZIP, 2.ZIP

3. Complete the bug entry form and press the OK
   button. Continue to add any additional reports or suggestions.

4. When you are ready to prepare a file to send to TopSpeed, select Prepare
   Bugs For Upload from the main menu. This step will create a single file
   in the SUPPORT subdirectory containing UPLOAD.TPS, which includes all
   records that were not previously reported, plus the individual 1.zip,
   2.zip files and the CONTROL.TPS file with your system information. This
   zip file name will not have a .zip extension. The name will be:
   (your reg.number.today's day + today's number) example 999999.262
   This indicates the second file created for registration number 999999 on
   the 26th. In case you need this number, it can be found along with the
   example files zip file name in your database on the bug entry screen.

5. You may now upload this file to USA CompuServe TopSpeed Forum:

   USA     GO TOPSPEED or GO CLARION - LIB 3 Bug Uploads
           Clarionet.   305 785-9172               8N1

   EUROPE  TopSpeed BBS -   44- (0) 582- 769666    8N1

Or mail disk to:
   TopSpeed Corporation
   Attn.: Technical Support
   150 E. Sample Road
   Pompano Beach, Fl 33064-3550
   USA

   TopSpeed Software Limited
   Clare House
   Thompsons Close
   Herts
   AL5 4ES
   ENGLAND, UK


<<Downloading The TopSpeed Database>>
Downloading The TopSpeed Database:

The TopSpeed bug and suggestion database will be made available for
download on CompuServe and Clarionet. The download file will contain a file
called PROBLEMS.TPS. This file will always be the complete database file so
it should replace your existing copy. This will allow you to view all
reported bugs and suggestions received by TopSpeed. NOTE:  The database you
download will contain suggestions, duplicates, unconfirmed reports,
confirmed reports and fixed bugs because we are making our internal database
available to you. Please understand that the total number of reports does
not in any way reflect the true number of confirmed bugs in the product.

<<Merging the TopSpeed Database>>
Merging the TopSpeed Database:

Select Merge Database Files from the main menu. This option will update your
database with the information from the TopSpeed database, including, Top
Speed's assigned bug number, status, and any work around that has been
posted.



<<Status Codes>>
 Status Codes

The following table explains the Incident Status codes

STATUS            DESCRIPTION

Incident         - As reported, not yet processed.

Problem          - The Incident report has been tested and confirmed as a
                   bug.

Doc Error        - An error in the printed manuals.

Help Error       - An error in the online help.

Suggestion       - Helpful hints that may improve the product.

Request          - New feature request.

Fix for QA       - Development has fixed bug, awaiting Quality Assurance
                   (QA) testing. Fix has not been confirmed by QA.

Passed QA        - QA has confirmed that bug is fixed. Fix will be
                   available in a future release.

Closed-Released  - Fix has been incorporated in specified version.

Closed-Duplicate - Duplicate of a previously reported incident -Duplicate
                   number is indicated. To track this incident, refer to
                   the other number.

Closed-Doc/Help  - Updated Documentation or Help error has been corrected
                   in specified printing or version number.

Closed-Need      - Incident did not contain enough information to reproduce
Info               the bug. Please submit a new bug report with more
                   detailed information, including Steps to Reproduce. If
                   the problem occurs at runtime, please include a test
                   file to assure that we will be able to reproduce the
                   problem.

Closed-Not a Bug - Problem reported is intended behavior.

Closed-Can't     - Bug cannot be reproduced in specified version. If you
Reproduce          can still reproduce this problem in the current release,
                   please submit a new bug report with more detailed
                   information. If the problem occurs at runtime, please
                   include a test file to assure that we will be able to
                   reproduce the problem.

Closed-Not       - Incident is not related to Clarion For DOS or was a
Accepted           suggestion that was not accepted.


