AutoPatcher Launcher
JTok
11 Feb 2011
In the course of my work I found a use for AutoPatcher, but found that I wanted a way to automate my use.
I wanted it to:
1)Run, installing updates for the given OS
2)Restart
3)Run again
4)Restart
5)Run, this time installing the Addons
In the end, I had to write a small application to accomplish this. I (creatively) named it AutoPatcher Launcher, or APL for short.
Setup is very simple:
1)Create a folder for each OS you would like and run apup.exe
1a)The folder names should be XP, Vista, 7x32, and 7x64
1b)These are the only operating systems supported at this time
2)Create an answer file for each OS called answer.aaf in its respective OS folder
3)Create a folder for the addons (named Addons) and run apup.exe
4)Create an answer file for each OS in the addons folder named after each OS
4a) XP.aaf, Vista.aaf, 7x32.aaf, and 7x64.aaf
Sadly this is a .NET 2.0 application, which means XP requires that to be installed first (.NET 2.0 comes with Vista and 7)
The solution is to use a batch script that prompts if you're running XP and then tries to install .NET 2.0 Framework, before rebooting and then automatically running the AutoPatcher.
I have included everything you need in the attached zip file to get started, including folder structure, a place holder for the .NET installer, a batch script for installing .NET for XP, and an autorun inf for use with insert-able media. The only thing you should need to do is download .NET 2.0 redistributable if you plan to use this with XP, download the autopatcher and set it up for each OS, and create your answer files.
You can download APL via the attachment to this post, or at http://www.mediafire...th8cmlshr6vvtab.
TECHNICAL DETAILS
APL uses the HKCU\SOFTWARE\MICROSOFT\WINDOWS\RunOnce key to start at boot.
APL supports arguments, but only one at a time:
/XP1 (Install XP updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/XP2 (Install 2nd XP updates, then restart and run Addons)
/XP3 (Install XP Addons only)
/Vista1 (Install Vista updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/Vista2 (Install 2nd Vista updates, then restart and run Addons)
/Vista3 (Install Vista Addons only)
/7x321 (Install 7 32-bit updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/7x322 (Install 2nd 7 32-bit updates, then restart and run Addons)
/7x323 (Install 7 32-bit Addons only)
/7x641 (Install 7 64-bit updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/7x642 (Install 2nd 7 64-bit updates, then restart and run Addons)
/7x643 (Install 7 64-bit Addons only)
FUTURE PLANS
-Add argument for running a given phase once.
-Wait for other suggested improvements.
APL.zip (82K)
downloads: 4
I wanted it to:
1)Run, installing updates for the given OS
2)Restart
3)Run again
4)Restart
5)Run, this time installing the Addons
In the end, I had to write a small application to accomplish this. I (creatively) named it AutoPatcher Launcher, or APL for short.
Setup is very simple:
1)Create a folder for each OS you would like and run apup.exe
1a)The folder names should be XP, Vista, 7x32, and 7x64
1b)These are the only operating systems supported at this time
2)Create an answer file for each OS called answer.aaf in its respective OS folder
3)Create a folder for the addons (named Addons) and run apup.exe
4)Create an answer file for each OS in the addons folder named after each OS
4a) XP.aaf, Vista.aaf, 7x32.aaf, and 7x64.aaf
Sadly this is a .NET 2.0 application, which means XP requires that to be installed first (.NET 2.0 comes with Vista and 7)
The solution is to use a batch script that prompts if you're running XP and then tries to install .NET 2.0 Framework, before rebooting and then automatically running the AutoPatcher.
I have included everything you need in the attached zip file to get started, including folder structure, a place holder for the .NET installer, a batch script for installing .NET for XP, and an autorun inf for use with insert-able media. The only thing you should need to do is download .NET 2.0 redistributable if you plan to use this with XP, download the autopatcher and set it up for each OS, and create your answer files.
You can download APL via the attachment to this post, or at http://www.mediafire...th8cmlshr6vvtab.
TECHNICAL DETAILS
APL uses the HKCU\SOFTWARE\MICROSOFT\WINDOWS\RunOnce key to start at boot.
APL supports arguments, but only one at a time:
/XP1 (Install XP updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/XP2 (Install 2nd XP updates, then restart and run Addons)
/XP3 (Install XP Addons only)
/Vista1 (Install Vista updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/Vista2 (Install 2nd Vista updates, then restart and run Addons)
/Vista3 (Install Vista Addons only)
/7x321 (Install 7 32-bit updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/7x322 (Install 2nd 7 32-bit updates, then restart and run Addons)
/7x323 (Install 7 32-bit Addons only)
/7x641 (Install 7 64-bit updates, plus all subsequent phases; i.e. restarting and running the 2nd, then restarting again and running Addons)
/7x642 (Install 2nd 7 64-bit updates, then restart and run Addons)
/7x643 (Install 7 64-bit Addons only)
FUTURE PLANS
-Add argument for running a given phase once.
-Wait for other suggested improvements.
APL.zip (82K)
downloads: 4
_def_x_
12 Feb 2011
Pretty bad timing if I do say so, when the project is done, finite', you post an app for what will soon be Unofficial and Unsupported releases. If your app actually works it wouldn't matter - the Unofficial warning - as long as you're creating the script you can trust the release and ignore the message.
What would have been nice is help with a script and maybe the project could have had a longer life, oh well.
What would have been nice is help with a script and maybe the project could have had a longer life, oh well.
JTok
15 Feb 2011
gUiTaR_mIkE, on 12 February 2011 - 05:47 PM, said:
Pretty bad timing if I do say so, when the project is done, finite', you post an app for what will soon be Unofficial and Unsupported releases. If your app actually works it wouldn't matter - the Unofficial warning - as long as you're creating the script you can trust the release and ignore the message.
What would have been nice is help with a script and maybe the project could have had a longer life, oh well.
What would have been nice is help with a script and maybe the project could have had a longer life, oh well.
Yeah, I caught that. What can you do though? Thought I'd share anyway. Maybe someone will get a little use out of it. For a time at least.
As for helping with the scripts, had I been able to be more active, and made myself aware sooner, I may have helped where and when I could. Alas, it was not to be.
_def_x_
15 Feb 2011
It's a nice gesture (your app). Who knows, the admin(s) may bring in new blood to give the project a future. I guess it's the existing people he wants to get rid of, no one really knows whats happening. Anyway 
dfdff3000
16 Feb 2011
It looks like a pretty decent idea for the future (if there ends up being a future for this project). I'm still having a hard time wrapping my head around the concept that it's ending primarily because of spam. AutoPatcher survived legal threats from Microsoft and still kept going once those concerns were addressed!! I continue to keep my fingers crossed that all is not lost. 
_def_x_
16 Feb 2011
Quote
I'm still having a hard time wrapping my head around the concept that it's ending primarily because of spam.
The sad thing is I really have no idea what has transpired here but it does appear the people who could allow the project to live on would rather it die, so be it.
