                 FIRMWARE RELEASE NOTES
                 ======================

Products affected: AXIS 2460 Network DVR

Release date: 2004-08-11

Release type: Production 

Firmware version: 3.12

File name: 2460_312.bin

Preceding release:  3.11

---------------------------------------------------------------------

UPGRADE INSTRUCTIONS
====================
         

1.  You must be at the command prompt and in the directory that contains the
    upgrade file.
    For example: C:\Axis\2460\3_12>

2.  From the command prompt, open an FTP connection to the unit to 
    upgrade. (Do not use a Windows-based FTP program for this - use only 
    command line FTP programs!)

3.  Log in as root. The default password for the user root is "pass", unless
    this has been changed. You must be logged in as the root user
    to upgrade the unit.

4.  Change to binary transfer mode by typing "bin" and press enter.

5.  Type "hash" and press enter. (This will allow you to see how the upgrade
    progresses)

6.  Type the command "put XXX.bin flash_all" where XXX.bin is the name of the 
    upgrade file you downloaded (and maybe decompressed) from our site. This 
    file is typically named 2460_312.bin or axis2460.bin. 

7.  Wait for the flash load to complete, which may take 3-10 minutes. The
    upgrade procedure is in three steps:
    Step 1, Uploading firmware:
      The old firmware will be erased and the new firmware will be saved.
      During this step the Power LED will blink green and amber and all other
      LED:s will be off.
    Step 2, Reboot:
      The FTP session terminates and the system automatically restarts. During
      this step all LED:s will be amber.
    Step 3, Reconfiguration:
      The new firmware settings are configured to match the previous 
      settings. During this step the Status LED will be amber. 
   
8.  After the upgrade has completed, the unit will automatically initiate the
    system, during which the Status LED blinks amber. When the system is initiated 
    and ready for use, the Status LED will be green. 
    


RELEASE 3.12
==============


New features in 3.12:
=======================

3.12.1  Database recover tool hidden at http://[host]/admin/recover.shtml.
        This allows full or partial recovery of the recordings if the internal
        database has become corrupted. It is not recomended to use this
        without first contacting AXIS Support for help.


Corrections in 3.12 since 3.11:
===================================

3.12.1  Long recording lists would sometimes be cut short or missing some data
        if the network connection was not perfect.

3.12.2  A recording list request with search criteria that did not match any
        recording at all will now return an empty list. Earlier firmwares
        returned a HTTP error. 

3.12.3  The file "/etc/user.task.list" for user defined tasks was missing.

3.12.4  The pop-up window for error checking disk hdd claimed incorrectly
        that the disk was "Bus A Slave" instead of the correct "Bus B Slave".

3.12.5  When using the HTTP API for playback (player.cgi) of a recording with
        a pre-alarm buffer the stream would not start playing at the correct
        position (earliest recorded frame of the pre-alarm buffer) unless
        parameter "starttime" or "startframe" was used.

3.12.6  A request for playback of a recording with a pre-alarm buffer
        backwards until the beginning of the pre-alarm buffer would stop
        playing too early (before reaching the earliest recorded frame of
        the pre-alarm buffer).


Application developer / scripting news in 3.12:
=================================================

The following HTTP API groups are supported by the AXIS 2460. For more 
information, please see the HTTP API document available at www.axis.com.


Group         Exceptions
=====         ==========
General       Get property
Jpeg/Mjpg     JPEG/MPEG quad, halfsize, fullsize, hugesize
              JPEG buffer
              JPEG/MPEG CGI only supports parameters camera and timeout
PTZ
Recording     Play recording requires either parameter sessionid or both
              parameter recordingid and parameter camera
              Play single image requires parameter step
I/O
Serial port
PPP
Event
Firewall



Known problems and limitations:
===============================    

             
L1.  Maximum number of events is 25, due to performance limitations.

L2.  Disk utilization is limited to 40GB per disk. Larger disks may be
     installed, but only 40 GB per disk will be used.

L3.  Recordings are not listed with 1/100 sec accuracy. All time and frame
     data is listed as xxxxxx:00.

L4.  Deleting (not removing) all Events will trigger a bug that prevents any
     new Events from being added.
     
L5.  Pressing any button in the player window before the first image has
     been displayed will cause the player to terminate the player session
     by sending illegal requests to the server.