12-04-2001 09:22 AM
12-04-2001 09:29 AM
12-04-2001 09:55 AM
LabVIEW, C'est LabVIEW
03-07-2002 08:54 AM
10-24-2003 11:03 AM
03-09-2011 10:41 PM
I tried to use the .vi from the .Exe by renaming it to .llb. But the LLB manager is unable to open the .llb file. I use Labview 2010. Any idea which Labview version should i use to make this possible.
03-09-2011 11:06 PM
This only worked for LabVIEW 7 and earlier. Up to 2009 you could use a compression program to view the executable's list of files, and you could extract them, but that wouldn't get you the code since the block diagram is stripped once the executable is built.
01-12-2015 02:32 AM
Hi,
I intended to use Labview 7.2 (run on Windows XP) to modify an old Labview .exe file (written in 2004, possibly created by Labview 7.x or earlier).
I tried to rename the .exe file to .llb, but still could not access the .vi files.
Does anyone know how to do that? Do I need any programs other than the Labview?
Thanks in advance.
- timers
01-12-2015 03:05 AM - edited 01-12-2015 03:11 AM
First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.