NEW SOFTWARE RELEASE ==================== Products involved: AXIS Camera Management Release date: March 26, 2007 Release type: Production Software version: 2.00.031.0 File name(s): AXISCameraManagementSetup.exe File size: 24 725 400 bytes Supported OS: Microsoft Windows Vista Business, Windows XP Professional (Service Pack 2), Windows 2000 (Service Pack 4), Server 2003 (Service Pack 1). For other operating systems, see www.axis.com/techsup Preceding release: 2.00.026.0 -------------------------------------------------------------------------------- INSTALLATION INSTRUCTIONS ========================= Please follow the instructions found at http://www.axis.com/techsup/cam_servers/cam_mgmt_software/firmware.php or the file named howtoinstall_ACM.txt. -------------------------------------------------------------------------------- RELEASE 2.00.031.0 ================== New features ============ F01 Support for Microsoft Windows Vista. Corrections since 2.00.026.0 ============================ C01 Correct formatting of HTML table when exporting devices. Co2 The status "Invalid Operation" is not shown when unknown device is selected for custom operation. RELEASE 2.00.026.0 ================== New features ============ F01 Support for AXIS 292 (version 4.40 and above) Note: ACM will discover AXIS 292 on the network, but most product maintenance is not supported. Modifications ============= M01 Added support for HTML encoded parameter names. M02 Changed the default value of maximum transmitted packages per second from 1000 to 500. Corrections since 2.00.023.0 ============================ C01 The number of events in the Event Log dialog (View - Event Log) was not reset when the log was cleared. C02 Text in Japanese Windows XP was clipped. C03 It was possible for a user to attempt to set some read-only parameter in a device even though ACM knew it wouldn't work. ACM now prohibits setting read-only parameters. C04 The proposed parameter values for the parameter AspectRatio (in group ImageSource.I0.Sensor) were incorrect. C05 Validation of subnet masks are now performed correctly. Known limitations =================