Hiya, I maintain Winapp2.ini on the Piriform Forums (/winapp2.com), and I wrote this entry. The Piriform copy of the file is used as the CCEnhancer definitions. I'm going to reply to several posts at once, though I'm currently at work so I may get distracted The script does indeed target the log files generated by running MBAE, at least whichever version it was on when I wrote the entry. If the path has changed, it wont delete anything. Winapp2.ini is essentially a database and all entries are opt-in (disabled by default), users are encouraged to exercise caution when cleaning (analyze first!). No entries are intended to disrupt the functionality of any programs, possibly with the exception of the Steam Installers* entry, which prevents games from launching if they haven't been initialzed before their installers are deleted. WRT deleting many small files - it adds up, and some people like to purge all "useless" (to the end user) files before they do an image backup or whatever. As you said, it doesn't break the functionality of the program, it's really just an opt-in for folks who deem the files useless (we do vet what is and is not useless (most recently, here: http://forum.piriform.com/index.php?showtopic=32310&p=250202 and down)) Nope, and if you mention CCEnhancer on the Piriform Forums, no one will talk to you about it (per the developers request). Any inquiries about the script can be left in the winapp2.ini thread I linked above, any CCEnhancer questions can be posted on the Singular Labs forums http://singularlabs.com/forums/ Aye, everything is defaulted to opt-in (default=false) so nothing is cleaned without the user explicitly opting in to it (though a few times a few default=trues have snuck in, I've tried to maintain opt-in since 2010) If there are any other questions about anything, I'd be glad to answer them.
