LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW exe from 1998

Solved!
Go to solution

Oh boy! This is a fun one. I would like to just view a LabVIEW program made in 1998. I don't have source code (yay!) and when I run it, I get the virtual instrument icon on my taskbar for a few seconds, then it closes. Any thoughts on where to even start here? I downloaded the oldest runtime engine I could get (2009) and it did nothing. I don't even know how to start troubleshooting this without any errors or anything. There are also two dll's that came with the program I put in the same folder thinking maybe it couldn't find them.

 

 

Message 1 of 13
(1,715 Views)

You may be in luck since the LabVIEW version is so old.  I've never tried any of this but I remember hearing about LabVIEW EXEs being easy to hack since they were really just zipped LLBs or somesuch.  A quick search led me here:  Solved: Deconstructing an LabVIEW Application - uncompressed access to files - NI Community

 

See where that takes you and hopefully someone else who has actually done this will add to the thread...

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
0 Kudos
Message 2 of 13
(1,688 Views)

Solved: decompiling 2009 executable - NI Community

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
0 Kudos
Message 3 of 13
(1,684 Views)

@NIquist wrote:

Solved: decompiling 2009 executable - NI Community


It's not that simple. 1998 is at most LabVIEW 5.0, and possibly LabVIEW 4.1 (5.0 was released in February 1998 and may have been used for this program, or it may not).

You may be able to get it to run on Windows XP as it is possibly a Windows 95 version but it could just as well be compiled for Windows 3.1 and that can not run on any NT kernel.

 

Yes those executables were in fact an LLB tacked onto an executable stub. But that LLB still had only the front panels that were ever shown, and no diagram at all for any of the VIs in it.

 

 

Rolf Kalbermatter
My Blog
Message 4 of 13
(1,631 Views)
Solution
Accepted by topic author StevenD

Hi,

 

Can you post the exec here? Still have some old versions running in a virtual machine. 

 

Kees

0 Kudos
Message 5 of 13
(1,595 Views)

@rolfk wrote:

@NIquist wrote:

Solved: decompiling 2009 executable - NI Community


It's not that simple.

 


Ah, I figured that would be too easy.  I didn't realize which version we were talking about either.  My very first LabVIEW was version 5 and I'm OLD.  Brings back memories of convoluted stacked sequence structures riddled with sequence locals.  Like worms in a rotting apple...  Good times. 😋

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
Message 6 of 13
(1,549 Views)

You may try to run that exe from command prompt and post the error message.
another question is, What is your os that run the exe? 32-bit or 64-bit?

please set this as ANSWER or KUDO this post, if it help you.


0 Kudos
Message 7 of 13
(1,516 Views)

I have tried from a command prompt. It doesn't return any information. A LabVIEW icon shows up on the taskbar for a few seconds, then disappears. No warnings, errors, ect. I'm running Windows 10, tried all the compatibility options, XP, 98, 95. Always same behavior.

0 Kudos
Message 8 of 13
(1,482 Views)

Even if it is somehow actually trying to run, it may be making calls to the OS or hardware that are no longer allowed.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 9 of 13
(1,476 Views)

@StevenD wrote:

I have tried from a command prompt. It doesn't return any information. A LabVIEW icon shows up on the taskbar for a few seconds, then disappears. No warnings, errors, ect. I'm running Windows 10, tried all the compatibility options, XP, 98, 95. Always same behavior.


When you say "no warnings/errors", have you checked the Windows event log?  A lot of times when something dies silently, a log entry will be made there in the "Windows logs\Application" or "Windows logs\System" log category.

Message 10 of 13
(1,469 Views)