Adobe Flash Builder Std. Etd. v4.0 silent key for setup exe
The setup.exe upon installation , extracts about 9 msi's.When the msi's were installed seperately only some files were getting installed. The application was not installed completely.
Silent installation of the exe was checked with the switches like /quiet , /silent, /s etc, but the exe could not be installed silently.
Any one help me out Silent key for this application so that install the setup silently.
Silent installation of the exe was checked with the switches like /quiet , /silent, /s etc, but the exe could not be installed silently.
Any one help me out Silent key for this application so that install the setup silently.
0 Comments
[ + ] Show comments
Answers (16)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Posted by:
venkatgowda
14 years ago
Posted by:
Technocrat
14 years ago
The setup.exe upon installation , extracts about 9 msi's.When the msi's were installed seperately only some files were getting installed. The application was not installed completely.
There may be chances that apart from 9 MSI's, setup might install legacy files of its own.
Hence, the better way to do this would be check in the event viewer for the sequence of 9 msi's.
Create a new MSI for all the files/registries which are not getting installed via vendor MSI's.
Then, in your MSI do a silent nested call for all the vendor MSI's in the desired sequence.
I hope this will help you to make the application run. [:)]
Posted by:
venkatgowda
14 years ago
Posted by:
Technocrat
14 years ago
Posted by:
anonymous_9363
14 years ago
I meant, did you log the install when you used the MSIs.
Anyway, we could go on like this forever. The way to proceed is to:
- install the MSIs
- rename the 'Uninstall' keys in the registry to fool setup.exe into thinking that none of the MSIs are installed
- start a lightweight capture tool, such as InstallWatch
- take a 'Before' snapshot
- run the set-up stub
- TEST THAT THE PACKAGE WORKS
- take an 'After' snapshot
- incorporate any relevant changes into a new MSI which you will then install after the other 9 have been successfully installed
Anyway, we could go on like this forever. The way to proceed is to:
- install the MSIs
- rename the 'Uninstall' keys in the registry to fool setup.exe into thinking that none of the MSIs are installed
- start a lightweight capture tool, such as InstallWatch
- take a 'Before' snapshot
- run the set-up stub
- TEST THAT THE PACKAGE WORKS
- take an 'After' snapshot
- incorporate any relevant changes into a new MSI which you will then install after the other 9 have been successfully installed
Posted by:
anonymous_9363
14 years ago
...or maybe use the Notes which somebody thoughtfully pointed out in a thread a moment ago (thanks, Joe)
Posted by:
venkatgowda
14 years ago
I got silent key (code in .xml format) for setup exe.. i am facing followong issues..
1.After installing setup exe silently, while launching shortcut it prompt for EULA dialogue box,if accept that EULA it again prompt for licence key dialogue box..
Please help me out how to suppress EULA and Licence key dialogue box...
1.After installing setup exe silently, while launching shortcut it prompt for EULA dialogue box,if accept that EULA it again prompt for licence key dialogue box..
Please help me out how to suppress EULA and Licence key dialogue box...
Posted by:
Technocrat
14 years ago
- Before launching the shortcut for the first time, start a capture tool (e.g. Picture Taker, Installrite, etc)
- Take the 'Before' snapshot (Initial Scan)
- Launch the shortcut and perform all the required changes such as 'Accept EULA' and entering license info.
- Take the 'After' snapshot (Final Scan)
This will give you all the changes done due to 'Accept EULA' and licensing info. Incorporate this changes in your package so that this changes are updated at the time of installation itself.
- Take the 'Before' snapshot (Initial Scan)
- Launch the shortcut and perform all the required changes such as 'Accept EULA' and entering license info.
- Take the 'After' snapshot (Final Scan)
This will give you all the changes done due to 'Accept EULA' and licensing info. Incorporate this changes in your package so that this changes are updated at the time of installation itself.
Posted by:
Rheuvel
14 years ago
actually, configuring the license and EULa options are both explained in the link to the note, that VBScab already posted.
Posted by:
venkatgowda
14 years ago
Posted by:
Rheuvel
14 years ago
The error code and message in the cmd prompt aren't that useful most of the time. Luckily any Adobe installer also generates additional log files, in which you'll find more details about what's causing the installation to fail.
As the earlier mentioned note says the CS5 installation engine is used, this article will tell you how to find the real cause of your failed install.
As the earlier mentioned note says the CS5 installation engine is used, this article will tell you how to find the real cause of your failed install.
Posted by:
venkatgowda
14 years ago
Posted by:
Rheuvel
14 years ago
OK, good! Where did you find it? If it was hiding in some exotic location, make sure to post it in the Package KB!! :)
And if you still need to analyse the log, give this Adobe Support Advisor a try:
http://www.adobe.com/support/loganalyzer/
Someone posted it in another thread recently and I'm curious about it's performance!
And if you still need to analyse the log, give this Adobe Support Advisor a try:
http://www.adobe.com/support/loganalyzer/
Someone posted it in another thread recently and I'm curious about it's performance!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.