Need the following .vi9(s)

[Ben]

My LV 6.1 machine with a full compliment of add-ons fails to find those VIs when searching.

I vote those are all custom VI or they were loaded as part of a some third party add-on.

Ben

[Bebeto]

I can assure they are not custom, they must be included in a toolkit

[Ben]

---

Bebeto wrote:

Hello,

First of all, this is the message I get when loading the VI:

An error ocurred loading VI"binRead.vi".

LabVIEW load error code 10: VI version (5.1.1) is to old to convert to the current LabVIEW version (8.6.1)

Now this is the path I get:

Loading:

C:\Documents and Settings\montoye\Desktop\HAWK GUIs\Strip Chart Source\HawkStripChart.vi\binRead.vi

 Searching:

 C:\Documents and Settings\montoye\Desktop\HAWK GUIs\Strip Chart Source

---

I have never seen a spec like that.

A VI inside a VI?

If my coffee was fully functional, what would that tell me?

Ben

[smercurio_fc]

At this point I am thoroughly confused. I thought we were dealing with LabVIEW 6i VIs, now it seems we're trying to load LabVIEW 5.1 VIs in 8.6, and we're also apparently dealing with VIs inside of VIs.

[Bebeto]

well the LabVIEW version used was 6i, still the files can be from a previous version, and yes they are VIs inside the general VI

[Ben]

Just to rule it out I tried saving a VI into a llb and then from Windows. renamed the llb to just .VI and a caller was still able to find the sub VI inside the VI!

So try browsing into that "hawk" file to see if THE CUSTOM Vis are in there.

Ben

[billko]

It's Colonel Mustard in the Study with the Candlestick.  😉

Even if it was from a toolkit, who would put something like that on their desktop??? 😮

I think you'd better find out who this "montoye" user is and see if you can find the folder.

Bill

Edit:

Even if you're using the same computer, if you're logged in as yourself (not "montoye") and you don't have admin rights to the computer, you won't be able to access that folder.  FYI

Message Edited by billko on 08-26-2009 09:39 AM

[Ben]

---

Ben wrote:

Just to rule it out I tried saving a VI into a llb and then from Windows. renamed the llb to just .VI and a caller was still able to find the sub VI inside the VI!

So try browsing into that "hawk" file to see if THE CUSTOM Vis are in there.

Ben

---

Image showing what I tried to describe above.

Ben

[Bebeto]

the VIs are not there, llike mentioned before I had the same problem with another Vi JtfaEngine.vi and it turned out to be inside an obsolete library. Then the people from NI converted the file for me to be readable in 8.6.1

[billko]

---

Bebeto wrote:
the VIs are not there, llike mentioned before I had the same problem with another Vi JtfaEngine.vi and it turned out to be inside an obsolete library. Then the people from NI converted the file for me to be readable in 8.6.1

---

That just doesn't make sense.  How can NI convert something that isn't there?  Do you mean the library had dependencies on VIs that no longer exist?  Anyway, the files that have problems are on somebody's dektop where they shouldn't belong.  That in itself tells me they are third party (custom) VIs, which is why everyone responding is having a difficult time supporting you.  NI doesn't install stuff to the desktop, BTW.  😉

Bill