[analogduck]

Are all automated or silent installations made with default settings only? Or can you customize installations as though you chose the "Custom..." button during a manual install?

A simple example, when I install Acrobat Standard I don't ever want the Office toolbar buttons installed. I don't recall what these "helpful" items are called off the top of my head, but I always deselect them from the installation tree ("Do not install" or whatever the option is) during the procession of setup dialogs. Can I automated this? What are my options and what are the catches to them?

I dread creating and using some sort of macro (autohotkey, autoit, etc.) to use the GUI installer during a post-OS-installation routine. I am currently imagining the only other alternative would be to snapshot the files and registry changes made during such an install. Doing so sounds a bit risky with some applications that tend to add a bazillion registry keys.

Clues always appreciated! Thank you!

[MHz]

InstallShield Tuner 7.0 for Adobe Acrobat may help to achieve your goal with Acrobat Standard.

Installers can vary with options available via commandline use, so I think you already realize that snapshot installation packages maybe the only method if you aim too high. There is no single answer that can cover all installers. They all are mostly different and may require different methods to make them install close enough to your expectations. Some members have used programs like InstallRite and have seemed happy. I use AutoIt scripts, others use may purely repacking. I use Inno Setup for repacking into a new installer. The options are available in different forms and there is no real correct or best way to fully have a customed installation of all your software.

You perhaps already understand what I have said already, but there is no magic wand for Software Installers that I know of. Sometimes a compromise is needed with Software Installers.

[analogduck]

-Sigh- As I feared.

Thank you very much for the Acrobat clue. I'll put that to use immediately!

As for InstallRite vs. AutoIt, isn't the AutoIt process laborious (much typing and fiddling to get things right)? Or do you have a quick way of producing the scripts? I imagine that you prefer InstallRite over AutoIt because it's cleaner/safer? Just looking for your insights, as you've likely already suffered the paths I'm considering going down now.

Thank you for your quick and appropriate reply. =)

[Nologic]

If you know what your doing with AutoIt...its on par with a repack...I feel...with the up side that a script can generally be reused for a number of updates to the software...where a repack requires...well starting from scratch again.

Repacks are less likely to break...tho if an AutoIt script is written well...generally they don't break...but repacks are suprior in this area....if your good at them that is.

There is no real clear answer...but if you don't update software much...repack is probably the way to go...if you swap out fairly often...then AutoIt is likely the best route...if you never update...hehe ghost is the best route bar none.

[MHz]

analogduck, on Feb 4 2006, 04:27 PM, said:

-Sigh- As I feared.

Thank you very much for the Acrobat clue. I'll put that to use immediately!

No problem. That is what I would use if I used Acrobat.

analogduck, on Feb 4 2006, 04:27 PM, said:

As for InstallRite vs. AutoIt, isn't the AutoIt process laborious (much typing and fiddling to get things right)? Or do you have a quick way of producing the scripts? I imagine that you prefer InstallRite over AutoIt because it's cleaner/safer? Just looking for your insights, as you've likely already suffered the paths I'm considering going down now.

Hmm, someone who does not not me well, lol. I like using AutoIt as in general scripting. I must admit that automating some installs can be a pain. Probably about 20% of my installations are automated and the rest are done by silent switches. I used to automate them all, but got tired of the extra effort needed to do it and update them. 100% of my scripts are AutoIt and no need for any CMDOW, Taskkill or any other 3rd party commandline tool that needs to be used with a cmd file. As for seeing any automation of installers is not seen as I use AutoIt to cast a full screen picture on a AllWaysOnTop Gui at T-12 as seen here. No tricks, as only AutoIt scripting.

InstallRite seems to give good results for what I have done with it, by means of testing. But I prefer to keep the installer original as the author intended, as it saves doubts as to whether the software will work as to expectation.

I have repacked a few installers with Inno Setup. One installer I have, uses Inno Setup v1.2, but is still a good software. Since it has not been updated for about 5+ years, I repacked it as it did not support silent install. No matter what happens, I still use AutoIt to handle the installation.

If you want a good helper with dealing with installers, then I recommend CMenu (yeah well, promoting my own product) . This shell extension is made for helping with installations, even if you do not use AutoIt. It also makes template AutoIt scripts for the installers. All of my installation scripts are CMenu created. The scripts are self contained to install silently with switches if identified, shortcut folder moved to a catagory folder and unnecessary shortcuts removed. You can add your own code to add or remove files and every other task imaginable.

As you seem to not want to exert yourself into scripting in general, then most above maybe just something to read, but well, I guess someone may enjoy reading about my methods.

Oh, don't forget, unattended projects are endless projects as for updating and changing of software ... so learning some scripting will certainly be needed at some point.

This post has been edited by MHz: 04 February 2006 - 06:08 AM