Home

Previous

Up

Next

MultiCam Boards Documentation > MultiCam Documentation > MultiCam User Guide > Installing MultiCam > Supported Platforms > Supported OS
Supported OS

This section summarizes the information related to the latest MultiCam version of each different type of the MultiCam driver.

MultiCam for Windows (32- and 64-bit)

For a complete list of the supported OS, please refer to the Releases Notes coming with your MultiCam packages on the Euresys website.

Power saving modes of the operating systems (StandBy, Sleep, Suspend...) are not supported.

MultiCam for Windows 32-bit

When PAE —Physical Address Extension— is activated (Windows 32-bit), it is mandatory to use the automatic memory allocation mode of MultiCam.

The development of 64-bit applications with MultiCam is also possible on a 32-bit Windows installation, providing that the x86-64 development tools are properly installed. Both the 32-bit and 64-bit versions of MultiCam.lib import libraries are installed when the import libraries installation option is checked.

On Windows operating systems, MultiCam relies on a service named MultiCam Service. This service is automatically started when the computer boots. Software should only access MultiCam when this service is started. McOpenDriver will return MC_SERVICE_ERROR if the MultiCam service is not started when called.

MultiCam for Linux (32- and 64-bit)

Power saving modes of the operating systems (StandBy, Sleep, Suspend...) are not supported.

MultiCam for Linux 32-bit

In case of 32-bit operating systems, the memory allocated for MultiCam must be below 4 GB in the physical memory addressing space. PAE —Physical Address Extension— is not supported.

MultiCam for Linux 64-bit

In case of 64-bit operating systems, it is allowed to allocate memory anywhere in the available physical memory addressing space. When memory is allocated beyond the lowest 4 GB of the physical memory addressing space, the OS performs automatically a buffer copy.

Image Buffer Allocation

Despite the support of 64-bit OS, the physical memory addressable by a frame grabber is determined by the hardware capabilities.

For boards having a 32-bit physical addressing capability, it is mandatory to allocate the image buffer into the lowest 4 GB of the physical memory. Consequently, for systems having more than 4 GB of physical memory, it is mandatory to use the automatic memory allocation mode of MultiCam.

Currently, only Grablink Full, Grablink DualBase and Grablink Base support 64-bit physical addresses.