Jump to content

Winapp2.ini

Beta Testers
 View Profile  See their activity

  • Posts

    6,470

  • Joined

  • Last visited

 Content Type 

Posts posted by Winapp2.ini

    Winapp2.ini additions

    in CCleaner

    Posted

    2 hours ago, Nergal said:

    I understand zero percent of this post.  What's the problem and what's the edit of ccleaner.ini needed, or is an edit of winapp2.ini what's needed but I still don't know what edit you say is needed?

    I believe back_track is referring to the alphabetization of the entries in the CCleaner application pane, where it prioritizes entries with spaces over those without. (eg. Origin* comes after Origin Installers*, but based on the bottom set of entries, I imagine that Origin * would precede Origin Installers* ). Changing entry names however restores their disabled state because CCleaner does not detect that an entry's name has been changed and instead detects it as a new entry, requiring the end user to reconfigure their settings after any name changes (via the UI or via ccleaner.ini)

    Winapp2.ini additions

    in CCleaner

    Posted

    It does appear the application no longer works. It does still generate files if run, however, despite its non-working state.  Tested with the version found on FileHippo. I'm all for removing it since any reasonable user would probably have uninstalled the non-working application (Soluto themselves seem to have moved on to some slightly different business model using the same name)

    Winapp2.ini additions

    in CCleaner

    Posted

    On 21/11/2017 at 21:23, mta said:

    I thought Opera was natively supported by CC, that is, no need for winapp2.ini as it's in winapp.ini ?

    I'll do an audit for CCleaner overlap after the upcoming refactor

    Also for the interested, I've recently updated WinappDebug with some nifty new features (including checking alphabetization of FileKeys, RegKeys, and entries, numbering for FileKeys, RegKeys, Detects, and DetectFiles, and some checks to make sure RECURSE and REMOVESELF entries are formatted properly) It also spits out the number of entries in the file at the end.

    Running it on the current release is a doozy...

     

     

     

    (Side note: that number drops really quickly while actually fixing the errors, assuming you remember to check your numbering..... ;) - it also doesn't really handle numbers too well either.. :lol: )

    The Firefox/Mozilla Thread

    in Software

    Posted

    A bit late but Stylo is ready for testing in nighty...

     

    https://blog.nightly.mozilla.org/2017/07/25/stylo-is-ready-for-community-testing-on-nightly/

     

    in my experience, very few issues with it. No generally perceivable difference in rendering or performance (yet)

     

    QFEN:

    17: https://ehsanakhgari.org/blog/2017-07-28/quantum-flow-engineering-newsletter-17
    18: https://ehsanakhgari.org/blog/2017-08-04/quantum-flow-engineering-newsletter-18

    19: https://ehsanakhgari.org/blog/2017-08-11/quantum-flow-engineering-newsletter-19

     

    TWIF:

    21: https://blog.nightly.mozilla.org/2017/08/02/these-weeks-in-firefox-issue-21/

    22: https://blog.nightly.mozilla.org/2017/08/16/these-weeks-in-firefox-issue-22/

     

    PEN:

    9: https://dolske.wordpress.com/2017/07/24/photon-engineering-newsletter-9/

    10: https://dolske.wordpress.com/2017/08/01/photon-engineering-newsletter-10/

    11: https://dolske.wordpress.com/2017/08/04/photon-engineering-newsletter-11/

    12: https://dolske.wordpress.com/2017/08/13/photon-engineering-newsletter-12/

     

    Photon is pretty near complete at this point

     

    WebRender Newsletter #1:  https://mozillagfx.wordpress.com/2017/08/16/webrender-newsletter-1/

     

    I've been testing WR for some time, still pretty buggy, but lots of promise.

     

    64 Bit is now the default on 64bit windows:

    https://blog.mozilla.org/firefox/firefox-64-default-64-bit-windows/

     

    There's also some new test pilot experiments:

    https://testpilot.firefox.com/experiments?utm_source=testpilot-dev

    The Firefox/Mozilla Thread

    in Software

    Posted

    ​

    ​

    ​

     

    They aren't dropping 32-bit support. They are just going to use a universal installer so 64-bit users get 64-bit version and 32-bit still have 32-bit. It's not a big deal anymore since XP and Vista is dropped and only like 5% of Windows 7 users is 32-bit. Plus dropping 32-bit build, when they do, would save some development time slightly not having to deal with 32-bit and 64-bit.

     

    32-bit can get 4gb ram and 64-bit can reach 3 exabytes of ram, but I don't think ram is the reason why they are switching. Having around 10 tabs open only consumed 2-3gb ram, so it's still enough for 32-bit users.

     

    By the way, is there/has there been any news if Mozilla will extend the 52ESR branch? I thought I heard at one point that it was going to be discussed?

     this page: https://hardware.metrics.mozilla.com/#detail-browser-share-os-32-64

    suggests that around 22% of active firefox installs are on 32bit OS' (thus cannot even install 64bit software), so I don't think Mozilla will be dropping 32bit support anytime soon. As you said, this is more geared towards migrating 32bit fx on x64 hardware to 64bit fx.

    I don't think they'll be extending the 52 ESR beyond its expiration date of August 2018

    ​

    ​

    The Firefox/Mozilla Thread

    in Software

    Posted · Edited by Winapp2.ini

    "We don't expect 64-bit Firefox to have any performance improvements over 32-bit" :mellow:

    Based on the discussion there, seems to be primarily a stability choice to move to 64bit.

    ​

     

    ​

    - 64-bit content process crash rate is about the same as 32-bit for

    users with 2 GB and about 20% less with 2+ GB!

     

    - 64-bit browser process crash rate is about the same as 32-bit for

    users with 2 GB and about 20% less with 2+ GB!

     

    - 64-bit plugin process crash rate is about 50% less than 32-bit for

    users with 2 GB and 80% less with 2+ GB!

     

    Moving to 64bit alone doesn't carry (m)any performance enhancements, but it does allow for better security (ASLR) and fewer out-of-memory situations (64bit applications use by default more memory due to the larger register size required by 64bit which is a bit of a regression, but the upper limit of total memory use for 64bit apps is much higher than 32bit ones)

     

    Also, PEN #9:

    https://dolske.wordpress.com/2017/07/24/photon-engineering-newsletter-9/

     

    Edit:

     

    ​Firefox Roadmap for Flash End of Life:

    ​https://blog.mozilla.org/futurereleases/2017/07/25/firefox-roadmap-flash-end-life/

    ​

    Stylo is Reader for Testing in Firefox Nightly:

    https://blog.nightly.mozilla.org/2017/07/25/stylo-is-ready-for-community-testing-on-nightly/

     

    Make Firefox Better With Pioneer:

    https://medium.com/firefox-context-graph/make-firefox-better-with-pioneer-10c82d0f9301

     

     

     

    The Firefox/Mozilla Thread

    in Software

    Posted

    Migrating 32bit Firefox installs on 64bit Windows to 64bit installs:

    https://groups.google.com/forum/#!topic/mozilla.dev.platform/hlCGG_Hib1w

     

    PLANS:

    * In Firefox 55 (August 8), the Windows stub installer will default to
    64-bit Firefox for eligible users (Win64 and 2+ GB RAM).

    * In Firefox 56 (September 26), we will migrate existing eligible 32-bit
    Firefox users to 64-bit. About 70% of Windows Firefox users currently
    run 32-bit Firefox build on Win64. Nearly all of these users can be
    migrated to 64-bit Firefox.


    Switching to TaskCluster Windows Builds on July 26th 2017:
    https://groups.google.com/forum/#!topic/mozilla.dev.platform/pOSncDUVids

    PEN 8:
    https://dolske.wordpress.com/2017/07/05/photon-engineering-newsletter-8/

    TWIF 20:
    https://blog.nightly.mozilla.org/2017/07/19/these-weeks-in-firefox-issue-20/

    QFEN:
    15: https://ehsanakhgari.org/blog/2017-07-07/quantum-flow-engineering-newsletter-15
    16: https://ehsanakhgari.org/blog/2017-07-21/quantum-flow-engineering-newsletter-16

    ​

    ​

    Avast aquires Piriform

    in Software

    Posted

    ​

     

    I remember the heady days when this forum was CCleaner only, with an easy on the eye blue colour scheme.

     

    Can't see the colour scheme coming back but a CCleaner only forum was so much less hassle.

     

    Maybe my optimism is getting carried away.

    I miss that blue theme.

    The Firefox/Mozilla Thread

    in Software

    Posted

    Some updates...

     

    QFEN:

    11: https://ehsanakhgari.org/blog/2017-06-02/quantum-flow-engineering-newsletter-11

    12: https://ehsanakhgari.org/blog/2017-06-09/quantum-flow-engineering-newsletter-12

    13: https://ehsanakhgari.org/blog/2017-06-16/quantum-flow-engineering-newsletter-13

    14: https://ehsanakhgari.org/blog/2017-06-23/quantum-flow-engineering-newsletter-14

     

    TWIF:

    19: https://blog.nightly.mozilla.org/2017/06/21/these-weeks-in-firefox-issue-19/

     

    PEN:

    5: https://dolske.wordpress.com/2017/06/08/photon-engineering-newsletter-5/

    6: https://dolske.wordpress.com/2017/06/15/photon-engineering-newsletter-6/

    7: https://dolske.wordpress.com/2017/06/22/photon-engineering-newsletter-7/

     

    Date/Time inputs enabled on Nightly:

    https://blog.nightly.mozilla.org/2017/06/12/datetime-inputs-enabled-on-nightly/

     

    Firefox Focus on Android:

    https://blog.mozilla.org/blog/2017/06/20/firefox-focus-new-to-android-blocks-annoying-ads-and-protects-your-privacy/

     

    An Inside Look at Quantum DOM Scheduling:

    https://hacks.mozilla.org/2017/06/an-inside-look-at-quantum-dom-scheduling/

     

    Introducing HumbleNet:

    https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cross-platform-networking-library-that-works-in-the-browser/

     

    Designing for Performance:

    https://hacks.mozilla.org/2017/06/designing-for-performance-a-data-informed-approach-for-quantum-development/

     

    Powerful new additions to the CSS Grid Inspector:

    https://hacks.mozilla.org/2017/06/new-css-grid-layout-panel-in-firefox-nightly/

    Winapp2.ini additions

    in CCleaner

    Posted

    Are you sure those changes are working? I think something went wrong.

     

    [Adobe Photoshop Elements*]

     

    -FileKey1=%AppData%\Adobe\Elements Organizer\*\Organizer|*.txt;status.dat (one subfolder between)

    +FileKey1=%AppData%\Adobe\Elements Organizer*\Organizer|*.txt;status.dat (no subfolder)

     

    [Adobe Premiere Elements*]

     

    -FileKey1=%AppData%\Adobe\Common\Thumbnail Cache|*.*|RECURSE (all files = *.*)

    +FileKey1=%AppData%\Adobe\Common\Thumbnail Cache|.|RECURSE (missing asterisks)

     

    -FileKey3=%Documents%\Adobe\Premiere Elements\*|*.log (one subfolder between and all log-files = *.log)

    +FileKey3=%Documents%\Adobe\Premiere Elements*|.log (no subfolder and missing asterisk)

     

    -FileKey4=%Documents%\NewBlueFX\Logs|*.txt (all txt-files = *.txt)

    +FileKey4=%Documents%\NewBlueFX\Logs|.txt (missing asterisk)

     

    Very strange, not sure what happpened but will fix. Likely an issue with GitHub formatting and copy/paste :)

    The Firefox/Mozilla Thread

    in Software

    Posted · Edited by Winapp2.ini

    All CSS properties supported by Gecko now supported by Stylo:

     

    https://groups.google.com/forum/#!topic/mozilla.dev.servo/9jZtdX1pAQA

     

    Race Cache with Network:

     

    https://groups.google.com/forum/#!topic/mozilla.dev.platform/fvCmc6kR9Uk

     

    PEN #3:

     

    https://dolske.wordpress.com/2017/05/30/photon-engineering-newsletter-3/

     

    PEN #4:

     

    https://dolske.wordpress.com/2017/05/31/photon-engineering-newsletter-4/

     

    Goodbye PNaCL, Hello WebAssembly!

     

    https://blog.chromium.org/2017/05/goodbye-pnacl-hello-webassembly.html

     

    including this because Mozilla is heavily involved in WebAssembly and one of its precursors, asm.js. Hooray open standards!

     

    Aurora gets swapped out for Nightly on the Play Store:

     

    http://www.androidpolice.com/2017/05/30/mozilla-replaces-firefox-aurora-play-store-listing-firefox-nightly/

    Winapp2.ini additions

    in CCleaner

    Posted

    Maybe we could just use 1 detect for them both?

     

    Adobe Photoshop Elements could be Detect=HKCU\Software\Adobe\Photoshop Elements

     

    Adobe Premiere Elements could be: Detect=HKCU\Software\Adobe\Premiere Elements

    Agreed

    Winapp2.ini additions

    in CCleaner

    Posted

    Revised Entries

    Added support for Adobe Photoshop Elements 14, 15 & Adobe Premiere Elements 14. 15

     

    [Adobe Photoshop Elements*]

    LangSecRef=3023

    Detect1=HKCU\Software\Adobe\Photoshop Elements\11.0

    Detect2=HKCU\Software\Adobe\Photoshop Elements\12.0

    Detect3=HKCU\Software\Adobe\Photoshop Elements\13.0

    Detect4=HKCU\Software\Adobe\Photoshop Elements\14.0

    Detect5=HKCU\Software\Adobe\Photoshop Elements\15.0

    Default=False

    FileKey1=%AppData%\Adobe\Elements Organizer\*\Organizer|*.txt;status.dat

    FileKey2=%CommonAppData%\Adobe\Elements Organizer\Catalogs\My Catalog|face.thumb.9.cache;thumb.5.cache

    FileKey3=%CommonAppData%\Adobe\Elements Organizer\Catalogs\My Catalog|WaldoData\waldo.cache

    FileKey4=%CommonAppData%\Adobe\Photoshop Elements\File Agent|WatchFolder.3.cache

    FileKey5=%LocalAppData%\VirtualStore\ProgramData\Adobe\Elements Organizer\Catalogs\My Catalog|face.thumb.9.cache;thumb.5.cache

    FileKey6=%LocalAppData%\VirtualStore\ProgramData\Adobe\Elements Organizer\Catalogs\My Catalog|WaldoData\waldo.cache

    FileKey7=%LocalAppData%\VirtualStore\ProgramData\Adobe\Photoshop Elements\File Agent|WatchFolder.3.cache

    RegKey1=HKCU\Software\Adobe\Elements Organizer\11.0\CurrentMediaFilePath

    RegKey2=HKCU\Software\Adobe\Photoshop Elements\11.0\common\settings\Elements MRU

    RegKey3=HKCU\Software\Adobe\Photoshop Elements\11.0\CurrentMediaFilePath

    RegKey4=HKCU\Software\Adobe\Photoshop Elements\11.0\VisitedDirs|STARTUPIMAGEDIRECTORY

    RegKey5=HKCU\Software\Adobe\Elements Organizer\12.0\CurrentMediaFilePath

    RegKey6=HKCU\Software\Adobe\Photoshop Elements\12.0\common\settings\Elements MRU

    RegKey7=HKCU\Software\Adobe\Photoshop Elements\12.0\CurrentMediaFilePath

    RegKey8=HKCU\Software\Adobe\Photoshop Elements\12.0\VisitedDirs|STARTUPIMAGEDIRECTORY

    RegKey9=HKCU\Software\Adobe\Elements Organizer\13.0\CurrentMediaFilePath

    RegKey10=HKCU\Software\Adobe\Photoshop Elements\13.0\common\settings\Elements MRU

    RegKey11=HKCU\Software\Adobe\Photoshop Elements\13.0\CurrentMediaFilePath

    RegKey12=HKCU\Software\Adobe\Photoshop Elements\13.0\VisitedDirs|STARTUPIMAGEDIRECTORY

    RegKey13=HKCU\Software\Adobe\Elements Organizer\14.0\CurrentMediaFilePath

    RegKey14=HKCU\Software\Adobe\Photoshop Elements\14.0\common\settings\Elements MRU

    RegKey15=HKCU\Software\Adobe\Photoshop Elements\14.0\CurrentMediaFilePath

    RegKey16=HKCU\Software\Adobe\Photoshop Elements\14.0\VisitedDirs|STARTUPIMAGEDIRECTORY

    RegKey17=HKCU\Software\Adobe\Elements Organizer\15.0\CurrentMediaFilePath

    RegKey18=HKCU\Software\Adobe\Photoshop Elements\15.0\common\settings\Elements MRU

    RegKey19=HKCU\Software\Adobe\Photoshop Elements\15.0\CurrentMediaFilePath

    RegKey20=HKCU\Software\Adobe\Photoshop Elements\15.0\VisitedDirs|STARTUPIMAGEDIRECTORY

     

    [Adobe Premiere Elements*]

    LangSecRef=3023

    Detect1=HKCU\Software\Adobe\Premiere Elements\11.0

    Detect2=HKCU\Software\Adobe\Premiere Elements\12.0

    Detect3=HKCU\Software\Adobe\Premiere Elements\13.0

    Detect4=HKCU\Software\Adobe\Premiere Elements\14.0

    Detect5=HKCU\Software\Adobe\Premiere Elements\15.0

    Default=False

    FileKey1=%AppData%\Adobe\Common\Thumbnail Cache|*.*|RECURSE

    FileKey2=%CommonAppData%|StreamingMediaTechnologyLog.txt

    FileKey3=%Documents%\Adobe\Premiere Elements\*|*.log

    FileKey4=%Documents%\NewBlueFX\Logs|*.txt

    RegKey1=HKCU\Software\Adobe\Premiere Elements\11.0\MRUDocuments

    RegKey2=HKCU\Software\Adobe\Premiere Elements\12.0\MRUDocuments

    RegKey3=HKCU\Software\Adobe\Premiere Elements\13.0\MRUDocuments

    RegKey4=HKCU\Software\Adobe\Premiere Elements\14.0\MRUDocuments

    RegKey5=HKCU\Software\Adobe\Premiere Elements\15.0\MRUDocuments

    https://github.com/MoscaDotTo/Winapp2/issues/87

    The Firefox/Mozilla Thread

    in Software

    Posted

    Firefox 54 may see 4 content processes on by default (up from 1):

     

    https://bugzilla.mozilla.org/show_bug.cgi?id=1367244

     

    the number of content processes can be modified by the user in about:config with dom.ipc.processcount or through a panel in the preferences (I've seen mockups but this module hasn't yet landed in Nightly)

     

    PEN 2:

    https://dolske.wordpress.com/2017/05/23/photon-engineering-newsletter-2/

     

     Preview Form Autofill in Nightly:

    https://blog.nightly.mozilla.org/2017/05/23/preview-form-autofill-in-firefox-nightly/

    The Firefox/Mozilla Thread

    in Software

    Posted

    Wait what is "chrome compatibility" why are they dumbing down customization of themes and,toolbars

     

    The WebExtensions API is meant to replace the current addon model, but they don't plan to turn it on by default until it has reached feature parity with Chrome's API in order to make it easier for chrome extension developers to port their extensions to firefox

     

    I believe they're moving the front end UI code from XUL to html/css (part of Quantum DOM?) and in doing so removing a lot of customization. I think userchrome.css will still be functional, I think more advanced themes that rely on XUL functions will not be.

×
×
  • Create New...

Important Information

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

  I accept