Autopatcher v6.2

In this area, you will find test programs and scripts.
User avatar
Whatacrock
Release Maintainer
Release Maintainer
Posts: 1967
Joined: Mon Oct 28, 2013 10:47 am
Location: Australia
Contact:

Re: Autopatcher v6.2

Post by Whatacrock »

Downloaded and test this one.... Yipeeee NO more "Yikes" I can live with the current behavior.
► Show Spoiler
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher v6.2

Post by TheAPGuy »

hmm... you did not get an error for not being able to delete a batch file. Yet you say it leaves one. :(

Also... it DID pop up a msg box telling you it was unable to delete the directory right?
User avatar
Whatacrock
Release Maintainer
Release Maintainer
Posts: 1967
Joined: Mon Oct 28, 2013 10:47 am
Location: Australia
Contact:

Re: Autopatcher v6.2

Post by Whatacrock »

As far as I can see it is the behavior of this system NOT autopatcher.

I did get the dialog box... Leave it as it is, I just get use to the quirks that get dished up..
:) :)
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher v6.2

Post by TheAPGuy »

That is the same drive that is still giving you permission problems for doing anything right?
User avatar
Whatacrock
Release Maintainer
Release Maintainer
Posts: 1967
Joined: Mon Oct 28, 2013 10:47 am
Location: Australia
Contact:

Re: Autopatcher v6.2

Post by Whatacrock »

My apologies that log was from the boot drive, temporarily copied AP to it for a test run, and saved the log for posting.

I did run AP this morning on the drive causing issues and compared the log files, the result is they are identical.

Am going to copy AP to a portable device and run the test once more.. results to come

Tested from a portable hard drive and results are identical to previous two tests..
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher v6.2

Post by TheAPGuy »

wait... so your OS, not your HD is not letting you delete the temp directory? I don't know what to say really. It works exactly as expected in my VM of XP x64 and windows 10. This is odd behavior.
User avatar
Whatacrock
Release Maintainer
Release Maintainer
Posts: 1967
Joined: Mon Oct 28, 2013 10:47 am
Location: Australia
Contact:

Re: Autopatcher v6.2

Post by Whatacrock »

Yes it works fine in my VM's as well, just don't play ball in my main system(this one)
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher v6.2

Post by TheAPGuy »

ok... I will put this version to main list.
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher v6.2

Post by TheAPGuy »

OK Its on the main list... will update the sites front page in a min.

Changes this version 6.2.14
Fixed the executable giving occasional permission errors (always happens for WAC though until this version)
Fixed temp directory deletion errors giving YIKES! crash screen. Now just pops up dialog box with warning.
IF it failed to delete the temp batch file it "SHOULD" pop up an "retry or cancel" dialog box.
AP will NO LONGER auto delete APUP files and old sweeper... it WILL silent warn you in the log file it found them though.
themadkansan
Posts: 60
Joined: Tue Jan 07, 2014 8:25 am

Re: Autopatcher v6.2

Post by themadkansan »

OK, trying 6214 on a fresh bare-metal install of Win7sp1-64bit with previously-downloaded archive folder, getting crash on launch:

"Run-time error '339':
Component 'RICHTX32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid."

This install media worked correctly on the test machine and 6209 worked correctly with it with the same archive folder, but not yet updated with the 11/8 scripts. Nothing was done to the install before trying to run 6214.

any ideas?

(also: 6214 worked on previously updated machines with no errors displayed.)
Post Reply