AutoPatcher Forum

This little beauty will sweep your module folder clean of all files that don't belong there. Its still in testing but preliminary results are golden. I will enable apup to use this in the future. It will remain an external program so that you may use it at any time.

Sweeper.exe It uses your RTI files to figure out what needs to go so if your missing RTI files it WILL delete things if you hit yes or have it on quiet mode.

edit: my bad forgot to say something, unzip it into your apup folder next to apup.exe
edit2: Newer version with \fast switch and sweet broom icon made by me(not really good but, whatever).
edit3: It will remove empty directories that it clears out.
edit4: new icon(s), added help commands, fixed up the empty dir removal, auto scrolling of log if your watching it.

Here are the following accepted commands:
/verbose - Fill the log file with more stuff like Missing files or md5 and size errors(unless you combine with \fast)
/quiet - Don't show anything, will auto delete files.
/test - Will not delete but will still show in log as if it did.
/fast - Skips doing md5 and size tests just checks file names(md5 and size tests are from AP code that I left in because they are useful). <--- super fast and shouldn't have any problems using this always(might make this default)

Known issues:
Doesn't delete empty dirs. (DOH, ohh well it will still make things official. I will fix it when I get more time.) Fixed(it will only delete directories that it makes empty though) Fixed again... Removes all empty dirs it finds

Apup_1_4_3.zip(not a link)
Size: 1,492,702 bytes(yes the attachment link below shows a different size due to the way it calculates size)
MD5: 50B21AA56DA99D29A13D0AC4F8C5631C
Edited by ViroMan, 03 January 2013 - 12:41 AM.

Newer version possibly final.
So I am happy with its current status. Unless anyone has anything to say about it. I will probably leave the utility as is and I will release another version of apup that will make calls to it.

For those of you saying hey wait... what about if I create a test script that isn't signed will it delete my stuff... answer... YES! UNLESS you place a command in your script that will disable running of the sweeper. I am not sure what the format of the command would be yet. Possibly Test=true or something like that. I however might make it not run sweeper if your running your own script via /localscript from command prompt.

Running sweeper WILL be mandatory and automatic(unless Test=true command is given in script) after next version of apup is release. We will remove all preaction deletes that delete things script side. Its a complete waste of space to make the scripts 1/4th larger then they need to be in order to delete old stuff when a less then 1 second run of sweeper can remove them faster then running all them batch commands to delete files. Not to mention sometimes things are forgotten to delete.
Edited by ViroMan, 22 December 2012 - 12:54 AM.

ok... so apup and sweeper are now "ready" for testing. I am pretty sure its ready for public but, since this could potentially delete whole modules dir I want more testing.

Apup1_4_2.zip is attached. It has the new apup + sweeper and a fancy new icon for apup... same but new.


Sweeper is on by default now. You can turn it off though the options window. For those of you that said... what about my scripts and sweeper deleting things... you can place a hidden setting in your apup.ini file that will allow sweeper to run but, not delete things. SweeperTesting=1. I say hidden because it won't show up in the ini file unless you place it in there. Reason its there instead of just turning sweeper off is that you can get a nice log if things that it finds... extra files(it wanted to delete) or missing files.
Edited by ViroMan, 03 January 2013 - 12:33 AM.

I see 4 downloads... anyone have any comments?

Tried running Sweeper /? from command prompt to ascertain options - no luck; should be added. Did run Sweeper /test - did not expect to get a Delete files Yes/No option in Test mode - should not have occurred.

I believe VM indicated in his post above that you had to add SweeperTesting=1 to the APUP.ini. Looks like he changed his mind about some of the switches such as /test.
Edited by click-click, 30 December 2012 - 11:51 AM.

click-click is correct....you need to add manually SweeperTesting=1 to your apup.ini file......to turn it off then SweeperTesting=0.

Having tested this application thoroughly(and made a few mistakes) it runs efficiently.

Works very very fine! And It's amazing!

Works fine for a first release! I did, however, get the infamous prj.updater error on my most cluttered folder. The files were deleted correctly, and I cannot reproduce the error on any of my other folders.

Notes: I am running APUP 1.4.0.2. Sweeper and the new APUP are both set to 'Run as Administrator'. NTFS permissions should be OK.
I have separate folders for each OS (XP, Vista, 7, etc.) and separate folders for Extras, Adobe, DotNet, and MS Redist. Tried those and it works fine without a plethora of prj.updater errors...could have been just a really messed up folder with a ton of clutter (reduced to 146MB from 1GB+). I did have my DotNet, Adobe, and MS Redists all in with Extras initially which is why the folder got so large, so maybe this error won't be very common.

One small suggestion (perhaps this should go under Feature Requests): The new APUP 1.4.0.2 w/ Sweeper should be added to the releases.list. The UI is entirely different and is a vastly visual upgrade all around =) I had to login to download the 1.4.0.2 update, so perhaps it could go under /apengine like other releases.

I would also like in inquire about Sweeper with a couple questions:
1: May I ask what language Sweeper is written in?
2: It appears to choose deletions based on the existence of .rti files, even if certain releases are unchecked after being enabled/downloaded previously.
Are there any plans to configure behavior to sweep based on which releases are selected?
3: Are there any plans to open source this tool (just sweeper)?
4: Are there any plans in the future to make it look closer to APUP in the (possibly distant) future?

Very useful tool, BTW!

The sweeper tool can be run by iteslf or run by apup. When its run by apup it runs with the commands /quiet /fast. This tells it NOT to show its gui and runs quick checks by file name only(no md5 or size). When you put in SweeperTesting=1 in the apup ini, apup will pass /test to sweeper as well.

If you are running sweeper yourself, you should pass /test in if you don't want it to delete things since it does NOT read apup.ini.

For script writers it is recommended to pass in the following 2 commands /verbose /test
with /fast off and /verbose on it will perform md5's and size checks and report any discrepancies it finds as well as pretending to delete things.

the new apup has not been added to the main list yet since its still in testing.

1) Sweeper is written in VB since its the only IDE I have access to atm. MY IDE of choice, Borland Builder 6 C++(its old) is on my computer and I am currently using my mothers computer(she doesn't use it anyways).

2) Yes sweeper uses the rti files to choose what is deleted. Basically anything NOT listed in the found valid rti's are deleted. I am going to create one more file type it will read so that people can make their own scripts that are not signed and not have their files deleted.

3) There are no plans to open source this tool atm and I really don't see a reason for it.

4) The tool doesn't need to look closer to apup since its just a tool that probably won't be run by most users. I made it an external program instead of part of apup so that people who make their or scripts can use it.

sorry about not having /? in. Forgot about that. The next one will.
Edited by ViroMan, 30 December 2012 - 11:14 PM.

Quote

Just noticed tat you said that. Were you running sweeper through apup or manually? Did you remember the error it threw.. like saying what line number it was?
Edited by ViroMan, 30 December 2012 - 11:36 PM.

ViroMan, on 29 December 2012 - 09:13 PM, said:

Well, I'm not sure what to think! A friend ran Sweeper, they said when Sweeper finished their speakers were missing, literally were missing from their desktop.

I ran Sweeper - now my wallet is missing.

HTH -:-

I got the version 1.4.2 and it worked fine. What I would to see when I run it is the version number. That way I would know I am running the latest version. Keep up the great work.
Edited by Black Ghost, 02 January 2013 - 09:40 PM.

um... it does say the version number. Not in the title but the log it shows.. it shows your the log that its creating on the fly. I will however make it show the version in the title.

OP updated with new zip. Apup and sweeper both changed. PS using max compression(not ultra) in the zip file. Unsure if windows can unzip it. Tell me if you guys have problems.

Downloaded APUP1_4_3.zip and it extracted OK to \AutoPatcher folder. (Used 7z version 9.30 to extract in Win7 Ultimate 64bit - no problems.)
Better now with version in title bar.
Get list > Available Releases > top item: AutoPatcher Updater 1.4.0.0 - this should be updated to match latest version.
No listing for XP Pro x64 w/SP2 (Yes, I know - change to releases2.list - why not combine them?)

Releases2.list
Get List > Available Releases > top item: AutoPatcher Updater 1.3.0.1 - a bit out-of-date.

1.4.0 is still the official version. 1.4.3 is beta version and may yet go one more update. I will remove 1.3 since its so horribly old.

Not going to combine the lists because as stated the second list is for testing with. Things on the second list may wipe out an AIO you have for example. Not know to you guys but, at one point early in WAC's x64 script development, it was wiping out his drive lol. Lucky he was testing on a USB stick otherwise it would have removed his OS. This is not something we want on the main list even if it said testing or beta.
Edited by ViroMan, 03 January 2013 - 10:20 PM.

In regards to the infamous prj.updater error, I was only able to see it the one time (in my most cluttered folder). Since it did the deletions regardless of the error, I can't reproduce it (yet), but I can (hypothetically), do some re-creation of the most cluttered folder and see if it does it again. There were so many popups of the error (thus, I didn't take the time to note the line #'s), due to the clutter of the folder and this was on apup 1.4.2. I will try to simulate the same tests under 1.4.3 and see if the problem is fixed. If it happens again with the new version, I can take notes on the line number(s) and report back. It could have been an extremely rare scenario since I have been using apup since it was first introduced (and AP way before that)...thus, my folder was years in the making. The tool absolutely rocks...saved me a ton of disk space =)

I did update 1.4.3 to push most any errors you see to the log file as well.