Autopatcher.net

...probly a good thing I have the archive saved, then.

Now I just need to find which version of AP will run them correctly... ~:L

Having a different AP to do XP isn't a big thing for me, it's EOL so I just need to be able to bring a machine up to the endpoint; I can stow the XP archive and the older AP together separate from the newer stuff. It's just a matter of getting a copy, since the 6.x versions I have don't work. 6.1.32...

...I just did all this through AP6.1.32 not very long ago and it worked fine. Strike that, I just remembered I didn't use AP on the last machine I installed to before this one - was a quick&dirty install to check function of some other hardware. lemme see if I can find 5750 like you said... nop...

I have tried it with both AP6.1.4 and 6.2.0 - Sweeper sez the archives are legit, but it hits me with the blizzard of barf with either version while installing.

Im'a wipe the drive and try a fresh XP reinstall one more time - apparently I'm Entropy Incarnate right now...

Pulled fresh copies of all .NET files with latest scripts, AP6.1.4 shows official, AP6.2.0 shows thppppbt; Im'a assume that's something with 6.2.0.

well, spit - now something else is wrong; none of the updates install - they fail out with a message box about using command-line switches...

Thankee, sir. :) ETA: crap - spoke too soon; throwing a shoe in a different way now: Sweeper Has Started At 5/27/2016 12:52:26 AM Version: 2.0.0 Starting Sweeper From: E:\autopatcher Parsing Detected Commandline Arguments... Sweeper is running with the following arguments: verbose Initialization Suc...

much obliged, sah.

...well, pish. now it can't find "windows_xp_x86.apm" - Sweeper apparently sees everything else in the XP folder OK now, though.

might I talk you out of a copy?

...in the interim, do you happen to have the original KB3136000 package that I can stick in my folder to get it to quit yowping at me, or has the script been updated to use the -v2 package?