eRoom Application - How to open Installshield Setup.exe
In eRoom application, I have a "ClientSetup.exe" file which needs to be run as a silent install.
I tried extracting the "ClientSetup.exe", there are couple of files along with a Installshield "Setup.exe" .
When it is run, there are only 2 screens, first asks the users to click "Install" button and on second screen the user gets a Reboot (Yes/No) prompt.
/s switch works here but it reboots the systems without any prompt, as default is set to "Yes".
I want to run this install as a silent install and at the same time just want the users to see the reboot prompt, allowing them to restart the systems.
As there is no msi here, how can I do the customization?
Also, I created a setup.iss file and tried using it while running Setup.exe with silent switch like <Setup.exe /S /f1setup.iss> , still it reboots the systems.
Please, guide me as to how I can prompt users for reboot?
Thanks
I tried extracting the "ClientSetup.exe", there are couple of files along with a Installshield "Setup.exe" .
When it is run, there are only 2 screens, first asks the users to click "Install" button and on second screen the user gets a Reboot (Yes/No) prompt.
/s switch works here but it reboots the systems without any prompt, as default is set to "Yes".
I want to run this install as a silent install and at the same time just want the users to see the reboot prompt, allowing them to restart the systems.
As there is no msi here, how can I do the customization?
Also, I created a setup.iss file and tried using it while running Setup.exe with silent switch like <Setup.exe /S /f1setup.iss> , still it reboots the systems.
Please, guide me as to how I can prompt users for reboot?
Thanks
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Well, I can't think of anything which a combination of ProcMon and In Control (Ziff-Davis's snapshot tool) has failed to spot. You will waste more time in trying to find out how to stop that reboot than you will spend in fully capturing it.
I'm sure the InstallShield web site/forums will have documentation on all the relevant sections and entries for recorded set-up files.
My procedure - for ALL my captured packages is to run the MSI that the capture produced, THEN re-run the vendor install over the top (deleting any registry/file flags indicating that it's already installed) whilst running a snapshot tool. If anything significant is missing, I add it to my package and repeat the exercise. This ensures that everything which the vendor set-up does is repeated in my package. I use a similar procedure after the set-up part is done to see if the application itself write any further data anywhere. Again, anything relevant gets added.
I'm sure the InstallShield web site/forums will have documentation on all the relevant sections and entries for recorded set-up files.
My procedure - for ALL my captured packages is to run the MSI that the capture produced, THEN re-run the vendor install over the top (deleting any registry/file flags indicating that it's already installed) whilst running a snapshot tool. If anything significant is missing, I add it to my package and repeat the exercise. This ensures that everything which the vendor set-up does is repeated in my package. I use a similar procedure after the set-up part is done to see if the application itself write any further data anywhere. Again, anything relevant gets added.
Posted by:
anonymous_9363
16 years ago
There are a limited set of circumstances for which a machine needs to be rebooted. Most packages reboot because the packager was too lazy to work out how to update the system without requiring one. Many assume, for example, that if their software requires an addition to the environment's PATH variable (don't get me started on software which needs to do THAT!), it needs a reboot.
If there's a reboot flag in the package, I don't think you can avoid it. I'd re-package it. During that exercise, you'll discover why it reboots and then "program" out the reboot.
If there's a reboot flag in the package, I don't think you can avoid it. I'd re-package it. During that exercise, you'll discover why it reboots and then "program" out the reboot.
Posted by:
MSIRepackager
15 years ago
Yes, you are right, Re-packaging would solve the purpose here.
However, earlier attempt of repackaging was unable to capture some things which resulted in failure of the package. After exhausted with repackaging/capturing setup, we altimately decide to run vendor supplied .exe file only. But, running this (InstallScript based) Setup.exe in silent mode, is causing forced reboot.
I tried searching several switches to avoid reboot like /norestart etc........Isn't there anything which we can set in setup.iss which will avoid forced Reboot?
Thnaks for your time and help.
However, earlier attempt of repackaging was unable to capture some things which resulted in failure of the package. After exhausted with repackaging/capturing setup, we altimately decide to run vendor supplied .exe file only. But, running this (InstallScript based) Setup.exe in silent mode, is causing forced reboot.
I tried searching several switches to avoid reboot like /norestart etc........Isn't there anything which we can set in setup.iss which will avoid forced Reboot?
Thnaks for your time and help.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.