Garbage text in ConfirmPopup

[LuisG]

Hi Rick,

Thanks for the reply. Unfortunately, everything seems perfectly normal with your current installation. This shouldn't really be happening, and I'm quite puzzled by it.

If re-installing CVI in the affected PC won't be too disruptive for you, you can go ahead and try it -- but do make sure that you uninstall the CVI RTE ("NI LabWindows/CVI Run-Time Engine 2010") from Add/Remove Programs. Uninstalling just the ADE won't have any effect. -- But I have to say that I can't see any problem right now that re-installing would fix, since the relevant files that you have already seem to be correct.

If re-installing doesn't fix it, the next step would be for me to send you a logged version of cvirte.dll, so that we can continue debugging further. Let me know if you'd like to do this instead of (or in addition to) re-installing.

Luis

[ryk]

Hi Luis,

We have done a complete un-install of the NI environment (include explicitly removing the RTE from Add/Remove Programs) and reinstalled 2010 with the same results. 

I am not sure what the "logged" version of the cvirte.dll will do, but maybe its time to try it.  How do we proceed?

Thanks,

Rick Blum

[LuisG]

By "logged", I meant a version of the CVI run-time with some diagnostic messages that might shed some light on what is going on. To try this out, do the following:

1. Make a back-up of c:\windows\syswow64\cvirte.dll.

2. Take the cvirte.dll that I'm attaching and copy it to c:\windows\syswow64. You might have to close all instances of CVI before you're allowed to replace cvirte.dll.

3. In your system registry, create the following value:

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\CVI Run-Time Engine\cvirte

Value: statelogfile

Data: <the full path of a log file that CVI will create>

4. Make sure you build a 32-bit version of your program (it doesn't matter if it's a debug or release configuration) and run it, either inside or outside the CVI environment.

5. After the program finishes running, look for the file that you specified in step 3. It will probably have some numbers appended at the end of the file's basename.

6. Attach the file here.

7. Restore your back-up of cvirte.dll

Luis

[ryk]

Luis,

Hi, sorry for the delay in getting back, its been busy here.  We finally re-imaged the PC (from the OS up), the problem no longer exists.

This particular PC has been used as a platform for all kinds of configuration testing as we prepare for a factory wide migration from Windows XP to Windows 7 and onto a new domain with new rules.  It no doubt had some mis-configured registry entries resulting in abnormal behaviors, including the incorrect button label displays we were seeing in CVI. 

Thanks for your persistent help.  We did not attach the log file as it would contain information potentially misleading due to the mis-configuration of the PCs OS during the problem.

Thanks,

Ryk