Jeff,
You're right. All I had to do was delete the newer CVI runtime files from
the Windows\system32 folder and then I could install the old runtime. By
converting my app's UIR to a TUI and editing it to remove the bitmaps and
changing CTRL_MENU_RING_LS to CTRL_MENU_RING, I was then able to build and
run my app under CVI 5.5. This allowed me to confirm that my original
problem still happened under 5.5 so the problem had to be in my code.
I'm glad you pointed out that the runtime installer won't overwrite an
existing runtime if its a newer version. I was really "barking up the wrong
tree" by looking in the Windows registry.
Thanks!
"jlaney" <x@no.email> wrote in message news:207882@exchange.ni.com...
> Hello,<br><br>If you are trying downgrade your CVI runtime engine you need
to manually go to the Windows\System32 folder and remove everything CVI
related. This includes files, such as cvirte.dll and folders with cvi in
the name. Then you should ba able to install an older runtime. What is
happening is the older runtime is checking these files and finding a newer
version than itself installed and not allowing you to install an older
version over a newer one.<br><br>Anyways, you should be able to use the CVI
7.0 runtime engine since the CVI runtime engine is fully backwards
compatible. If you are having troubles with this, I would reinstall/repair
the CVI 7.0 runtime engine. <br><br>Sorry for the late reply, been out for
a while.<br><br>Jeff<br>NI