------------------------------------------------------------------------------
                      MIL AND ACTIVEMIL DRIVER for METEOR 2
------------------------------------------------------------------------------


==============================================================================
MIL INFORMATION
==============================================================================
    
------------------------------------------------------------------------------
CURRENT LIMITATIONS AND PARTICULARITIES USING MIL WITH THE METEOR-II
(Subject to change in future releases of driver, not in printed documentation)
------------------------------------------------------------------------------

Limitations with MJPEG add-on module:
        - Only standard cameras (interlaced and non-interlaced) are supported.
        - Lossless compression is currently not supported.
        - Hardware decompression is currently not supported.
        - Not supported under the Meteor2-DIG.

MdigControl() and MdigInquire():
        - M_GRAB_FIELD_NUM and M_GRAB_FRAME_NUM are only available on 
          the Meteor2-DIG.
        - On the Meteor2-MC, M_GRAB_EXPOSURE_BYPASS is only supported in the
          manual exposure model (M_DISABLE).

MdigGrab():
        - On the Meteor2-MC, when grabing using a 2 taps camera only the field 
          configuration is implemented.  That is when data from tap 0 is written
          to the even field, while data from tap 1 is simultaneously written to
          the odd field. 
        - On the Meteor2-DIG, only vertical subsampling values that are a
          multiple of 2 are supported while grabbing in a HOST buffer. That
          is, M_GRAB_SCALE_Y with 1/2,1/4,...,1/16.

MdigGrabWait():
        - On the Meteor2-DIG, M_GRAB_NEXT_FIELD is not supported.

MdigHookFunction():
        - On the Meteor2-DIG, M_GRAB_FRAME_START and M_GRAB_FIELD_END/_ODD/_EVEN
          are not supported.                            

Under DOS
        - Meteor2-DIG is currently not supported under DOS.


WHEN DEBUGGING USING DIRECTDRAW
-------------------------------

       When the MIL driver makes use of DirectDraw (DDraw), 
       you might experience some problems while debugging an application with 
       a display active. The system will hang and will not let you continue 
       debugging. To work around this problem, a remote debugger may be used 
       to separate the debugger environment from the application user interface. 
       Another method would be to use the M_NO_DDRAW init flag parameter at the 
       MsysAlloc() call. This will not let the allocated system to use DirectDraw.
       Another approach would be to use MdispControl() to specify the use of 
       a timeout to avoid a desktop lock. The control type to use is 
       M_DESTOP_LOCK_TIMEOUT and the control value to specify is the maximum time 
       in ms that the desktop may be locked. This time is usually related to the 
       camera frame time used in the application (two times the frame time). See
       MdispControl() below for more information.

       MdispControl():   
       
            Under Microsoft Windows, to enable/disable the use of enhanced window 
            tracking:
            M_WINDOW_USE_SYSTEMHOOK_TRACKING (M_ENABLE, M_DISABLE) 
            Default=M_ENABLE.
            
            Under Microsoft Windows, to enable/disable the use of desktop 
            lock timeout:
            M_DESKTOP_LOCK_TIMEOUT (M_INFINITE, M_DEFAULT, any other value)
            Default=M_INFINITE.
            
            Value M_INFINITE: The timeout is not activated; therefore the desktop 
            may hang while debugging the application.
            Value M_DEFAULT: The timeout is activated using a timeout value 
            equal to twice the frame time of a standard RS-170 camera.
            Value long > 0: The timeout is activated and the timeout value is
            the time specified in ms.
    


==============================================================================
ACTIVEMIL INFORMATION
==============================================================================
    
------------------------------------------------------------------------------
CURRENT LIMITATIONS AND PARTICULARITIES USING ACTIVEMIL WITH THE METEOR-II
(Subject to change in future releases of driver, not in printed documentation)
------------------------------------------------------------------------------

NOT AVAILABLE YET
-----------------

GrabFieldNumber
- Digitizer.GrabFieldNumber

GrabFrameNumber
- Digitizer.GrabFrameNumber


NOT AVAILABLE
-------------
Display Control FrameStart Event - Not Supported.


WHEN DEBUGGING USING DIRECTDRAW
-------------------------------

       When the ActiveMIL driver makes use of DirectDraw (DDraw),
       you might experience some problems while debugging an application with 
       a display active. The system will hang and will not let you continue 
       debugging. To work around this problem, a remote debugger may be used 
       to separate the debugger environment from the application user interface. 
       Another method would be to use System.InitializationFlag = mNoDirectDraw.
       This will not let the allocated system use DirectDraw.
       Another approach would be to use Dislay.Control() to specify the use of 
       a timeout to avoid a desktop lock. The control type to use is 
       mDesktopLockTimeOut and the control value to specify is the maximum time 
       in ms that the desktop may be locked. This time is usually related to the 
       camera frame time used in the application (two times the frame time). See
       System.Control() below for more information.

       System control "Control" method:
       
            To enable/disable the use of enhanced window  tracking:
            System.Control(mWindowUseSystemHookTracking, mEnable) or
            System.Control(mWindowUseSystemHookTracking, mDisable)
            Default = mEnable
            
            To enable/disable the use of desktop lock timeout:
            System.Control(mDesktopLockTimeout, VAL...) 

               with VAL being one of the following:
            
               mInfinite : The timeout is not activated; therefore the desktop 
                           may hang while debugging the application.
               mDefault  : The timeout is activated using a timeout value 
                           equal to twice the frame time of a standard 
                           RS-170 camera.
               long > 0  : The timeout is activated and the timeout value is
                           the time specified in msec.
               
               Default = mInfinite.
