ShakerWD
30th August 2005 12:15 UTC
ExecWait, and then wait for 2nd process?
hi,
just begun working with nsis. its really nice to work with, especially with EclipseNSIS. first off all thx for these great tools!
in my installer i'm checking if acrobat reader is installed.
if not, i start the installation with ExecWait. the problem is that the newest acrobat installer launches 2 processes. the first process invoked by me is AcrReader.exe
This process ends and the Reader installation is continued with the msiexec.exe process.
thus my installation continues during the main reader-instalaltion 'cause AcrReader.exe ended.
how i can observe these 2 processes? nothing found so far.
need to wait until the 2nd process returns.
cheers
Daniel
KenA
30th August 2005 15:43 UTC
Hi ShakerWD,
you should be able to monitor msiexec.exe, and any other process for that matter, with the "FindProcDLL" plug-in. Don't remember if it's in standard NSIS install tho.
Hope this helps,
KenA
OJi
30th August 2005 19:42 UTC
when you launch the exe does it begin to decompress acrobat reader ?
if yes - unpack it your self and lauch the msi directly.
hope it helps.
OJi.
ShakerWD
30th August 2005 21:19 UTC
you should be able to monitor msiexec.exe, and any other process for that matter
thats what i've already done. the problem with this solution is that adobe starts the msiexec 4!! times. 3 times with the logged in user, the 4th time with an system account. works fine. i'm waiting a well defined time. checking the state of the process. problem is that the 4th msiexec.exe never dies. it will run until the end of windows session. or until killed by hand. so moitoring the process wont give the right solution.
unpack it your self and lauch the msi directly
took a while to find the needed files. will try tomorrow if it works. but think execwait will run against the same wall as the aproach above cause the hanging process. will try an older reader version too.
thx for your replies
cheers
Daniel
Takhir
31st August 2005 07:03 UTC
You can launch Acrobat setup at the end on installation (last section, for example) and finish your installer instead of waiting. NSIS 'finish' page must be omitted this case - see finPre function in the attached script. I did this trick for .NET 1.1 installation because it may require reboot (if replaces 1.0). Attached script is draft only, it searchs $EXEDIR for 2 additional predefined setup files (dotnetfx and 'components' package) and (if any) displays sections page (editor itself not requires sections). Hides itself during 'components' package installation (SEC_2).
ShakerWD
31st August 2005 09:43 UTC
thx takhir,
solved it this way. searched the unpacked files.
added them to installer.
starting installation with
ExecWait"msiexec.exe/i$TEMP\Test\Acrobat\Reader.msi"
ExecWait can handle the hanging process. works fine now.
thx for your replies