Tomcat and /S

Hi,

I'm applying the same /S /D=<installdir> to install Tomcat silently on Windows. It pretty much works.

There are two cliches that I would like to ask for help:

1. How to suppress the initial dialog "Using JDK found on <...>" with an OK button?

2. When install is completed, an Explorer Window with the new install directory is popped up. How can I suppress that?

Thanks.

Function .onInit
Call GetParameters
Pop $0
StrCmp $0 "/S" end_function
StrCmp $0 "/a" end_function
MessageBox MB_YESNO|MB_ICONQUESTION "You have ran the installer in silent mode.$\r$\nContinue? IDNO +2
Exec "My_Install_Package.exe /S"
Abort
end_function:
FunctionEnd

Posting a question once is enough.

You can't do what you're asking to do unless the creator of the installer have made the installer sensitive to /S on the command line.

See this post too:

How'd my post get in here?
lol

-Stu

Actually the tomcat installer takes /S and works almost perfectly besides the cliches mentions. I also have the Tomcat.nsi file. Just want to see if I can pass anything at the command line to suppress those two annoying dialogs.

I merged the two posts and moved Edmond Chui second, almost identical post to another place.

Edmong, take a look at that other link I added in the last post, it contains more information.

If you want you can also change the script and recompile. All you need to do is add a silent check and skip the dialogs if /S was used. For this you should use:

Great information! Thanks kichik! And apologies for cross-posting.

So what I have gathered is that Tomcat was not made to be completely silent with the /s, so the alternative would be to recompile this adding the above mentioned changes. My question is do you need the .nsi file to do this? Is there a way to extract the install information or an install watch file? Basically do I have to find the nsi script for this? Thanks in advance and pardon my ignorance this will be my first install with this tool.

You must have the .nsi script, but since Tomcat is open source it's not a problem. The .nsi file is probably in Tomcat's CVS.