Can LV7.1 co-exist with LV6.1?

[wilvil2000]

I am about to install LV7.1 in a Win2K machine alongside with LV6.1 and LV5.1.1. I asking anyone that have had any problems with LabVIEW "getting confused with libraries, windows registry, NI Licensing, shared components, etc.." to please comment on this. I currently do my main development on LV6.1 and can't afford to have it hicupp on me now.

Wil

Thank you.

[EdDickens]

I currently have LabVIEW 5.1, 6, 6.1, 7.0 and 7.1 installed.

The only problem I have is that only one of the versions can be registered to open a VI when double-clicked from explorer. This can be solved by adding all the LabVIEW versions manually to the file types that can open a VI. If this is what you mean when you said "getting confused with libraries", it's something you'll have to look out for.

There's a line you can add to the LabVIEW ini file that will let you specify what version you want registered to open files when double-clicked. Add the line "RegisterExtensions=False" without the quotes to the versions you do not want to run when you double-click on a VI. Change it to True in the one version you do want to open on a duoible-click. Unfort
uately, LabVIEW does not have the capability to look at file to see what version it is and then launch the correct one.

Of course if LabVIEW is already open, whatever file you double-click on will be opened in that version.

The main thing that might cause problems is NI-DAQ. I think the best way to avoid problems here is to first uninstall your current NI-DAQ drivers before installing LabVIEW 7.1 and the NI-DAQ 7.2 that ships with it.

Ed

[Wiebe@CARYA]

Just to add to the excellent answer, you can also have different versions
running at the same time. Unfortunately, you cannot copy paste to/from
different versions.

Regards,

Wiebe.

"Ed Dickens" wrote in message
news:506500000005000000F49C0100-1079395200000@exchange.ni.com...
> I currently have LabVIEW 5.1, 6, 6.1, 7.0 and 7.1 installed.
>
> The only problem I have is that only one of the versions can be
> registered to open a VI when double-clicked from explorer. This can be
> solved by adding all the LabVIEW versions manually to the file types
> that can open a VI. If this is what you mean when you said "getting
> confused with libraries", it's something you'll have to look out for.
>
> There's a line you can add to the LabVIEW ini file
that will let you
> specify what version you want registered to open files when
> double-clicked. Add the line "RegisterExtensions=False" without the
> quotes to the versions you do not want to run when you double-click on
> a VI. Change it to True in the one version you do want to open on a
> duoible-click. Unfortuately, LabVIEW does not have the capability to
> look at file to see what version it is and then launch the correct
> one.
>
> Of course if LabVIEW is already open, whatever file you double-click
> on will be opened in that version.
>
> The main thing that might cause problems is NI-DAQ. I think the best
> way to avoid problems here is to first uninstall your current NI-DAQ
> drivers before installing LabVIEW 7.1 and the NI-DAQ 7.2 that ships
> with it.
>
> Ed

[Ram2003]

I have 6.1 and 7.0 coexist in my laptop. My original application developed in 6.1 could not be executed in 7.1 without modifications in visa serial configure VI. The new serial driver visa configure connection pattern is different in 7.0. But this was just a minor modification.
I installed 7.1 today in the same laptop today, so far no problems noticed.