Command Line - Help on Options
Posted 09 March 2010 - 10:35 PM
Some are straight forward like /help, /recommend, /english, /noreboot
I keep testing each one to see what each command does, but was hoping there were more details avaialble. For example, it seems /minimal does nothing on its one but works with /unattend to show a progress status.
This is what I have: /nolicense /unattend /minimal /neverselectinstalled
Will the above ignore the agreements, select all blue items, ignore items already installed, and show a progress status?
What I don't know for example is if I use /unattend, does that also reinstall all current items already installed (black items), only the blue items, or do I need the /neverselectinstalled with the /unattend so not to reinstall the black items?
I'm just trying to get an idea of how these command work together. I can only test so far before AutoPatcher actually starts working unless there is a demo mode.
Posted 10 March 2010 - 12:17 AM
2 - Treeview Shortcuts
Shortcuts available from the selection window.
Ctrl + A Select all
Ctrl + D Deselect all
Ctrl + N Select none (same as above)
Ctrl + I Select all except installed
Ctrl + L Load selection from answer file
Ctrl + S Save selection to answer file
Ctrl + R Restore defaults
4 - Commandline Arguments
Commands you can pass to AutoPatcher.exe via the command line to alter default behaviour.
? Shows a message about the available switches
help Shows a message about the available switches
nolicense Skips both the AutoPatcher and Microsoft licenses
nocrashhandler Disables the crash handler
log Enables active file logging (to <windows>\autopatcher.log)
report Used along with /log, adds an installation report to the log file
verbose Enables additional output that /log would not normally write
devmode Allows you to ignore errors (in crash handler)
noreboot Skips the reboot sequence (Not implemented yet fully)
nodetection Skip file and registry detection on modules. Everything will be as if it's not installed, even if it is!
english Overrides the user interface language (normally adapts to regional settings) and switches it to default, english.
answerfile:<filepath> Specifies an answer file to load. This overrides the Answer File screen (where AutoPatcher would normally detect answer files in its folder and ask you whether it should load any of them)
unattend Activates unattended installation (implies nolicense). This also skip the answer-file screen, so the only way of specifying an answer file is through the answerfile switch.
minimal Only used along with unattend. This will run AutoPatcher with a minimal UI.
recommended Normally only modules marked as critical will be checked by default in the selection window. This switch allows modules marked as recommended to be checked by default too.
neverselectinstalled Installed child items of a parent will not be selected when the parent is marked for installation (normally selecting a parent will also select ALL children, even if installed/blue).
slipstream:<share> Allows you to integrate patches into installation media, where <share> is the drive and path to the share. This disables detection (no point detecting what is installed on the running system since the patches will be applied to a share), removal (can't remove an integrated patch from a share, can you?) and environment checks (e.g. windows version, language, ie, wmp -- for the same reason that detection is ignored).
as for your question:
> Will the above ignore the agreements, select all blue items, ignore items already installed, and show a progress status?
i never tried that option, but i believe that will do that, yes
Posted 10 March 2010 - 06:31 PM
One question. Is the default behavior of "/unattend" (assumed used with no other command) to...
Not display the agreements
Checks all items (black and blue) even if already installed
Posted 10 March 2010 - 07:17 PM
> Not display the agreements
> Checks all items (black and blue) even if already installed
> No interface
yes. i'm unsure about the progress bar
Posted 10 March 2010 - 07:37 PM
So the /unattend command will only check all blue items, check items based on an answer file, or use the default selection of items checked?
Posted 10 March 2010 - 07:52 PM
no. it will work in default mode, meaning that only the modules tagged as critical will be installed, if they aren't installed yet
> check items based on an answer file
in deed, /unattend can work in that way
> use the default selection of items checked
this is the default behavior (or should be)
if you wish match with wu, you can choose the /recommended, that will to the trick. with /neverselectinstalled , it can be an good choice. the modules required to match with wu are all tagged as /recommended. issue: certain modules (that i personally don't like) are also required to match WU, like (argggggggggggggggg) windows search. the wga modules are also recommended, but those requires user interaction to be installed and i'm unsure if they will prompt for an user answer due the /unattend.
my personal choice is another one. i don't like that answers file, so i have 3 folders:
1 - with the version that is online;
2 - with my edited modules, where everything that i us to set to be installed tagged as critical, among certain personal modules, like 7zip, etc;
3 - the folder where i put an copy of the folder 1 and, after it, i put an copy of the folder 2, replacing the folders/files that was in there.
so, in this 3rd folder i also have an .bat file, that calls for autopatcher without the licenses dialog. with that, all that i have to do is run that .bat file, reboot and then run that same .bat file again to fully update any windows.
issue: that 3rd folder is always unofficial and i will not sign that just because i can do it. in fact, i remove the .rti files to load faster
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users