------------------------------------------------------------------------------- Matrox Imaging Library (MIL) 10.0 Update 11 Release Notes (MilSupersight) February, 2014 (c) Copyright Matrox Electronic Systems Ltd., 1992-2014. ------------------------------------------------------------------------------- This document outlines what is new with MIL for Matrox Supersight and explains the current limitations and particularities when using MIL with Matrox Supersight. It also presents last minute information that did not make it into the manual or on-line help. Note that this text file serves to complement your manual. The information found in this file overrides your formally documented material. Contents 1. Matrox Supersight with MIL. 1.1 What's new in MIL 10 Update 11. 1.2 What's new in MIL 9 Update 65 and MIL 10. 1.2.1 Overview. 1.2.2 Bug fixes. 1.3 MIL 9.0 Update 7. =============================================================================== 1. Matrox Supersight with MIL 1.1 What's new in MIL 10 Update 11 - Fixed SupersightCfg alarms for Supersight Solo. - Fixed dmilpcie connection issues after Slave SHB restart. 1.2 What's new in MIL 9 Update 65 and MIL 10. 1.2.1 Overview. - Added support for Supersight Solo. - Updated SupersightCfg. 1.2.2 Bug fixes. - Fixed connection issues with dmilpcie. 1.3 MIL 9.0 Update 7. - Additions to MsysAlloc(), SystemDescriptor parameter: - dmilpcie: Use dmilpcie instead of dmiltcp to use the Supersight PCIe connection when using Distributed MIL. Usage is: "dmilpcie://RemoteComputerName/MILSystemType". The IP address is not supported. - Additions to MilConfig. - The Distributed MIL server can now be started at the logon of the user. This permits MILGPU to be used with Distributed MIL. - Added the dmilpcie protocol in the Connections page of Distributed MIL. - Licenses. License permissions of the Main board are now propagated to all slave SHBs (System Host Board).