Jump to content
Piriform Community Forums

Winapp2.ini

Beta Testers
  • Content count

    6,307
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Winapp2.ini

  • Rank
    Friendly neighborhood addon manager
  • Birthday 25/01/1993

Contact Methods

  • Website URL
    http://www.mosca.to
  • ICQ
    0

Profile Information

  • Gender
    Not Telling
  • Location
    Long Island, New York
  • Interests
    Sleeping

Recent Profile Visitors

1,930 profile views
  1. Winapp2.ini additions

    Sorry about the rushed nature of the builds I had about 4 days from start-to-finish before I would (as I am currently) become busy with some school business, probably for the next week or so, so I wanted to get down what I could while the concepts were still somewhat fresh in my mind. WRT REMOVESELF I think this should only be used in instances like cache folders, where deleting the folders goes hand-in-hand with deleting their contents. Empty folders aren't necessarily junk or a privacy concern.
  2. Winapp2.ini additions

    Thanks! This has been fixed, which winapp2ool will probably inform you of, but will require a manual redownload
  3. Winapp2.ini additions

    A new version uploaded only just a few minutes ago is available. It now checks for updates against the GitHub version and notifies the user in the menu when an updated winapp2ool is available. Enjoy!
  4. Winapp2.ini additions

    I've uploaded a new version of winapp2ool that fixes both this and the numbering issue (which was in the trim module as a result of some refactoring) All modules have had their behavior modified, and the menus have all been tweaked to be more consistent as well
  5. I would guess that ICS here means Intelligent Cookie Scan and the value of this key is the CCleaner build during which you last ran the intelligent cookie scan.
  6. Winapp2.ini additions

    I have uploaded a new version that should address these issues: https://github.com/MoscaDotTo/Winapp2/blob/master/Tools/beta/winapp2ool.exe
  7. Winapp2.ini additions

    I have updated winapp2ool considerably and made available the source code. https://github.com/MoscaDotTo/Winapp2/commit/b69b08c54e70929c2ca8c33ec0a5fdec5f11b8cb Notably, I made a fix to trim such that it will actually respect the hive provided by Detect= entries, it previously ignored any markers such as HKCU, HKLM.. etc and checked all hives simultaneously, which can (strangely enough!) lead to "false" positives (eg. a key exists in HKLM but not HKCU, while the detect is for HKCU. Thus trim would count is as valid but CCleaner would never present this entry, presumably.)
  8. Winapp2.ini additions

    I've uploaded a new version of winapp2ool that should address both the ExcludeKey error checking in WinappDebug and the detectless entries being ignored in the trim module.
  9. Winapp2.ini additions

    I've just uploaded a new version of winapp2ool, give it a try. The trim module has been tweaked a bit to prevent it from outputting a bad ini file. FWIW I think there may be some bug in trim.bat because it also generated more entries for me, but some of them should not have been detected as being on my system.
  10. Winapp2.ini additions

    You may want to try running the .NET Repair Tool are you including the .ini extension when entering the file name? (you should be!) ' Have you tried running just the trim module? It doesn't call any code from diff so it should not trigger a crash in that module as far as I'm aware. Does the error still occur if you move to tool to a less privileged folder?(ie. downloads) Thanks for trying it out!
  11. Winapp2.ini additions

    The output is generated based on the file contents, so I must have used a version from before that PR was merged to produce it, or else it's absence in the later file would have triggered the "was removed" line. The next time I post a change log, this change will most likely make itself apparent.
  12. Winapp2.ini additions

    Here is a demo of the new multitool (winapp2ool): https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/beta Please give it a try, it includes a slightly improved WinappDebug, ccinidebug, a new module called "diff" that compares two winapp2.ini versions and outputs the changes, and a trimming module with an option to both overwrite the existing winapp2.ini file or to output to a new file called winapp2-trimmed.ini Recommended that you run it as an administrator, many of the functions don't work will without elevation. Trim especially, as it can't access certain registry keys without elevation and will as a result, erroneously trim entries from your file.
  13. Winapp2.ini additions

    This one IS a changelog.
  14. The "Birthday" place.

    Happy birthday Dennis! Just think of all the free cooling you'll get this summer with those new holes in the ceiling! Heat rises, after all.
  15. Winapp2.ini additions

    I've completed the basic work for this now actually. It's not ready for public release just yet, but it is functional. Here is an example of the output: NOTE TO READERS: THE BELOW IS NOT AN OFFICIAL CHANGELOG OF ANY SORT AND SHOULD NOT BE INTERPRETED AS ONE. IT IS SIMPLY THE OUTPUT OF A CLASS I AM TESTING THAT WILL EVENTUALLY REPLACE THE BACKBONE OF THE CURRENT SET OF TOOLS SUCH AS WINAPPDEBUG. I have provided it for feedback purposes only
×