Jump to content
Piriform Community Forums

Winapp2.ini

Beta Testers
  • Content count

    6,343
  • 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 it'd be a better user experience to use a tool like Everything to do broad recursive searches for filetypes
  3. 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.
  4. 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.
  5. 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
  6. 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
  7. 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.
  8. 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.
  9. Winapp2.ini additions

    https://github.com/MoscaDotTo/Winapp2/issues/226
  10. 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
  11. 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!
  12. 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.
  13. Winapp2.ini additions

    winapp2ool has been updated, comes with some neat lil tidbits
  14. 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
  15. Winapp2.ini additions

    Is the Media Cache worth cleaning at all?
  16. 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
  17. Winapp2.ini additions

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

    Look forward to this in the next release when it comes Had never really considered it I guess I'm fairly sure this was always an option though.
  19. Winapp2.ini additions

    I also prefer the alphabetical sorting. It's straightforward, immediately understandable, and requires no foreknowledge of windows directory/registry hive hierarchy to format.
  20. Winapp2.ini additions

    Since the forums formatting appears to be breaking the diff formatting, a more readable version can be found here: https://paste2.org/DGfHNUzy
  21. Winapp2.ini additions

    I fixed a small bug in winapp2ool that was causing the diff module to print exceptions under some circumstances. Here is the changeset between my previous post (2018-01-25) and the current master file at the time of this post
  22. Winapp2.ini additions

    Yes. They're on my radar (and indeed some of the scaffolding is completed for WinappDebug's upcoming autocorrect functionality). Most of this release's front end changes were concerned with setting up a consistent menu system and exception handling.
  23. Winapp2.ini additions

    There is a new version of winapp2ool (v0.6) available for testing. Most of the changes are under-the-hood but you should see a little more prevention against loading files that don't exist or contain no content (eg. loading an empty file will present an error that the file is empty instead of just attempting to do whatever module work with an empty file under some circumstances.) There's also a new menu/output design that's fit to the size of the console window and consistent throughout the modules. The WinappDebug module's alphabetization checking has been tweaked a bit to organize entries that belong in the browser sections differently (via langsecref instead of specialdetect) Known issues: There may be some places where entering 0 to return to the menu fails to properly do so. I think I've caught all these but let me know if you find one. There may be some inconsistent grammar throughout menus. Again, if anything jumps out, do let me know. Diff might throw some exceptions under some circumstances, I'm currently looking into the cause of this. Bug reports are best left through GitHub but comments here are fine too. This should be fixed now. Opening winapp2ool.exe without an internet connection should produce an error against the update checker before printing the menu instead of simply crashing.
  24. Winapp2.ini additions

    I have this fixed on my side, I'm hoping to have some time within the next week to clean up and push the next update
  25. Winapp2.ini additions

    Would this be better suited to the Windows Subsystems * entry?
×