Runtime Engine 6.0.2 doesn't have an executable?? Did I install this wrong...

[Phredrick Dobbs]

One of my superiors surprised me by showing up with Labview 6.0.2 (we had 5.0.1). Yay!

However, since we don't have the application builder or the professional development package, we use the run-time engine.

I downloaded the 6.0.2 runtime engine from:

http://digital.ni.com/softlib.nsf/16a19f446db24ce5862568d2005b971c/d5f11a64a905db27862569ec005e31e2?OpenDocument

I installed it, but it didn't apparently create any sort of executable, although it did make a runtime folder with plenty of .DLLs. What do I need in order to run 6.0.2 .vi files?

-Dobbs

[Shan Pin Koh]

Well, the run-time engine is not an executable. The VI applications created from Application Builder would have be an executable (.exe).

I am guessing (please correct me as I am unsure about the terminology) that the run-time engine provides the symbols, the controls, the indicators, the arithmetic functions, etc in order for your VI executable to work properly.

I hope that somehow answers your question. Regards,

Shan Pin Koh

[Phredrick Dobbs]

That's rather peculiar. The 5.0.1 runtime engine from

http://digital.ni.com/softlib.nsf/16a19f446db24ce5862568d2005b971c/e7df786664269134862566390070aebb?OpenDocument

WAS an executable. I'd click on a VI, and it would open it using this program. So the "Test Executive Run Time System" is an executable, but just the "run time engine" is not?

Is there an equivalent program out there that is also free? We don't have the app. builder as far as I know.

Do you need either the application builder or the professional version in order to distribute a .vi? I'm trying to move it from this development machine to a laptop without labview.

Thanks,
-Dobbs

[Shan Pin Koh]

I am not sure how it was done in 5.0.1 so I can't comment on that. I know that since 5.1.1, the runtime engine is nothing but .dlls.

There is another way. Have someone create a generic EXE file. Then run this generic EXE. (What I mean by generic is that you do not specify any VI when you create the application.) It will prompt you to select a file when you run the executable. You can then browse to your VI and have it run that way.

I am not sure if you'll need any license by doing it this way... What I'm suggesting here is a way for you to have an executable like what you've described. Maybe you could talk to a NI application engineer or your sales person to have them create you the generic EXE.

I am not sure about software distribution. Y
our sales person would be the one that you talk to about that. The NI Developer Suite or LabVIEW PDS is something to consider if you're planning on distributing your applications.

Thanks.

Shan Pin Koh