When loading Labview 6.1 program I get "OS cannot run %1" message on Windows XP

[hall]

When loading a Labview 6.1 vi using Windows XP OS machine, I get "The operating system cannot run %1" message . This appears several times and if I click OK each time, eventually the vi is loaded. How can this be fixed?

[LarsRoe]

It sounds like something is configured incorrectly with the ".vi" associations in XP. Were you opening it by double-clicking? Try opening it from LabVIEW (File >> Open), and see if that gives an error.

[Jeremy Braden]

I had a simmilar problem. I kept getting a message that went something like, "The file you are about to download may contain harmful material" whenever I tried to open a llb from Windows explorer. The menu repeated until I canceled the action. My llb was fine when I opened it in LabVIEW. The fix, as the previous poster suggested, was to right click on a .llb >> open with >> Labview and click on the "always open with this program" button.

[hall]

I get the same error even if I open the file from Labview

[Jeremy Braden]

It sounds like the VI is corrupted. The next time you open the VI, copy its diagram to a new VI and save. This way you can perserve your code and isolate the bad VI.

[hall]

When I save changes to the Vi, I get a message "Do you want to save the changes to AI Hardware Config.vi". No matter which way I answer it, I still have the original problem. I can't even find this vi in my code. Looks like it might be time to try a reinstall of Labview.

[LarsRoe]

Have you recently upgraded or uninstalled/reinstalled LabVIEW? It doesn't make sense that you would be prompted to save AI Hardware Config.vi since it comes with LabVIEW. You could be looking at an old VI with a newer version of LabVIEW.

[hall]

Yes. I was running LV 6.1 on a Dell GX110 W2000 Professional when I wrote the code. Our company recently installed Dell GX260 with XP and they may have done an image transfer from the older computers rather than a reinstalling software. Since the vi comes with Labview, a reinstall may solve my problem. On top of all this, I am going to need to run the executable on a W98 system.

[hall]

Uninstalling and reinstalling solved my problems

[LarsRoe]

Good to hear. I'm guessing it had to do with file associations: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/programmersguide/shell_basics/shell_basics_extending/fileassociations/fa_intro.asp