Is there a smaller runtime only version of the NI-DAQmx 8.5 drivers?

[Troy]

Digging up old bones here, but have a question regarding building the installer with the Runtime 5 choice.  I am using 8.6.1 and DAQmx8.8 in development.

My production target machines do not need any of the items left out of the Runtime 5 and all but one of my installs worked with no issues.  However, the one install that is giving me problems is on a machine that also has LV8.5 development environment and the DAQmx drivers that came with LV8.5. 

My real question is can the DAQmx runtime 8.8 drivers co-exist with the full DAQmx drivers included with LV8.5 (DAQmx 8.6 I believe) or will there be some conflicts or missing items causing problems? 

My application is locking up and we got an error from Visual C++ Runtime Library that showed the program nimxs.exe was terminated unexpectedly when we restarted the PC at one point after install.  This is what is leading me to believe that the driver versions cannot co-exist.

[EEsRULEtheWORLD]

Hi, Troy.

Just to review:

• The full DAQmx installs all of the driver software included in NI-DAQmx, except LabVIEW SignalExpress.  This is used if you need to develop with NI-DAQmx on your machine. 
• The runtime 5 DAQmx installs all of the driver software included in NI-DAQmx, expect for LabVIEW SignalExpress, DAQ Assistant, NI-DAQmx documention, LabVIEW real-time support, MAX, and application development environment (ADE) support for LabVIEW, LabWindows/CVI and NI Measurement Studio.  This is used if you are deploying your NI-DAQmx application into an executable that requires no further development.  When using this option, make certain that you did not use the DAQ Assistant in developing the application, the application will not be deployed to a Real-Time target, and MAX is not required for such things as troubleshooting installation, setting up device configurations including device names, tasks, scales, and channels.  This can be used to create an installer.

 
The full DAQmx and runtime DAQmx can coexist.  The LabVIEW runtime engine will exist separately, and the target machine will be able to run the executable using the runtime it was built with.  You can also install as many different versions of runtime engines on a machine as you would like, and they will not interfere with one another.  For example, if you want to send someone a LabVIEW executable built on LabVIEW 8.6, and they are already utilizing LabVIEW executables built with LabVIEW 6.1.  The new 8.6 LabVIEW runtime engine will exist next to the older LabVIEW 6.1 runtime engine on the target machine, and nothing will be overwritten or conflict.

Here is a good KnowledgeBase for information regarding which version of LabVIEW Runtime should be used.  The Related Links on this KnowledgeBase are also very good.

The issue at hand seems unrelated to the versions of the Runtime and full versions of DAQmx.  Make sure to add the following services to the exception list of any firewall software: NIMax.exe, nimxs.exe, NiAsstnt.exe, nipalsm.exe, nidevmon.exe.  I think there may be a Database corruption error.  Go through the steps in the following KnowledgeBase and see if this solves the issue:  Why do I get a MAX Database Corruption Error?

I hope you're having a great day!