===============================================================
        (c) Copyright ICONICS Incorporated,  1986-2005         
===============================================================
         AlarmWorX32 MMX V8 Post SP1 (8.2.141.9) Hot Fix
      AlarmWorX32 MMX Server UNICODE Hot Fix RELEASE NOTES 
                         August, 2005               
===============================================================

Follow the Installation procedure for proper operation:

WARNING: MAKE SURE YOU ARE INSTALLING THESE HOT FIXES ON A 
         UNICODE SYSTEM RUNNING ALARMWORX32 MMX v8 SP1. 
         FAILURE TO DO SO MAY RESULT IN UNPREDICTABLE BEHAVIOR.

1. Make sure all the ICONICS applications are closed and not running.
   1a. Note: Once you stop the visible applications, please run
             C:\Program Files\Common Files\ICONICS\StopGenesis.exe

2. Locate and backup the files which will be substituted to a 
   safe place in order to roll back if necessary.
   2a. Note: The files for this hot fix are located here:
             C:\Program Files\ICONICS\GENESIS-32\Bin\

3. Copy the file(s) found in the zip archive OVER the old one(s).

4. Restart the application completely.

===============================================================

Files Included in this zipped archive : 

1. AWXMMX32.exe (version 8.2.141.9)
2. AWXMMX32_README.txt

INSTALL THIS HOT FIX ONLY IF YOU ARE EXPERIENCING ONE OF THE FOLLOWING PROBLEMS:

 - AlarmWorX32 MMX Server fails to reconnect to the SQL server 
   configuration database if the database connection is lost.  

 - The AlarmWorX32 MMX Pager agent seems to stop sending out 
   pages when the action set or its active filter has been 
   changed while the AlarmWorX32 MMX server is running.  

 - Your old alarms are being re-triggered: when the journal table 
   is cleared, any pre-existing alarm is reprocessed a second time.

 - Alarms that you have configured with required acknowledgement 
   value set to 0 are not triggering. 

 - Use of TraceWorX32 to troubleshoot issues causes instability
   of AlarmWorX32 MMX Server.

 - You experience irregular triggering of AlarmWorX32 MMX agents

===============================================================

Disclaimer : 

IT IS UNDERSTOOD THAT THE PRODUCT SERVICE RELEASE ALTHOUGH EXTENSIVELY TESTED, MAY CONTAIN DEFECTS AND ICONICS MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND. ICONICS SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES THE PRODUCT MAY HAVE REGARDING MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE USER SHALL HAVE THE SOLE RESPONSIBILITY FOR ADEQUATE PROTECTION AND BACK-UP OF THE DATA USED IN CONNECTION WITH THE TESTING AND USE OF THE PRODUCT.

The User agrees that ICONICS shall not be responsible for any loss or damage to the User, its customers, clients, employees, or any third parties caused by either failure of the Product or oversight in the technical support services rendered by ICONICS.

The User agrees to indemnify and hold ICONICS harmless from any liability, loss, cost, damage, or expense, including attorney's fees, as a result of any claims which may be made by any person, third parties, that arise out of or result from the manufacture, delivery, actual, or alleged ownership, performance, use, operation, possession of the Product.