I have trouble in building stand-alone application, "you must intall Labview run-time engine on any computer on which you want to run this application"

[Dr._Imad]

since you have the runtime engine 7.0 already installed,  check the access rights on the  ..\\national instruments\shared folder.  the operator should have full access rights to this folder

[Sheldon_Stokes]

This brings up my biggest wish, which is to have real genuine stand-alone executables from Labview.  Having to install a multi-meg environment on each target machine isn't very satisfying.  If I could produce real stand-alone code, I'd uninstall my other compilers, and be a real happy camper.

Sheldon

[shoneill]

Are you trying to tell me that Visual basic and co are "stand-alone" executables?  What about the various VBRUN.DLL files to be found on any Windows PC.  Well I'll be darned if that's not the equivalent of a LV run-time.

The only difference is that Bill bundles THEM with his OS.

Do that with LV and the problem's solved.  Only problem is that they'd probably rather implement their own (inferior) version....

Hope this helps

Shane.

[altenbach]

---

@sheldon Stokes wrote:

This brings up my biggest wish, which is to have real genuine stand-alone executables from Labview.  Having to install a multi-meg environment on each target machine isn't very satisfying.  If I could produce real stand-alone code, I'd uninstall my other compilers, and be a real happy camper.

---

Well, we had this in LabVIEW 4 and it was not very satifying. Every executable was several megabytes, because it contained the runtime "inside". Now, there is a shared DLL containing all the common code and the executable can be very small. If you have more than one executable installed, you immediately win :).

(I you had followed the size inflation of the runtime engine over the years, you would not want to include that with every little program ;))

This is not any different with other code. If you distribute a fortran program, you need to provide dforrt.dll, etc.

Maybe in a few years LabVIEW executables will be so prevalent that the runtime is included in a standard OS install. Who knows? 🙂

[Dr._Imad]

At least the old style stand-alone executable (LV 5.0 and earlier ) should be made an option.  For many applications, the size of an execuable does not matter.

[Mark H]

Raghunathan,

Could it be that you have not installed NI-DAQ on your target machine?

Whilst the Application Builder can create an installer that optionally includes the LV Run Time Engine, but it does not install NI-DAQ.

NI DAQ has to be installed seperately - normally using the CD that comes with DAQ hardware, or download the (large) NI-DAQ from NI's web site.

You may also need to seperately install additional NI drivers for other hardware capabilities, such as GPIB and VISA if used.

Mark H.

[olivier66]

Hi

"Thank you all~

But the thing is I did include the run-time engine by checking the option in "advanced installer settings". Even with a simplest program, I still have the trouble."

I DONT HAVE THIS OPTION "advanced installer settings"

please could somebody explain me where to find it on labview 8

thank you so much

olivier

[altenbach]

In LabVIEW 8.0, things got a bit more flexible and you need to do two things. A built specification has now two parts:

1. Create an application
2. Create an installer

I assume you/ve done (1). For (2), just righ-click on the "Built specification" in the project window and select: "New...installer".

Here you specify what to install, including runtime engines, etc. Look for the setting under "additional installers".

[olivier66]

HI
thank you so much
even if I have already found that by myself after a couple  hours of research

thank you again