After reboot, Labview looks for RTE 7.1 (RTE 8.2 installed)

[Mattjk]

I started developing software using Labview 7.1.  Mid way complete I decided to switch to Labview 8.2.  Now everytime I reboot, I get a Windows installer asking for the Labview 7.1 runtime engine.  I re-installed Labview 7.1 but I keep getting the installer asking for this runtime engine.  Eventually after clicking cancel about 10 times, it finds an engine (not sure which one) and runs the exe.  This exe is on a PC running Windows XP in a factory, controlling a machine.  I need to fix this problem for the customer to be happy.  Is it possible that one of the VIs I used in 7.1 is now in 8.2's code but needs the old engine to work?  How can I fix this problem?  Note that I'm not using any VIs in 8.2 that don't already exist in 7.1. (stupid mistake to use 8.2).

Hopefully someone can help me.

Matt Koebel

Technologist

[mikeporter]

Apparently Windows something got messed-up during the installation process. If it were me I think my first step would be to backup the source code and uninstall all National Instruments software. After the uninstall, reboot and run a registry cleaner like CCleaner (free download) to remove any remnants of old installations. Note that before it cleans up issues that it finds in your registry it will ask you if you want to back up the things that its removing - say "Yes". If necessary, run the scan repeatedly until it reports that it found no additional issues.

Finally, reboot again you should not get the message.

Now reinstall all the NI software. If the latest version of your code is in LV8.2 just install that (actually 8.2.1).

Oh yes, the most important thing: Be sure to do all of this from an administrator account.

Keep us posted on how you are getting on.

Mike...

PS: Looking back on what I wrote it occurs to me that perhaps it might be worth a try to download CCleaner and running it before you do the uninstall. It's probably a long shot, but it's clean-up process might fix whatever is causing the trouble. If it works you have saved a bunch of time. If it doesn't you haven't lost much.

[TreyB_NI]

It sounds like something is invoking the LV 7.1 RTE.

Here's some questions that will help me understand your problem:

1.  When you say you reboot, are you referring to your development PC?  Is the executable running at startup, or is this just a general windows installer popup asking for LV RTE 7.1?
2.  Is your application an installer, and if so did you install it to the development PC?
3.  When you installed LabVIEW 8.2, did you install the device driver CD or install NI-DAQmx 8.5?  Some of our older revisions of software, such as Measurement and Automation Explorer (MAX), would use the LV RTE 7.1.  The NI-DAQmx drivers include MAX.
4.  If you go into MAX (Program files>>National Instruments>>Measurement...) now and expand the software section, what versions of the following do you have?
a.  LabVIEW Run-Time (you can have multiple)
b.  NI-DAQmx

If the error occurs when you try to run the executable, I would mass compile your project.  Starting in LabVIEW 8.0, applications are now made through a project explorer whereas LV 7.1 did not.

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/aa97c01071d7cf678625695100582f40?OpenDocument

Message Edited by Trey B on 05-24-2007 02:23 PM

[Mattjk]

OK people, I figured it out.  First off, my executable was starting at start up.  There is another program that also starts up.  It is a database program which keeps track of data from the labview executable.  I didn't write this program and I don't know what all it uses but I'm sure it uses a data socket and a small program written to take control of the serial port (take control away from MAX).  This database program was lookikng for the runtime engine (7.1.1).  The problem occured when I moved the start menu shortcuts to labview (and all tools) to a sub directory.  The problem was solved by simply putting back all the shortcuts to their origional location in the start menu.  I'm not sure why there is a reference to the start menu shortcut.  Anyway, all is ok now.

Thanks for the help.

Matt Koebel

Technologist