Jump to content
Piriform Community Forums


Beta Testers
  • Content count

  • Joined

  • Last visited

Everything posted by Winapp2.ini

  1. Winapp2.ini additions

    Welcome! *** Please Read *** *** Thank you *** Link to download Winapp2.ini GitHub Direct Download Enjoy! Some tools: WinappDebug - A tool for detecting many potential errors in winapp2.ini. ccinidebug - A tool for organizing your ccleaner.ini and removing stale winapp2.ini entries from it ADVANCED USAGE AND TRIMMING How to make your own Winapp2.ini entry! (And if you do, feel free to post it here )
  2. Winapp2.ini additions

    I think items associated with VirtualStore locations are related to how Windows handles sandboxing / security when the UAC is enabled.
  3. Winapp2.ini additions

    Are the files process locked?
  4. The Firefox/Mozilla Thread

    Chrome has a similar feature that I've noticed but never seen discussed, so does Windows Explorer! I think this is something Microsoft is trying to take on as a UX problem (ie. unexpected restarts interrupt a user's workflow in a very destructive way) Timeline on Windows 10 and the upcoming (or released? I'm not sure) "Sets" feature I've seen talked about seem to be about remembering the context of your open applications and restoring them when appropriate.
  5. Winapp2.ini additions

    At this point yes, the features are mostly in their final state under the new menu system. I'll be working on creating documentation for it all soon. On a related note, I have intention to create likely one more module that executes combinations of the other modules tasks, so simplify the tool further.
  6. Winapp2.ini additions

    Winapp2ool has been (officially) updated to v0.85beta, existing previous versions should inform users of this.
  7. Winapp2.ini additions

    I created a "redux" version of Trim called TrimXP which targets .NET Framework 4: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/TrimXP This should be useful to anyone on WindowsXP who cannot otherwise run winapp2ool due to the .NET 4.6 Requirement The only concern I have is that I have never tested environment variable expanding on WindowsXP and don't know how/if some will work.
  8. Winapp2.ini additions

    A build of winapp2ool.exe with this fixed is available: https://github.com/MoscaDotTo/Winapp2/pull/245 It's not yet on the master as I've made significant changes to the code and want to make sure everything is still functional before pushing. Everything in my tests seemed OK though
  9. Winapp2.ini additions

    This is a bug (oversight regarding expanding wildcards) in Trim and will be fixed in an upcoming major update to the tool Thanks for pointing this out
  10. Winapp2.ini additions

    I think it'd be a better user experience to use a tool like Everything to do broad recursive searches for filetypes
  11. Winapp2.ini additions

    300 posts? There's over 7000! (but I suppose you probably meant pages) I don't think the thread needs cleaning. That's a lot of work for moderators and now that winapp2 itself is on GitHub it's a lot easier to track which changes actually make it into the file (when I was maintaining it alone and by hand, any changes I missed would be lost to the ages unless someone specifically audited for those changes and pointed out that I'd missed them). Overall I think that it'd be fitting for winapp3 contributions to be kept exclusively on GitHub. This is the winapp2 thread, and I think it'd be less confusing for everyone if it stayed that way.
  12. Winapp2.ini additions

    I don't think winapp3 is substantive enough yet to warrant its own thread or really even much discussion on this one besides update notifications. Any discussion about it is likely best kept to GitHub for the sake of keeping this thread on topic for now.
  13. Winapp2.ini additions

    This is the intended behavior. I had been working on finding unneeded parameterizations (eg log*.txt;log.txt -> log.txt is not needed because log*.txt covers it) but I didn't complete that work yet so I had intended to disable it. In the meanwhile, any wholly duplicate parameters should be caught properly by WinappDebug. Anything with wildcards is hit/miss (mostly miss) still. It should be noted that those errors are actually accurate in your output FileKey1=%CommonAppData%\CanonBJ\IJPrinter\CNMWindows|drvlog*;drvlog*.*;plmlog*.*;plmlog.*|RECURSE between plmlog*.* and plmlog.*, only plmlog*.* is needed
  14. Winapp2.ini additions

    I have a pending update for winapp2ool that could use some testing here's the PR that lists some of the changes: https://github.com/MoscaDotTo/Winapp2/pull/245 You can get the 0.85b executable here: https://github.com/MoscaDotTo/Winapp2/blob/591c4da686f5c9097a289d0a64389f2133c4ff65/Tools/beta/winapp2ool.exe Here's a photo showing some of the menu changes that have been put into place
  15. Winapp2.ini additions

    https://github.com/MoscaDotTo/Winapp2/issues/226#issuecomment-376043221 I updated this post with a small proof of concept tool. If anyone would be interested in maintaining a languages.ini meta file please let me know.
  16. Winapp2.ini additions

    https://github.com/MoscaDotTo/Winapp2/issues/226#issuecomment-376043221 I updated this post with a small proof of concept tool. If anyone would be interested in maintaining a languages.ini meta file please let me know.
  17. Winapp2.ini additions

  18. Winapp2.ini additions

    winapp2ool.exe has been updated Something not listed in the changes on the commit (pasted below) is that the application should no longer crash when you hand it an ini with no ; version string in it. I posted about the command line arguments here: https://github.com/MoscaDotTo/Winapp2/issues/200
  19. Winapp2.ini additions

    Merge has had its underlying behaviors changed since you posted this (namely how it handles sections with duplicate names between ini files) so I'll have to ask that you test with the newest build when its posted (hopefully tonight!) and see if this issue persists!
  20. Winapp2.ini additions

    I think I have an idea of the problem here and have a fix ready. Does your custom.ini have a "; version " string? or any ini comments (lines that start with ; ) at all? If not, try adding one and see if it works. I found a spot in the winapp2file constructor where an exception would occur if handed an inifile object with no comments. If that's the problem, the next build will fix it.
  21. Winapp2.ini additions

    winapp2ool has been updated, comes with some neat lil tidbits
  22. Winapp2.ini additions

    Capture software didn't seem to see the "this file has been modified by an external program" prompt in notepad++.... anyway here's a video of winapp2ool fixing up winapp2.ini.. https://streamable.com/1z3wg
  23. Winapp2.ini additions

    Is the Media Cache worth cleaning at all?
  24. Winapp2.ini additions

    I think it's fruitless to separate this entry without also including a warning that informs the user of the restart requirement
  25. Winapp2.ini additions

    I believe the dvdcss folder is generated by applications that use libdvdcss https://www.wikiwand.com/en/Libdvdcss