AutoPatcher Legend & Commandline Arguments


Recommended Posts

I can't seem to create the answer file. I'm using the october 2006 Dutch language full version. After starting AP and waiting 'till the modules have shown up, I select everything that applies to my situation. Then I press shift and see the button change to "save as default". However, when I click on it it just lists the module details for the module selected twice but doesn't save anything. Could there possibly be some bug?

Link to comment
Share on other sites

  • 4 months later...

How do I do a "Save as Default" in 5.6 and are the command line switches the same in 5.6 as in 5.1.

Thanks in advance.

(working with the Vista version)

Link to comment
Share on other sites

Press Ctrl+S to save the answer file and Ctrl+L to load one (when in the module tree screen).

In order for AutoPatcher find it and show it when you start AutoPatcher again, save it in \AutoPatcher folder.

Link to comment
Share on other sites

  • 2 weeks later...

Trying out the new AP v5.6 for Vista, much improved speed, very nice!

However, I can't get the switches to work, I read on here how to make a default answer file for the new v5.6

(Thx 'Gandolas'), but none of the switches for /noeula /defaults /skipdetection etc.. work.

Have they been renamed?

I'd like to deploy this as a silent install using an answer file, anything else I need to know?

Link to comment
Share on other sites

Trying out the new AP v5.6 for Vista, much improved speed, very nice!

However, I can't get the switches to work, I read on here how to make a default answer file for the new v5.6

(Thx 'Gandolas'), but none of the switches for /noeula /defaults /skipdetection etc.. work.

Have they been renamed?

I'd like to deploy this as a silent install using an answer file, anything else I need to know?

AutoPatcher 5.6 has a slightly different set of switches. Some have been replaced...

Commandline Arguments:

  • 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
  • nodetection: Skip file and registry detection on modules. Everything will be as if it's not installed, even if it is!
  • 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)
    Always use this argument last!
  • 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.

Link to comment
Share on other sites

  • 3 weeks later...

Question regarding Autopatcher 2003 (5.1)

I see how to make it patch automatically ... Works GREAT!

What I cant seem to figure out, is an answerfile that will always install ALL Critical & Recommended, without the need to recreate the file each time new updates are applied.

Ideally, you should be able to set the answer file like below .... without ANY other lines, and it should not have to contain each subitem underneath it.

// AutoPatcher 5.1 Answer File

+ Microsoft Windows - Critical Updates

+ Microsoft Windows - Recommended Updates

- Microsoft Windows - Updated Components

- Windows Addons

- Registry Tweaks

Thoughts/other suggestions?

Link to comment
Share on other sites

  • 3 weeks later...

Hi,

For those who need to delete the hotfix backups then you can use the tool from:

http://dougknox.com/xp/utils/xp_hotfix_backup.htm

This is a freeware tool which will delete the hotfix backups for you.

CCleaner will remove the hotfix install log files if you need to do this.

However I do not recommend deleting either of these.

If your system drive is that full up then you will probably have issues running Windows XP anyway. Remember that you probably need to have at least 1 GByte of free disk space on the system drive to use Windows XP effectively.

Kind Regards

Simon

Link to comment
Share on other sites

Is there a command line /defaults switch for AutoPatcher 5.6 like in previous versions? The old syntax doesn't seem to work with this version.

Link to comment
Share on other sites

^ It's in the 1st post.

Thanks man, I didn't realize it had been changed recently. You guys must have snuck it in after I left work yesterday.

Link to comment
Share on other sites

  • 1 month later...

So these still operate by the / before the code? I didn't see it documented in the first post. ;)

Edited by Jack 0Neill
Link to comment
Share on other sites

  • 4 weeks later...

could there be another command line switch added? a /? or /help or /switches or all of these to show the command line switches within autopatcher itself like many other programs?

Link to comment
Share on other sites

could there be another command line switch added? a /? or /help or /switches or all of these to show the command line switches within autopatcher itself like many other programs?

added to my todo list :)

Link to comment
Share on other sites

Question regarding Autopatcher 2003 (5.1)

I see how to make it patch automatically ... Works GREAT!

What I cant seem to figure out, is an answerfile that will always install ALL Critical & Recommended, without the need to recreate the file each time new updates are applied.

Ideally, you should be able to set the answer file like below .... without ANY other lines, and it should not have to contain each subitem underneath it.

// AutoPatcher 5.1 Answer File

+ Microsoft Windows - Critical Updates

+ Microsoft Windows - Recommended Updates

- Microsoft Windows - Updated Components

- Windows Addons

- Registry Tweaks

Thoughts/other suggestions?

I would also like this feature.

Link to comment
Share on other sites

Actually, let me explain what I'm looking for so it is clear.

It would be nice if you could set AutoPatcher to scan the current system it is running on and install all of the updates in the groups that you specify (Critical Updates, Recommended Updates, etc.). I don't see why I should have to create a test machine to run an answer file against.

One situation where I see this useful is if I later slipstream updates on to a CD and run AutoPatcher on first logon.

Link to comment
Share on other sites

  • 2 weeks later...

With regards to loading your custom selections, the older instructions stated the following:

Note #1

Never, I repeat, never use quotes. Even if the path to the answer file contains spaces, AutoPatcher will handle it without quotes.

Does this still apply? Should we still stay away from using "quotes" even if the filepath contains spaces?

Link to comment
Share on other sites

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

    • No registered users viewing this page.