BUG AND COMPATIBILITY REPORT FORMS
                     ==================================

There are now TWO different report forms for your beta test results:

1. Compatibility Report (for 3rd party product compatibility test results)
2. System Bug Report (for reporting Kickstart, Workbench, Extras bugs)


ALL TESTERS are expected to submit initial Compatibility Reports for each
of their own commercial products, including products that are working fine
under the current release.

Please retest ALL of your products with each new release of the OS, and
submit new reports for any product that behaves differently under the new
release.  If you have any products with severe problems and can not
determine the cause, please contact CATS for assistance.

Many compatibility problems have already been located and addressed thanks
to prompt and informative reports from developers.  But if we don't know
something is broken or different, we can't fix it.

If you have time, we would also appreciate any additional Compatibility
Reports you can provide for other 3rd party products you own.

Before reporting a problem, please verify the accuracy of your report.
Try removing any special programs, replacement commands, or hacks you may
be running (booting from your write-protected, unmodified, master Workbench
disk is a good way to guarantee this).

Submitted reports must include a TELEPHONE number.  Reports must be CLEAR,
COMPLETE and CONCISE.  Based on your bug report alone, we must be able to
REPEAT the bug.  Bugs that we can repeat in-house GET FIXED.

Completed reports may be submitted by any of the following methods:

USENET: mail "uunet!cbmvax!bugs","rutgers!cbmvax!bugs" or "bugs@commodore.COM".
        (email suggestions to "suggestions" instead of "bugs".)

   BIX: Post in your closed conference (amiga.com/bugs or amiga.update/bugs)
        or bixmail to afinkel.

USMAIL: Amiga Software Engineering, ATTN: BUG REPORTS, Commodore Business
        Machines, 1200 Wilson Drive, West Chester, PA  19380-4231, USA



The next pages contain the System Bug Report Form, followed by the
Compatibility Report Form.  Note - please fill in all ":" keyword lines
on the same line with the keyword.   For example,

Name: Joe Wizard  


     SYSTEM BUG REPORT - For Bugs in System Commands, OS, or Hardware
     ================================================================

Date:
Name:
Company:
Address:
Developer#:
EMail:
Phone:

Report Class:    [] Fatal    [] Problem     [] Cosmetic

### Brief Bug Description:




### Bug Location: [Hardware, Documentation, Software, Other]:

### I know this works with:  [] 1.3    [] 68020/30    [] ECS 

### Your Configuration [Model number, number and type of disks, memory,
### add-on equipment, special chip sets, etc.]:



### Revisions [Kickstart/Workbench revision numbers, etc.]:
Kickstart Rev:
Workbench Rev:
Other Revs:

### Other software running or resident at the time of the bug [should be
### "none"].  Don't forget any commands hidden in your startup-sequence!:


### Bug Generation Procedure [remember that someone else will be trying to
### repeat this bug based on your description alone]:












### Other important details:




### Related bugs:


   COMPATIBILITY REPORT - For 3rd Party Product Compatibility Test Results
   =======================================================================

Date:
Name:
Company:
Address:
Developer#:
EMail:
Phone:
### Third Party Product Information ( Omit "Inc.", etc. in Company name )
ProductName:
Product Version:
Product Company:

Report Class:    [] Fatal    [] Problem    [] Cosmetic    [] OK !!!

### ---- Cut here if report type is "OK", else complete rest of report ----
### ----- Please submit a separate report for each distinct problem -------

### Brief Problem Description:



### Problem Location [Hardware, Documentation, Software, Other]:


### I know this works with:  [] 1.3    [] 68020/30    [] ECS 

### Your Configuration [Model number, number and type of disks, memory,
### add-on equipment, special chip sets, etc.]:


### Revisions [Kickstart/Workbench revision numbers, etc.]:
Kickstart Rev:
Workbench Rev:
Other Revs:

### Other software running or resident at the time of the problem [should be
### "none"].  Don't forget any commands hidden in your startup-sequence!:


### Problem Generation Procedure [remember that someone else may need to
### repeat this problem based on your description alone]:








### What are you doing in this part of your code or hardware ?





### Other important details:


### Related problems: