LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Silent install LV RTE2009 with Spec file

Hi there,

 

Has anybody made this work for LV 2009?

 

A few of the problems  have encountered:

 

1.  Where to get the right 2009 RTE?

 

I tried getting it from disk which included around 30 files and included them all in my project.  The main executable is an ".msi" file.  The LV installer builder recognises only ".exe" files as files you can run after installation of your main app.

Then I downloaded the LV 2009 RTE from the NI website which is actually a single .exe file (much nicer to include in your project).  The poblem is that it is a self-extracting file.  Therefore before you can run it (i.e. silently) it needs to be extracted, therefore doesn't work with Spec file.

 

2.  I produced a Spec file using the cmd prompt by locating the (any instance?) setup file for my apps installer using tedious dos commands.  I had trouble with the location command "setup /generatespecfile [spec file location]" but managed to sort it out.

It was a very short process to produce the spec file.  I opened it up and noticed that there are sections in it you can fill out.  I think in my case since I only want to install the run-time engine then the command line statement "setup /q /AcceptLicences yes" should take care of everything.

 

I hope that this should start a discussion so that we can work this out for LV 2009, or hear from someone who already has.

 

Thanks,

 

Battler.

0 Kudos
Message 1 of 20
(4,117 Views)

Hi battler,

 

Can you not include the RTE when you build the installer?


Flash
National Instruments
Applications Engineer
0 Kudos
Message 2 of 20
(4,082 Views)

G'day Flash,

 

What is the file I should include as the RTE?  The file from the NI website is a single .exe file which when executed requires self-extraction, therefore not compatible with silent install.

 

The RTE that I hav with my copy of LV includes a .msi file as the main executable.  The installation builder does not recognise any file (to start after installation) which is not .exe.

 

Hope you can help.

 

Cheers,

 

battler.

0 Kudos
Message 3 of 20
(4,067 Views)

Hi battler,

 

The ".exe file" is msiexec

 

msiexec /quite /i aproduct.msi /l*v c:\aproduct.log

 

or

 

start /wait msiexec /quite /i aproduct.msi /l*v c:\aproduct.log

 

More about msiexec can be found by running without parameters or in Internet.

0 Kudos
Message 4 of 20
(4,062 Views)

Hi NicB,

 

I understand that the msi file is an exe.

 

However, after I include the msi and all other associate files in the project when I go to select it (it must be selected) in the installation builder (as a program to run following installation) LV does not recognise and does not show it.

 

Do you know what I mean?

 

Cheers,

 

Battler.

0 Kudos
Message 5 of 20
(4,054 Views)
Anybody done this?
0 Kudos
Message 6 of 20
(4,018 Views)

Hmmm, not sure what you needed exactly...

 

The easiest way from my point of view:

 

undefined

 

Isn't?

 

Andrey.

0 Kudos
Message 7 of 20
(4,016 Views)

battler. wrote:
Anybody done this?

 

Please refrain from postings like this. It is only annoying, and you will actually get less help with such a tactic   

 

you have to use the msiexec.exe file with some command line options to "install" a msi file. In your case I think it would be best to make a a third-party Microsoft Installer package. Use this site a starter

http://support.microsoft.com/kb/257718

 



Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
0 Kudos
Message 8 of 20
(4,006 Views)

No need for a spec file?

 

Where do I locate the RTE with this msiexec.exe?  This is what I have..

 

undefined

 

 Thanks. 

 

 

 

0 Kudos
Message 9 of 20
(4,004 Views)
Do I need to place all these files into the Project?
0 Kudos
Message 10 of 20
(4,003 Views)