Forum rules
1. Try to give more than you take, when possible.2. When posting for help, include d7x/dSupportSuite version, OS details, and steps to reproduce the issue.3. Start a new topic for a new problem, don't just post on existing topics that are NOT your EXACT problem.4. SEARCH THE FORUMS BEFORE STARTING A NEW TOPIC.

I’ve messed with Crap killer a little. The manual version seems ok, but I don’t dare try the automated version as I just don’t trust it to decide things for me. The one thing I don’t like is that when the manual version is done running and it didn’t find anything it just goes away. It would be nice if it stopped and said it didn’t find anything. Bill

Took me a little to figure out it was doing that. I started it manually and walked away, expecting to come back to a list but it was gone. Finally sat and watched it find nothing and poof.

I've given feedback on its page that I'd like to see a little clearer usage in it -- put the filter stuff at the top of the script for easier editing, make a way for exceptions (if they're there, they're not obvious). I, for example, want to be able to exclude the Google toolbar as I have enough customers that do use it.

I looked at this batch script not long ago and felt it was a little 'young' for inclusion in d7. I don't like the 'automated' option since it is the author of the app who decides what gets removed and what does not - it should be up to you, fully configurable. Well, it IS fully configurable as it is just a batch script, however not everyone has this knowledge, and updating the script from the author would overwrite your personal modifications and require you to re-code them.

Probably great for those who remove everything, as Xander pointed out there are customers who do use certain toolbars. For me, it would be better re-written to use whitelist/blacklist functionality. It could be coded to read line by line a plain text file with a rule set instead of 'hard coding' them into the batch... If it ever gets to that point I'll consider inclusion in d7 but until that time I don't think it's a good fit.

EDIT: not to mention this exact functionality can be duplicated with dUninstaller functions and definition files, especially now that I've updated it to match partial strings in the definitions, so it's really quite redundant for d7 users who are actually using d7 native functionality to it's full potential in that area...