AutoPatcher Legend & Commandline Arguments


Recommended Posts

post-51082-1133456885.gif

This thread will contain information which applies to all AutoPatcher releases.

Note, this information has been updated for AutoPatcher version 5.6 as of May 2007.

Command Line Arguments (a.k.a. Switches)

You may use the following command line arguments (a.k.a. switches) to control AutoPatcher's behavior.

  Quote
nolicense

Skips both the AutoPatcher and Microsoft licenses

nocrashhandler

Disables the crash handler

log

Enables active file logging (to <windows>\autopatcher.log)

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.

Shortcuts

  Quote
Ctrl + A Select all

Ctrl + D Deselect all

Ctrl + N Select none (same as above)

Ctrl + L Load selection from answer file

Ctrl + S Save selection to answer file

Ctrl + R Restore defaults

Exit codes

  Quote
-1 Crashed (!)

1 User exit

2 User exit, avoiding reboot

5 Installation finished, reboot not required

10 Installation finished, reboot required, but supressed via commandline

Kind regards,

Antonis Kaladis

AutoPatcher Project Manager

www.autopatcher.com

Edited by theblazingangel
  • 7 months later...
  eddie79it said:
How i need to create the answer.ini files?

Please send me a mail with a reply.

Eddie

586647099[/snapback]

Maybe you should read:

Saving your selections

This shouldn't be hard to do; all you need to do is hold down the Shift key on your keyboard and move your mouse over the "Module Details" button. The button caption will change to "Save as defaults". Press it (while still holding Shift) and you will be asked for a location to save defaults. Once this is done, you can close AutoPatcher. Your selections were exported to an 'answer-file'.

  • 2 months later...
  TheBlazingAngel said:

^ no i dont think it is at the moment.

the only things that use it are the ms updates. the best thing to do right now is put together a quick batch file to delete the backup directories after using ap

Thank you for your prompt reply, that sounds like a good plan.

Happy Christmas,

KR

  M2Ys4U said:

...... "Module Details" button. The button caption will change to "Save as defaults"......

Maybe it is a small bug but this button is blank.... I check this in polish and english autopatcher and in: AutoPatcher Translation Packs

  Marcin.Riki said:

Maybe it is a small bug but this button is blank.... I check this in polish and english autopatcher and in: AutoPatcher Translation Packs

If it's "blank" then take a look at the .lng file Marcin! Here on the Dutch version is not "blank", you can select to save the selections...... :whistle:

  DaFlapDrol said:

If it's "blank" then take a look at the .lng file Marcin! Here on the Dutch version is not "blank", you can select to save the selections...... :whistle:

oh, no !

It is My bug

Added :

MainSaveDefaults=Save as defaults

and works fine

THX

  • 4 weeks later...
  • 1 month later...

@bust3r

1) in a shortcut's target path field, insert them at the end after the path, (with a space to seperate them)

2) start > run, enter the path to autopatcher.exe and add them after it as above

3) use raptors 'Argument Runner' standalone module, which will allow you to right click on a program, select 'run with arguments', and enter them into the box.

  • 3 weeks later...

I'm pretty set on the use of the command line argurements to 'run' Autopatcher, but are there any command line arguments for the Autopatcher Installer? I can't seem to find any specifics for the Actual Autopatcher installer, and I'd rather not have to repackage the whole installation if not necessary.

  Angelico_Payne said:

/unattend /noeula /nochecks /nonags /nobackup /nolog /noreboot /screenlog /ignorelogs /forcelogs (prior presets)

Switches by thuun

forum topic

Do these work...?

Acctualy I'm intrested in /nobackup switch ,since I remember having a conversation with FlapDaFrol who specificly said that the install without backups is not supported.

Blaze?

^ ive never actually tried any of the command switches myself appart from /noeula

the 'switches by thuun' i believe may be back from ap 4.x or earlier because raptor hasnt listed many of them in this thread himslef.

if youve got a problem or question about the switches youd probably do best to ask raptor.

  • 4 weeks later...
  • 1 month later...

I have tried to use the answer.ini file to automate the installation of Autopatcher. Autopatcher is a great product but I have had mixed results while using the answer file. The answer file certaintly automates the install of the hotfixes for Windows XP but it did not work correctly for me. For example, I tell it "not" to install Windows 7.5 messager and yet it does? Does the answer.ini file need to be edited once it is saved to the hard drive? Does the order of each command make a difference?

Any help would be appreciated.

Wiz

  nw_raptor said:

post-51082-1133456885.gif

This thread will contain information which applies to all AutoPatcher releases.

AutoPatcher Legend

In AutoPatcher, some items appear with special formatting. The color legend below will help you understand what the formatting means.

Commandline Arguments (a.k.a. Switches)

You may use the following commandline arguments (a.k.a. switches) to control AutoPatcher's behavior.

Saving Custom Selections

Kind regards,

Antonis Kaladis

AutoPatcher Project Manager

www.autopatcher.com

  • 4 weeks later...

This tool is great. The silent options look like they could be used to run a full update from a central place. I tried this:

I downloaded the April 2003 full editition and manually ran it on a machine (awsome very nice).

I ran it again and generated a silent install ini (hold shift down like in the instructions). The auto ini included all critical patches and some options. The ini looks nice and logical in notepad.

I created a batch file with this command

"\\server\path\AutoPatcher_2003_Apr2006_Full.exe" /unattend:t2 /noeula /noreboot /defaults:\\server\path\\2k3Defaults.ini

When I run that though I get the end user agreement and then normal manual options.

So I look again and perhaps these options are not for the full install but the AutoPatcher.exe file installed under c:\program files\Autopatcher 2k3\autopatcher.exe.

So to autopatch new machines do I need to patch to that EXE on a machine where it was manually installed?

Can I copy that whole directory from program files to a net share and use it from there?

I dont see a manual for autopatcher (am I missing something) just links to the newsgroups which are not so set by step? I see the website is coming and then no doubt more instructions. I figure other must be doing what I want to do and could use a reply to this like me.

If I get it all sorted I am happy to write a step by step. Excellent tool and extendable for other packages which is awsome.

IronPaw

removed large excess space at the bottom of your post - theblazingangel

Edited by theblazingangel

@Ironpaw

the switches are for autopatcher.exe not the installer. the installer simply unpacks the autopatcher release, you then run autopatcher to install the updates.

after extracting the release(s) you can copy the contents of the folder you extracted it to directly to a cd/dvd/flash-drive/portable-hard-drive/network-share/etc

note, dont bother copying uninstall.exe!

im not clear on what you meant here:

  Quote
So to autopatch new machines do I need to patch to that EXE on a machine where it was manually installed?

did you mean 'what happens if a machine already has some patches installed'?

did you mean 'what should you do if a machine already has a copy of autopatcher installed'?

did you mean something completely different?

please elaborate.

  • 4 weeks later...
  nw_raptor said:

post-51082-1133456885.gif

This thread will contain information which applies to all AutoPatcher releases.

AutoPatcher Legend

In AutoPatcher, some items appear with special formatting. The color legend below will help you understand what the formatting means.

Commandline Arguments (a.k.a. Switches)

You may use the following commandline arguments (a.k.a. switches) to control AutoPatcher's behavior.

Saving Custom Selections

Kind regards,

Antonis Kaladis

AutoPatcher Project Manager

www.autopatcher.com

theblazingangel Mar 24 2006, 15:49 Post #18

AutoPatcher Team Member

Group: Registered

Posts: 1,211

Joined: 25-March 04

From: UK

Member No.: 51,082

^ ive never actually tried any of the command switches myself appart from /noeula

the 'switches by thuun' i believe may be back from ap 4.x or earlier because raptor hasnt listed many of them in this thread himslef.

if youve got a problem or question about the switches youd probably do best to ask raptor.

Raptor.

Could you please put together an up-to-date list of the switches that work with AP and examples of their actual usage??

Reading thru the forum it becomes VERY confusing a to what switches work and how to format them!

Thnx a lot.

Cutie_pyie

  • 1 month later...
  • 3 months later...
  Ironpaw said:

....... do I need to patch to that EXE on a machine where it was manually installed?

Sounds like IronPaw is attempting to run AutoPatcher across a network share.... haven't tried this myself, my thinking AutoPatcher looks at local install status only... that is unless %system% folder variable can somehow be changed/redirected...

but adding the 'path' to the AutoPatcher executable located in a share on a mapped network drive is what i think is being asked...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.