How compatible is 2009 runtime engine vs older versions?

[aeastet]

We are getting ready to launch a new software package commercially. In the past we have had troubles with compatibly between runtime engines with LabVIEW. Does anyone have experience with 2009 runtime with LabVIEW 7.0, 8.0, 8.1, 8.5, 8.6 and 2009 installed on a computer?

[JeffL · Accepted solution]

Hi aeastet,

While you do need the run-time engine for the version of LabVIEW you use/build an executable with, there shouldn't be any cross-over issues with having the other ones installed. I have runtimes for 7.1-2009 SP1 installed with no problem.

[DarkLordOfG]

Jeff,

I got an error when trying to install the 7.1.1 runtime on a machine that already had the 2009 runtime.  It says installation aborted a higher version of the product is already installed.  How do I get an older version installed?

John

[LV_Pro]

My recollection is that you have to remove the newer version(s) and reinstall oldest to newest.

[JeffL]

Hi rammer,

I don't think you should get such an error because each run-time is specific to the version of LabVIEW. I recently installed 8.2.1 onto my machine with all the latest stuff on it with no problem.

What version of the installer are you running? What is the exact error message?

[macski06]

Is this still the only way to install an older run-time engine?

This leaves 3 options when working with multiple people using varying versions of LabVIEW and/or the runtime engines:

- Build all programs for multiple runtime engines and find out which version will be necessary for each person using the executable.

- Tell people who have a newer version of LabVIEW that they will need to delete their current runtime engine and reinstall oldest to newest.

- Rebuild and redistribute all executables when a new version of LabVIEW is released (and hope there are no other compatibility issues).

These options seem to be confusing and inconvenient when distributing executables that are used by customers to demo your product.

Is there a specific reason to require the runtime engines to be installed in order?

Is this just a bug or is this the way NI intends it to work?

Thanks!

[rolfk]

---

@macski06 wrote:

Is this still the only way to install an older run-time engine?

This leaves 3 options when working with multiple people using varying versions of LabVIEW and/or the runtime engines:

- Build all programs for multiple runtime engines and find out which version will be necessary for each person using the executable.

- Tell people who have a newer version of LabVIEW that they will need to delete their current runtime engine and reinstall oldest to newest.

- Rebuild and redistribute all executables when a new version of LabVIEW is released (and hope there are no other compatibility issues).

These options seem to be confusing and inconvenient when distributing executables that are used by customers to demo your product.

Is there a specific reason to require the runtime engines to be installed in order?

Is this just a bug or is this the way NI intends it to work?

Thanks!

---

You need to give more specifics about version you try to install and such. Generally the installation order of old to newest applies if you install the development system, but there shouldn't be any problem installing a LabVIEW runtime engine when a newer is already installed too on that machine.

Maybe you are talking about drivers rather than the runtime engine. Drivers can be only installed in one version on a machine, but unless there is a huge difference between time of release of LabVIEW version and time of release of driver version, a newer driver will work with an older LabVIEW executable.

[altenbach]

I never needed any special order for the run time installers, so there is clearly something wrong if it won't let you install 7.1.1.

(There were similar discussions in the past, but I have trouble finding them).

You might only get an error like this if you would e.g. try to install 7.1 over 7.1.1, for example. Here only one can exist.

[macski06]

Unfortunately I don't have too many details. I have had several versions of LabVIEW for several years and have not encountered this myself since I am always upgrading to the latest development system. I was hoping to find someone who's had this problem since I can't recreate it myself.

In the past couple years, however, I have had multiple customers mention similar messages to the one mentioned above: "It says installation aborted a higher version of the product is already installed." They only way they were able to fix it was by deleting the newer run-time engine and then re-installing them in order. I was also curious if it made a difference whether they installed the standard vs. the minimum version of the run-time engine.