marqo
7th July 2004 12:51 UTC

Install an included installer
Hi all!
My installer is composed of 9 installer, one for each of my sections. That means that I call "InstallerSection1.exe" if the section 1is choosen, etc.
And "InstallerSectionX.exe" contains files, and the main installer only contains some "InstallerSectionX.exe" files.
My probleme is this one: when I call "InstallerSectionX.exe"
with
nsExec::Exec "$TEMP\${InstallerSectionFile}" /S /D=$INSTDIR

nothing appears in the log windows (Page instfiles) of the main installer...
I try a lot of solutions but nothing convinced me. I wouldn't like opening another windows for an internal installer, just get the log in the main installer.

Is it possible ?

Davion
7th July 2004 13:00 UTC

AfrowUK wrote a function to put the log from the instfiles Page into a file, so you could

-put the log into the file
-read the file into a variable
-delete the file
-print the content with "detailprint"
in your main installer

I hope you understand what I mean
and that it fits to your needs

marqo
7th July 2004 13:07 UTC

Thank you. Yes it could be a way, but if one of the internal installers need 2 minutes to install, nothing appears in the window during that time and users could think that install operation crash... with your method, I doesn't solve the problem. I really need to obtain log "as it comes".

Davion
7th July 2004 13:11 UTC

what about writing a detailprint ala "installing files, this may take a few minutes"

marqo
7th July 2004 13:23 UTC

Yes, it could be too... but... not exactly what I would...

Is it possible ?

pengyou
7th July 2004 13:34 UTC

nsExec::ExecToLog displays output in the log window "as it comes".

For more information see the nsExec.txt file in the Contrib\nsExec folder (the folder also contains a simple script which uses nsExec::ExecToLog).

marqo
7th July 2004 13:46 UTC

I'm sorry, but ExecToLog give you the possibilites to log a dos command, or a program that run in dos mode (as makensis). You cannot log a windows program, as an exe you made with makensis/makensisw. I am wrong ?

pengyou
7th July 2004 15:52 UTC

Sorry, I only glanced at the rest of the thread.

Why are you using separate EXE files for each section in the installer?

marqo
7th July 2004 15:58 UTC

Because it's suite of products. Each products could be installed alone, but the most of merket is the suite. There a lot of advantage, the first is that you can make a complete installer (with all "InstallerSectionX.exe" included), and with the same nsi you can make another one wich contains only code, and the "InstallerSectionX.exe" are downloaded :-)

Afrow UK
7th July 2004 15:58 UTC

Why not do it the normal way with the seperate sections containing the seperate files. If you have loads of files, and you want to break it up in the script, put the sections in different files and then !include the files.

I didn't write the dumplog function, that was written by Kichik for me :)
I wrote the other one though which dumps only lines containing a certain string.

-Stu