Jump to content


Beta Testers
  • Posts

  • Joined

  • Last visited

Everything posted by Winapp2.ini

  1. A new winapp2ool for your consideration: https://github.com/MoscaDotTo/Winapp2/pull/318/commits/976dd4c0885ba3d47e04330b062956dc2e8f5e75
  2. The LevelDB Logs generated by Google Chrome extensions are not logs in the conventional sense we usually approach with intention to delete. They hold buffer data for the LevelDB storage. https://github.com/google/leveldb/blob/master/doc/impl.md https://github.com/MoscaDotTo/Winapp2/issues/320
  3. I think these FileKeys should be folded into either Windows Logs * or Windows Subsystems * rather than have their own entry, good find
  4. A new version of winapp2ool.exe is available for testing (not yet pushed to master) Should be of particular interest to WindowsXP users, as there is now a version that should work on your system. Please let me know if anything jumps out as super broken. https://github.com/MoscaDotTo/Winapp2/pull/318
  5. This error wasn't happening in my development environment (probably due to the nature of debugging applications) but it should be fixed in the next winapp2ool update. The application is intended to be usable when offline (with the exception of online functions) If using .NET 4.5.2 you should also see a message on the menu informing you that the tool requires .NET 4.6 but 4.6 is only required to use TLS 1.2 for downloading the executable. Everything else should work as expected
  6. I think items associated with VirtualStore locations are related to how Windows handles sandboxing / security when the UAC is enabled.
  7. 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.
  8. 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.
  9. Winapp2ool has been (officially) updated to v0.85beta, existing previous versions should inform users of this.
  10. 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.
  11. 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
  12. 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
  13. I think it'd be a better user experience to use a tool like Everything to do broad recursive searches for filetypes
  14. 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.
  15. 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.
  16. 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
  17. 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
  18. 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.
  19. 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.
  20. https://github.com/MoscaDotTo/Winapp2/issues/226
  21. 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
  22. 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!
  23. 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.
  24. winapp2ool has been updated, comes with some neat lil tidbits
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.