LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI 2009 RTE eval mode

I've installed CVI 2009 on a PC with CVI 9.0.1 and 8.5 installed.

 

I'm still trying to resolve a licensing issue with our VL agreement for CVI 2009 so it is unactivated and in eval mode right now since our MStudio 8.6 license doesn't appear to be covering CVI 2009.  CVI 9.0.1 is running under the MStudio 8.6 license.  Our NI license support guys are calling the NI license support guys Smiley Sad

 

HOWEVER as we all know the CVI RTE was forced to CVI 2009 revision.  If I build a distribution in CVI 9.0.1 it now uses the CVI 2009 RTE.

 

So the million dollar question is:  Does this CVI 2009 RTE contain a limitation on runtime or eval period?  If I deploy an app built in CVI9.0.1 with the CVI 2009 RTE from an eval install will it stop running at some point?

 

If not, how do I recover the CVI 9.0.1 RTE?  Uninstall CVI 2009 and then re-install the 9.0.1 RTE?

 

What a hassle.  I never have liked the way NI has CVI silently coerce the RTE version up like this.  At least I'm wise to it now.

 

Menchar

0 Kudos
Message 1 of 5
(3,946 Views)

Does this CVI 2009 RTE contain a limitation on runtime or eval period? 

- No.

 

If I deploy an app built in CVI9.0.1 with the CVI 2009 RTE from an eval install will it stop running at some point?

- No. 

 

0 Kudos
Message 2 of 5
(3,919 Views)

Thanks Mohan.

 

I was worried that I had created a mess with the CVI 2009 install.

 

I see the dist kit size ballooned again - I suspect due to the CVI 2009 RTE, it must have gotten even bigger than the CVI 9.x RTE.  What was a 65 MB dist kit(!) is now 110 MB(!!!!).  

 

Menchar

0 Kudos
Message 3 of 5
(3,910 Views)

Woops -

 

The dist kit I made in CVI 9.0.1 that includes the CVI 2009 RTE won't install on one of my targets Smiley Mad

 

The installer hangs up when "Currently installing NI VC2008MSMs x86 Part 1 of 10" ...

 

Is this something specific tothe CVI 2009 RTE?

 

I did compile the app (a DLL and an exe) using the MS Visual C++ 8.0  compiler (which is the compiler used in VS 2005).   I wonder if this is an attempt to install support SW for the VCPP executables?

 

The same dist kit installed all OK onto at least two other PC's.

 

Thanks.

 

Menchar

Message Edited by menchar on 12-17-2009 09:56 AM
0 Kudos
Message 4 of 5
(3,902 Views)

We tried installing when Visual Studio 6 was not running and everything worked Smiley Happy

 

I am so glad this wasn't a problem with the RTE.

0 Kudos
Message 5 of 5
(3,891 Views)