CVI Run-Time Engine 2010 on Windows 2000 OS

[byrd01]

I have an old PC running Windows 2000 SP4, on which I would like to run an application that will be developed in CVI 2010.  I'm trying to find out if an application developed using CVI 2010 can be run on the Windows 2000 PC with the CVI 2010 RTE installed.  From looking at the List of Run-Time Engine Versions, it appears that, starting with RTE v2009 SP1, Windows 2000 is no longer supported by the CVI RTE.  Should the 2010 RTE still work on a Windows 2000PC, or is it totally incompatible?   If RTE 2010 is incompatible with Windows 2000, can I use the v2009 SP0 RTE to run and application that was developed in CVI 2010?

Thanks for the help!

[LuisG]

From a pure functionality standpoint, the 2010 RTE might work in Windows 2000, depending on what exactly you would want to do. But it hasn't been tested in 2000, so it is very uncertain.

The biggest problem, however, is the installer. The RTE installer will not install in Windows 2000, and neither will any distribution that you build with CVI. So, you'd have to copy the DLLs and support files manually yourself, which might work for some libraries, but will be totally impractical

for other libraries.

Luis

[byrd01]

Thanks for the info.  So if I install the 2009 SP0 RTE which IS supposed to support Windows 2000, is there a chance that a release executable (not a full distribution) built with CVI 2010 (on a different computer) will run on the the Windows 2000 computer?  I just want to be able to copy an exe file that is built on a Windows 7 developement computer over to the older Windows 2000 computer and run it. 

I'd like to avoid maintaining 2 versions of CVI on separate computers.  I've already tried to have both v8.1 and 2010 installed independently on the same computer, but the older CVI 8.1 projects seem to get damaged when they are compiled on a computer that also has CVI 2010 installed.

[LuisG]

Unfortunately, you can't do that either. Any executable that you build on a given version of CVI requires a run-time engine that is of the same version or higher. Therefore, an executable that you build with CVI 2010 cannot run on a computer that has only the CVI 2009 RTE installed.

Unofficially, you might get it to work if you install the CVI 2009 RTE and you then manually copy the 2010 version of c:\windows\system\cvirte.dll, as well as the entire contents of the c:\windows\system32\cvirte folder onto the computer where you have the CVI 2009 RTE installed. If it still doesn't work, it might require some additional DLLs, but if you'd like to go down that road, yet you're still getting configuration errors, we should be able

to figure them out.

Concerning your comment about CVI 8.1 and 2010 side-by-side, this is supported. And it should not be the case that building an 8.1 project in 2010 would damage the project in any way. This is officially supported, and so it should work.

Luis

[byrd01]

Thanks so much!  I certainly appreciate your help in getting me all straightened out on the issue.  Ideally, we'd like to replace the old computer, however, we're using an old ISA based servo control board that costs over $3K to replace (not to mention the cost of the computer).  Unfortunately that's a deal breaker under our meager budget. 

---

@LuisG wrote:
 

Concerning your comment about CVI 8.1 and 2010 side-by-side, this is supported. And it should not be the case that building an 8.1 project in 2010 would damage the project in any way. This is officially supported, and so it should work.

Luis

---

I'll check this out again.  I had two separate projects that I built on a Windows 7 computer that has both LabWindows 8.1 and 2009 (I was incorrect before when I said it was 2010 on that particular computer).  When I tried to run them I got quite a few new library errors.  In one instance I simply opened up a backed up version of a project, re-built it, copied it over to a separate Windows XP computer that ONLY has v8.1 installed, and it would no longer run without lots of library errors.  If I recall correctly, I believe that I had to install v8.1 in compatibility mode in Windows 7.  I'm not sure if that causes any issues.  Maybe I just need to try and reinstall v8.1.