unable to open cvirte but files are there

[KenbobC]

When I try to run my CVI gui on a new Win7 machine, I get the message "Unable to open C:windows\System32\cvirte\bin\cvirte.rsc".  But when I look in C:windows\System32, that folder and files are there.  I re-installed CVI/RTE 2013 SP2 just in case, but get the same result.  Tried running as an administrator, but get the same thing.  Probably something simple, but thanks for any advice.

[LuisG]

Assuming you have a 64-bit version of Windows, the CVI ADE should really be trying to load c:\windows\syswow64\cvirte\bin\cvirte.rsc.

The error message that you're seeing would be misleading in this case because, like most 32-bit programs, CVI really is trying to load it from c:\windows\system32, and is relying on the 64-bit OS to redirect the request to the syswow64 location.

Make sure that the syswow64 location exists in your computer. If it does exist, reboot your computer to make sure that some ghost process isn't holding a lock to that file that would prevent it from being reopened.

Luis

[KenbobC]

Thanks Luis,

I am running Win7 64bit.  c:\windows\syswow64\cvirte does exist, with not quite as many files below it as the system32 version, though both do have \bin\cvirte.rsc with the same date (6/25/2014 at 1am)

I restarted the machine this morning, get the same error message.  any more suggestions?

Ken

[LuisG]

Are you sure it's not the other way around? The files in system32 should be a subset of the files in syswow64, not the other way around. The syswow64 folder has cvirt4.rsc and msrt4.txt, which are not expected to be in the system32 folder. All other files should be the same.

Assuming the files are installed correctly, then this is going to be a bit trickier to figure out. Do you still have the CVI ADE working successfully in your old computer? If so, can you build a CVI program in that computer (a simple example from the CVI examples folder should do), then copy that program's .exe along with any other needed files, such as .uir files, to the problem computer and try to run the .exe? This will help us narrow down the problem to the ADE or the run-time engine.