
                  *************************************
                  *                                   *
                  *         ActionMedia (tm) II       *
                  *  Media Control Driver for MMPM/2  *
                  *                                   *
                  *              Read Me              *
                  *                                   *
                  *************************************



     Welcome to ActionMedia II.  This is the second release of the
     ActionMedia II Media Control Driver for MMPM/2 Version 1.0. and
     MMPM/2 Version 1.1.

     ------------------------------------------------------------------------
     MMPM/2 Updates

     If you have MMPM/2 Version 1.0 on your system the installation of 
     the ActionMedia II Media Control Driver will update MDM.DLL in the
     \MMOS2\DLL subdirectory. If you have a later version of MMPM/2 then
     MDM.DLL will not be updated.

     If you have the MMPM/2 Toolkit Version 1.0 installed, the following
     files will also be updated:

                     MCISTRNG.C
                     MCISTRNG.RC
                     MCISTRNG.EXE
                     MCISTRNG.H
                     MCIDRV.H
                     MEERROR.H
                     MMSYSTEM.H

     If you have a later version of the MMPM/2 Toolkit then these files 
     will not be updated.

     ------------------------------------------------------------------------
     Release Notes


     1.  When maximizing the ActionMedia II MCI default window while
         recording, cued for output, or displaying a small still image
         (less than full screen default size), the maximize icon
         becomes corrupted. Functionality is not restricted in any
         way.


     2.  Issuing the MCI_RECORD command causes any loaded video and
         still image elements in the same instance to be unloaded.
         If the record fails during processing of the message (e.g.
         there are not enough driver resources available due to other
         still image instances), the video element will be reloaded,
         but the still image element will not be reloaded. An image
         captured prior to the record, but not saved, will be lost.


     3.  When an AVSS file is saved by the  MCI device driver, no
         Extended Attributes are created with the file.  If you use
         the ActionMedia II Player/Recorder from the WorkPlace Shell
         Desktop, AVSS files created by the ActionMedia II Player/Recorder
         will not automatically have WorkPlace Shell icons associated with
         them.

         A standard icon for AVSS data files will be available for the
         user to use after the ActionMedia II Player/Recorder has created
         the AVSS file. Users can manually add icons to their AVSS files
         using the OS/2 icon editor.  The user can 'Open' the 'Settings'
         for the AVSS file, and click on the 'General' setting, in order
         to give their AVSS files a WorkPlace Shell icon.  A standard AVSS
         data file icon can be found in the \MMOS2\INSTALL subdirectory.
         You can 'Find' this icon under the Icon Editor in order to add
         this icon to your AVSS data files.

         The exact process is as follows:  Create your AVSS data file, and
         view it in the WorkPlace Shell.  Click on it using the right
         mouse button, then click on the arrow next to 'Open', then on the
         word 'Settings'.  Now, click on the word 'General' and 'Find',
         then 'Locate'.  You can then use either 'Path' to type in the path
         "C:\MMOS2\INSTALL" (assuming you installed your MMOS2 system on
         your C: drive) or use 'Drives' to find that path using the
         icons presented.  Then click on 'Find', and you will be presented
         with a list of MultiMedia Icons to choose from.  Select the AM2FILE
         icon, and it should now be associated with your data file.  You can
         now close the settings, and see the new icon on your data file.


     4.  The following sequence of MCI commands could cause an error
         when closing the device.

                 MCI_OPEN
                 MCI_LOAD  <video file>
                 MCI_PLAY  <with notify>
                 MCI_CUE   <for output, with notify>
                 MCI_CLOSE

         The MCI_CLOSE command takes several seconds to complete and
         returns the error code MCIERR_INVALID_MODE. This can be
         avoided by issuing an MCI_STOP command before the MCI_CLOSE.
         This problem is also evident when using the string interface.


     5.  The following sequence of MCI commands do not execute
         correctly.

                 MCI_OPEN
                 MCI_LOAD <video file>
                 MCI_PLAY <to target frame, with notify>
                 MCI_PLAY <to target frame, with wait>

         The second play supersedes the first, but does not wait.


     6.  The following command does not execute correctly

                 MCI_PLAY <to target frame 0>

         This should return the error code MCIERR_OUTOFRANGE, but
         actually cues the playback for output. Developers should
         not rely on this action occurring in future releases.

     7.  The problems with user-defined windows in the first realese
         have now been rectified. For user-defined windows that are
         NOT children of the PM desktop there is no longer any require-
         ment that a parent handle is specified at MCI_OPEN time. The
         parent handle at MCI_OPEN time should ONLY be used when 
         specifying the parent of the default video window.

     8.  The following sequence of MCI commands could cause an error
         when closing the device.

                 MCI_OPEN
                 MCI_LOAD  <video file>
                 MCI_PLAY  <with notify>
                 MCI_CLOSE <issued before the play finishes>

         Under conditions of heavy system load (e.g. several other
         applications accessing the disk during the MCI_PLAY command)
         the notify from the MCI_PLAY command will be lost. The 
         MCI_CLOSE command will also take up to 30 seconds to execute 
         as it times-out waiting for the lost notification.

     9.  PLV AVSS files created with stereo audio are now correctly
         supported by the driver. However, RTV stereo files created
         by the ActionMedia II Toolkit Version 1.1 Capture Sample
         Program (or by software utilizing source code from that prog-
         ram) will not play back correctly. This is due to a problem 
         with the ActionMedia II Toolkit Version 1.1 Capture Sample 
         Program.

     ------------------------------------------------------------------------
