Silent Mode (a.k.a. Unattended mode)

You can use the /unattend switch when you want to make AutoPatcher XP run in silent mode, suppressing any popup windows, batch file checks or questions. However: This wont stop any other applications/installation routines from giving popups or error messages...

Also, note that when you use the /unattend switch, AutoPatcher XP will NOT unckeck any installed updates. An other thing to keep in mind, is, that since the /unattend switch makes the process completely silent, there is no way you can select what to install... This means that AutoPatcher XP will use the defaults, provided by the database file. To change that, you will have to save your own defaults BEFORE using the actual unattended procedure!

No EULA Mode

In unattended mode, the EULA is displayed because it is an agreement between us and the users. If you have read it, agreed and don't want it to show up, you can use the /noeula switch. This switch will be very useful in unattended installs...

No Batch File Checks

When AutoPatcher XP starts, it checks for the target batch files, to prevent some problems... If you want to skip these tests and make the startup procedure somewhat faster, use the /nochecks switch.

Force Keep Backups

You can FORCE the end user to keep backups, using the /keepbackup. Note, that this will make AutoPatcher XP check ONLY for the normal batch files (and not the non-backup versions), but it will also disable the checkbox (quite handy!).

Force No Backups

Similar to the previous switch, but does the exactly opposite. If you want to FORCE a No-Backup process, you can use the /nobackup switch. Again, this will disable the checkbox.

Set the Restart Timer to 60 seconds

You can set the Restart Timer from 15 seconds up to 60 seconds, in order to be sure everything will close as it should. Just use the /60secs

Log events on screen

To make AutoPatcher log events on the screen, during the installation process, use the /screenlog switch.

Do not write a file log

AutoPatcher XP keeps a complete log of the database condition at the time of installation. This will helps us determine what went wrong in case you experience any problem... However, if you don't want to keep a file log, you can you the /nolog switch.

Force no reboot

You can use the /noreboot switch to bypass AutoPatcher's restart timer. Use this if you want to restart the system manually.

A couple more for December!:

Force previous log use

You may have noticed AutoPatcher asks about previous logs if you have used AutoPatcher again... There is a way to supply an answer to that question (other that the unattend mode!). Just use /forcelogs and AutoPatcher will automatically use any avilable log files to uncheck previously installed items...

Ignore previous logs

Similar to the previous switch, though this works in the opposite way... IF AutoPatcher does find any logs, if you supply the /ignorelogs switch, it will just ignore them and move on without asking... Some items (and only hotfixes) will still be unchecked based on the native hotfix check.

Disable Nags

You can automatically skip any 'nags' such as a failed database validation, antivirus warning, or even detection (logs & hotfixes) screen, by using the /nonags switch.

English Mode

If AutoPatcher's UI appears in an other language than english (this happens when a UI translation exists for your language) you can still run AutoPatcher with an english UI by using the /english switch.

AutoPatcher

If you want to open the AutoPatcher Tools immediatelly (normally started in About -> Tools) you can use the /tools switch. AutoPatcher will start, and instead of loading the normal UI and database, it will bring up the AutoPatcher Tools...

Have a nice day!

Just because I have to. And this has been discussed NUMEROUS times before. It helps when people search.

And as for my own opinion, note the word OPINION, I advise people to NOT use AutoPatcherXP. It's good for systems that are already up and running, but not for install. I'm not saying this because it is made by people over are neow1n, but because i just don't like it. There are security issues that can't be over looked. It's also ALOT faster in the long run if you just do it your self via the OFFICIAL microsoft method. When a new update comes out, you don't have to wait for the update of a program the runs the updates. You just add it to your disk, and you're done with it.

Personally, i like autopatcher,it has all the updates in one package..saves a heck of alot of time... but ppl are entitled 2 have their own opinion

Autopatcher is great

Actually i haven't tested it in an unattend but i figure i have to install it as the very last in my postinstall batches to avoid unpleasant behaviour from the many different patches.

But YES! Autopatcher is the ultimate add-on for windows it must be installed after SP1 at any time and the good thing is that not only it includes some non-MS patches it offers a great support to keep up-to-date w/o making a mess of things.

The ideea is to that u can make your options(save defaults) then use the flags(swithes) and never touch it again(i mean leave it alone and RUN! ) lol <kidding> of course u can touch it but only for changing the defaults -- thats all u have to configure at it, at least thats what i read and in silent mode it will get the default options u saved et voila.

BTW some1 who tested this plz confirm that it worked so i 'ld know what to do before i start my first unattend ever LOL i hope it doesn't go BOOM!

Have a nice day!

1) How does autopatcher work with SP2? it seems to not like it when i try to install it on an SP2 machine.

2) how can i make it install only certain elements. there are so many there has to be some external file that can cointain all the options that you want to install. (sorry for my ignorance here, i prolly overlooked something simple)