*.iss response file gives a dialogue box at the end.
Answers (4)
It does rather sound like the final dialog originates elsewhere to the other dialogs, and if so, no amount of recording will capture your final response.
I've encountered this before and sometimes had to resort to using AutoIt to respond to the prompt.
Here's a few lines of AutoIT script which might get you started if you go down that route
winwait("Zone Labs TrueVector service","This is a security",240)
Winactivate("Zone Labs TrueVector service","This is a security")
Send("!Y")
Explanation,
- The script waits for a Window with the title "Zone Labs TrueVector service" and containing text beginning "This is a security"
- When detected, the script gives the Window focus
- The script then send Alt+Y to the window, which in this case equates to a click of the "Yes" button.
- There is a timeout of up to 240 seconds for the window to appear before the script will terminate anyway
Just modify the values in the script to meet your own particular needs.
Spartacus
Comments:
-
Sorry but I don't like using AutoIT scripts. I'ts not packaging. - tellmehow 10 years ago
-
I will tell you how to get around with it by capturing that application using Wise or Installshield packager and you will have no problems with that dialog. Using AutoIT is still a part of packaging because your aim is to deliver that software without a user intervention. Most of the time, if you are not capturing the application, AutoIT or any scripts will help you achieve that and have a package. - dj_xest 10 years ago
-
Capturing drivers is not recommended otherwise I would have captured the installation to get around the issue. I thought I will check with everyone here first to see if there is a argument I can pass in the *.iss that will suppress that dialogue box. If not, instead of capturing, I will try to extract the drivers and install them using dpinst.exe. - tellmehow 10 years ago
"I have tried sending an enter key using a script but since the window is waiting for a user input, the send enter key script is never triggered."
"Sorry but I don't like using AutoIT scripts. I'ts not packaging".
Now I am confused, which type of script have you tried using and why did that one qualify as "packaging" whereas AutoIT does not, in your view ?
Spartacus
Comments:
-
I used VBScript which is widely used in packaging. For instance, for creating custom actions and even for wrapping MSIs for deployment depending on the environment.
AutoIT script is a third party "tool" that uses keystrokes and screen coordinates to automate the installation and IF the mouse is moved or the keys are touched during the process, your "package" will break. How many users can you stop from doing that? - tellmehow 10 years ago
Save yourself a whole heap of trouble and just repackage the app. The AppDeploy...sorry, IT Ninja... Repackager does the job, if your employer is too cheap to purchase a proper packaging tool.
FWIW, I almost never use vendor's installation set-up executables. I want to know EXACTLY what their EXE is going to do to my workstations!
Comments:
-
My employers preference is avoid capturing applications and to use the vendor media therefore I was trying to get the vendor media to work but I couldn't. I posted the solution in my question. - tellmehow 10 years ago
-
Great job! And now, even better, your employer knows that you know more about packaging than they do. I was going to comment that it's part of your role as the packaging "expert" to educate your employer. Dictats that make no sense - like letting vendors loose on your workstation estate (Adobe Acrobat Pro v9.01, anybody? Ha, ha, ha!) - are a huge mistake and *will* get you bitten on the arse! And then to whom do you think the blame will be attributed? "You're the expert! You're meant to know about this stuff!" - anonymous_9363 10 years ago
-
Don't you think I did? We can only advise but it's up to them to implement and they want to keep things the way they are. - tellmehow 10 years ago
If the native install is an MSI, can you not disable the final dialog with a transform?
If it is an EXE, how about running the exe from a wrapper, and then killing the installation process once the end is reached?
Comments:
-
Tried that from a wrapper but because the dialogue box is launched, the process is stuck there and the line that's supposed to close the box is never executed. Anyways, it's done now. - tellmehow 10 years ago
