LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with NI Developer Suite silent installation

How to silently install NI Developer suite and device drivers with custom items. NI Developer suite is been distributed among 3 disks. How to avoid user interaction and install products from all 3 disks.

 

Also, when i try to install Device drivers in silent mode, it is not getting installed at all. i.e. i am getting the startup window as below but nothing happens after that. It is loading around 25% and suddenly gets closed.

 

Device drivers.png

 

Command that i used for Device driver is "setup <spec file path> /qb /acceptlicenses yes".

 

Am i doing anything wrong? 

Anand kumar SP
Senior Project Engineer
Soliton Technologies Pvt Ltd
0 Kudos
Message 1 of 6
(3,203 Views)

So as you probably already noticed, that main setup installer on disk 1 is just an installer for installers.  You pick the applications you want to install and it goes an installs them one by one.  So I doubt there is any silent switches to the main setup on the root of disk 1, but there are silent installers for each subcomponent that gets installed.

 

Check out the Distributions folder, it will contain each of the NI products that can get installed.  So instead of using that main setup, copy each component you want installed from the Distributions folder, and then FOR all folders run their respective setup.exe with the silent switches.

 

Here is a document describing the silent options.

 

EDIT:  This document looks useful too.

0 Kudos
Message 2 of 6
(3,186 Views)

Thank you for your suggestion. Currently i am invoking each setup individually as you said. This is fine in case of LabVIEW toolkits but not for drivers. For device drivers, under products folder i am seeing a huge number of folders. It is difficult for me to segregate each of the product i need. Any idea/suggestion for this would be of more helpful for me.

Anand kumar SP
Senior Project Engineer
Soliton Technologies Pvt Ltd
0 Kudos
Message 3 of 6
(3,164 Views)

@AnandkumarSP wrote:

Thank you for your suggestion. Currently i am invoking each setup individually as you said. This is fine in case of LabVIEW toolkits but not for drivers. For device drivers, under products folder i am seeing a huge number of folders. It is difficult for me to segregate each of the product i need. Any idea/suggestion for this would be of more helpful for me.


Trial and error my friend.  On a virtual machine that has been taken with a snapshot before installing any NI software.  WireBird Labs describes the same type of thing you would have to do to get your drivers working.

 

https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-labview-run-time-engin...

 

He broke it down into each installer and basically installed each component one at a time, then tried his application.  If it didn't work, he installed one more component, until it worked.  Then he went backwords removing components until it stopped working.  This gave the idea of what was needed and what was not.

 

After you find all the installers you want to run, I suggest making an installer for the installers, which runs each one silently one at a time.  To do this in the past I've used INNO Setup.  Optionally assisting in making this installer is another tool called ISTool.  It usually is a bit of work but when you get it working it is nice to have a professional installer that does as it should and is a simple experience for the user.

0 Kudos
Message 4 of 6
(3,145 Views)

Atlast, got the answer for my problem. The silent installation did not work because I have checked .NET Framework support in the silent installation spec file. But my PC didnot have all the versions of .NET Framework. Once I removed these support from spec file, I am able to install required Device Drivers in silent mode.

 

Silent Installation error.png

Anand kumar SP
Senior Project Engineer
Soliton Technologies Pvt Ltd
0 Kudos
Message 5 of 6
(3,058 Views)

Glad you figured it out.  I'll be sure and keep that in mind in the future.  I wonder if NI could provide some kind of feedback to let you know that this is why the install paused.  Maybe a debug log showing where the install had issues.

0 Kudos
Message 6 of 6
(3,039 Views)