Silent install LV RTE2009 with Spec file

[Coq_Rouge]

The misexec.exe is a Microsoft provided file. On my computer it is located in c:\windows\system32\ I do not know if it need any support DLL(s). If you look at the picture from Andrey, you will find the full path in the lower right corner for the RTE msi file.

[Andrey_Dmitriev]

Hi, Battler,

 I have read this topic twice ans still can't understand what your final goal is?

So, if you need to deploy RTE together with your application as single installer, why do not simply select appropriate check mark in the additional installers list (see screenshot above)?

If you need to run setup silently, then just specify appropriate switches like setup.exe /q /AcceptLicenses yes, then it will be installed without messages.

I think you are looking for too complicated solution for the simple problem.

Andrey.

[Coq_Rouge]

I think Batty want to slim down the installer size. So he is trying to sneak in the RTE installer with no extra add on. I would be careful with this. Because it it very hard to predict a setup on a unknown computer. Some support files may be missing, and the installation will not work. And the customer will not be happy

[Andrey_Dmitriev]

---

Coq Rouge wrote:
I think Batty want to slim down the installer size. So he is trying to sneak in the RTE installer with no extra add on. I would be careful with this. Because it it very hard to predict a setup on a unknown computer. Some support files may be missing, and the installation will not work. And the customer will not be happy

---

Then I can understand this. The best case follow to scenario with packing all Run-Time files from <NI>\Shared\LabVIEW Run-Time\2009\*.* to the executable directory, then start it and step by step remove "overhead" files and check that the application still working. I have done this with LabVIEW prior 8.6 and it works, but with LV2009 its may be tricky, because Microsoft VC RunTime also required. Another way - go to \Products folder and install necessary products separately. After some hacks it should work. And the application should be goot tested after such hacks.

Andrey.

[battler.]

Thank you for explaining that the msiexec.exe is a Microsoft app.

So in the installation builder the exe I need to run after install is this msiexec.exe?  How do I know where it is on the target PC?  How do I tell it to load the LV RTE msi file?

I went to the path indicated in the installation builder (shown by Andrey).  This is what I found:

I don't actually see an msi file in the folder.  What do I need to include in the project?  This msiexec.exe and the RTE?

Thanks,

Battler.

[Ashish_Naik_NIUK]

Hi battler,

I am, like others still wondering what you are trying to acheive? I share Coq Rouge's sentiments, about trying to "sneak" the installer. As this in the long run, can cause you issues as mentioned.

The easiest way to deploy your NI app is by either an .exe or .msi file. Do you have LabVIEW Professional or the Application Builder? With regards to silently installing, have a look at the following two articles. This may help you. Some of this information has been mentioned previously.

KB 2LNEFG09 Silent Installation of the LabVIEW Run-Time Engine
LabVIEW 2009 Help file : Installing LabVIEW-Built Installers Silently

The Latest version of LabVIEW Run-Time can also be downloaded here

I hope this is of some help.

[battler.]

I am merely trying to silently install the LV RTE following installation of my app.  I don't want my users to have to accept the NI licence agreement.  That is as simple as it is.

I have read and tried to apply the KB articles you have indicated.  The reason for this thread is that I could not get it to work.

Judging by some of the suggestions in this thread the KB articles are incorrect.  The KB articles do not mention this msiexec.exe.

You've pointed me to the LV RTE.exe which requires self-extraction.  What do I need to include in the Project?  Do I extract all the files and include them?

The Installation builder does not recognise .msi files (which is what this LV RTE.exe contains following extraction).

[Coq_Rouge]

---

battler. wrote:

I am merely trying to silently install the LV RTE following installation of my app.  I don't want my users to have to accept the NI licence agreement.  That is as simple as it is.

I have read and tried to apply the KB articles you have indicated.  The reason for this thread is that I could not get it to work.

Judging by some of the suggestions in this thread the KB articles are incorrect.  The KB articles do not mention this msiexec.exe.

You've pointed me to the LV RTE.exe which requires self-extraction.  What do I need to include in the Project?  Do I extract all the files and include them?

The Installation builder does not recognise .msi files (which is what this LV RTE.exe contains following extraction).

---

Why did you not say so at your first postings

OK here is the thing to do. Locate the setup.ini, it is in the same folder as setup.exe then you build the application. Open the file with notepad. Then you toy around with the dialog settings under [Dialogs]. This is my favorite clean and nice

[Dialogs]
UserInfo=0
FeatureInfo1=1
SingleDirectory=0
InstallationType=0
FeatureTree=0
License=0
License2=0
NICertificate=0
ConfirmStart=0
End=1

[battler.]

Thanks Coq.

I need to test that the 2009 RTE is still installed when the dialog is not shown.  Does suppressing the dialogs still mean that the NI licence agreement is accepted?

Do you know how to uninstall the RTE (not on my development machine - as I dont think this would work)?  The LV 2009 RTE does not appear in the Programs list.

BTW I noticed in the setup.ini an entry at the very bottom:

[SilentInstallRequirements]
MustAcceptLicenses=1

Should I be setting this to =0?

[Coq_Rouge]

Sorry I can not be of any more help. You have to test. I do not have any computer that is free from some sort of labview software. You have to find out by yourself. But I am 99% sure the setup is OK since it follows the same script

I also think by using the LV RTE you have De facto agreed to all terms. I agree that the standard installer has to much of "nag screens" But I am happy with my modifications in the setup file

If I am wrong please make a posting