Running

To run an application that has been built using the Impact Acquire framework all user mode libraries belonging to the framework must be located in the library search path of the application using it. The minimal list of libraries that must be present when working with the Impact Acquire frame work consists of

• mvDeviceManager-lib
• mvPropHandling-lib
• at least one device specific user mode driver(e.g. mvBlueFOX-lib, mvGenTLConsumer-lib, mvVirtualDevice-lib...)
• at least one device specific kernel mode driver(if the driver comes with a kernel mode driver(mvVirtualDevice-lib for example doesn't))

A detailed list of the files and settings needed to deploy an Impact Acquire device driver can be found in the chapter Installation From Private Setup Routines.

Windows®

Running 32-Bit Applications On A 64-Bit Version Of Windows

When an application that has been developed for 32-bit Windows shall be deployed on a 64-bit version of Windows some extra work might be necessary. On 64-bit Windows there can be both 32- and 64-bit user code but only 64-bit kernel code. To deploy an application on 64-bit Windows there are therefore 2 ways to go:

• The complete application is rebuild for x64 using the 64-bit Impact Acquire driver framework. This is the recommended way as this is the only way to get all the benefits a 64-bit operating system has to offer
• The original 32-bit application is deployed on the target system and the Impact Acquire driver framework is set up to use the 32-bit user mode layer on top of the 64-bit kernel modules. This sometimes is the only way to go e.g. if the application depends on code that has not yet been ported or can't be ported to 64-bit.

Even when the latter method is used no extra work is needed when using Impact Acquire as all the packages for 64-bit include the 32-bit user mode code as well.