Jump to content

JDPower

Experienced Members
  • Posts

    3,379
  • Joined

  • Last visited

Posts posted by JDPower

  1. Whoopee <_<

     

    Oh the contradictions. They'll kill off a bunch of addons, and make them impossible to replicate, whilst claiming they'll "add capabilities to Firefox that don’t yet exist in other browsers". Riiiight, so you're gonna remove current capabilities that aren't present in other browsers, so you can ADD capabilities that aren't present in other browsers :rolleyes: Pretty much sums up the clueless, focusless, direction Mozilla have been heading the last couple of years.

  2. V01.log and WebCacheV01.dat are always locked by a svchost.exe process.

    the others can be deleted but get re-created, definitely at each boot, maybe sooner.

    all part of the brave new IE/Edge/Win10 new world I think.

    are you Windows 10?

     

    (apologies if none of that was news, may help others though)

    They're not even there, the folder is empty, yet CCleaner is claiming to clean them (analyze shows nothing, cleaning repeatedly shows them in the results of what's just been cleaned). And just to pre-empt, yes, I have hidden and system files visible.

     

    And no, not Win10, am on Win7 and it's IE11

  3. Dunno if this is a bug with the winapp2 entry, or showing up a bug with CC, or just a quirk of my computer, but part of the "Internet Explorer More" entry keeps showing webcache folder cleaned, then when you run CC again, it shows it cleaning the exact same files again (same file sizes), even though it's supposedly just deleted them, and even though the folder it's cleaning is actually empty. So EVERY time I run CC I get the below result for the entry, even though there's nothing there :huh: 

    Uj9Mjri.jpg

  4. Apologies if barking up the wrong tree, but isn't CCleaner using the Windows default border CORRECT behaviour? The screenshot showing the CC specific border is from V5.00 - CCleaner 5 had a custom border for 2 or 3 versions, but there were complaints that it wasn't respecting the Windows theme so was changed to do so. So there is no bug, just a change in the program.

  5.  

    Only if he gets 1000 plus tabs will he be in SuperFast's league. :lol:

    I don't NORMALLY have that many open (I did hit just over 300 a little while back, that's probably my record. And also the point I slapped myself and dealt with them lol). I get easily distracted and leave stuff open to read another time, then never do! In my defence I do use BarTab to unload unused tabs and rarely have more than 5 or 6 actually loaded tabs :ph34r:

  6.  

    Sry, i lost you. xd

     

    Its

     

    [NVIDIA Logs*]

     

    ^^

    I worked that out by copying the first line, then searching the full file for it. Just thought there might be an easier way. Presume it's a GitHub bug/quirk

  7.  

    Take my post above this one for example. If you click on the link and look to the left, you should see the line numbers, like 3780, 3781, 3782, etc. Along there, you should see a weird looking thing with arrows pointing up and down in it. Click that and it will expand the text.

    I'd already done that in the screenshot I posted (hence no arrow showing), was the first thing I tried. Clicking it in the patch posts doesn't work. It does work for the below post, but not for the patch posts :huh: (tried in FF, IE and chrome in case a browser specific issue)

     

  8.  

    there https://github.com/MoscaDotTo/Winapp2/compare/master...TZocker:patch-8

    and this entries

    Filekey=%LocalAppData%\NVIDIA Corporation\NvNode|*.log;*.bak
    Filekey=%LocalAppData%\NVIDIA Corporation\NvTelemetry|*.log;*.bak
    Filekey=%LocalAppData%\NVIDIA Corporation\NvVAD|*.log;*.bak
    Filekey=%LocalAppData%\NVIDIA Corporation\NVIDIA Share\CefCache|*.log;*.bak
    

    use strg F after = ;-)

    Nope, you lost me.

    When I click the change links like that, this is what I see. How do I tell what program entry it is that has been edited so I can copy to the right place in my winapp2 file?: q9Hb0fy.jpg

  9. Another minor version update, FF 49.0.2:

     

    New:

        Asynchronous rendering of the Flash plugins is now enabled by default. This should improve performance and reduce crashes for sites that use the Flash plugin. (Bug 1307108)

    Fixed:

        Change D3D9 default fallback preference to prevent graphical artifacts (Bug 1306465)

        Network issue prevents some users from seeing the Firefox UI on startup (Bug 1305436)

        Web compatibility issue with file uploads (Bug 1306472)

        Various security fixes

        Web compatibility issue with Array.prototype.values (Bug 1299593)

    Changed:

        Diagnostic information on timing for tab switching (Bug 1304113)

        Fix a Canvas filters graphics issue affecting HTML5 apps (Bug 1304539)

     

  10. I read some of these older comments and I just got to laugh. If you want a secure Firefox while still maintaining good performance on it, consider using something like HTTPS everywhere so you only access sites through secure connections (where available), consider using a more generalized blocking tool, like uBlock Origin, to block malware sites, ads, tracking, etc, and lastly, consider getting rid of flash player and using VLC Player instead. I have been using VLC Player as my only codec for playing video content on the web and so far every site I went on runs on VLC Player just fine. Believe me, you wouldn't even know how much more Firefox is more secure without Flash Player. Don't have to worry about flash based attacks and all those security holes in flash player (while there are a few in VLC, sure, what program doesn't have any, but they are far less severe and there are a lot less in general).

     

    I have been using this setup for years and I have never has any performance degrade and never had any malware problems through Firefox. Not too mention Firefox is pretty secure by default, as it has a large community/team and it's open-source.

    So glad you're here to enlighten us about all this stuff we "wouldn't even know" :rolleyes:

  11.  

    A user posted this over at GitHub: https://github.com/MoscaDotTo/Winapp2/issues/42

     

    What does everyone think? Some of them look a little too risky maybe?

    The ones that delete old Windows installations, the $patchcache and the winsxs backup folder are definite no no's IMO (I do occasionally wipe the latter, but seen others have issues caused by it). In all my years of computing I've never seen a convincing/safe reason to delete the $patchcache, other than a last resort if running out of disk space. And the old installations files, seems common sense to not delete them, at least not as a matter of course in a cleaning program.

  12. unless you plan on manually merging each entry.

    Thought that was what everyone did? :huh:

     

    Removing/splitting entries is a terrible idea IMO. Does trim.bat really take THAT long?

     

    EDIT: Just had a thought, wouldn't it actually SLOW things down for users, as they'd have to run trim.bat on TWO files instead of one. Or have to go through the so called 'old' file and copy and paste them all individually into their winapp2, which would then be overwritten the next time they downloaded winapp2, leaving them doing the whole process again?

  13. The problem with doing this is:

     

    -  An awful lot of people do not upgrade versions of software until they absolutely have to because something does not work with a new version of Windows or whatever.  Third party licensed software that charges for upgrades each time they issue a major version release is one of the main reasons people do not upgrade....can't afford to keep shelling out money.  Thus, editing Winapp2.ini based on version number, age, can reduce the effectiveness on those peoples systems.  And they certainly do not enjoy being constant auditors of what has been removed from Winapp2.ini and then adding back in code.   

     

    -  And to be truthful, it bothers me when we start "editing/merging/ code" Winapp2.ini because it means tested code has to be retested to ensure that it is working/functioning properly on user and my own systems.  

     

    -  Trim.bat is an excellent tool to speed up Winapp2.ini's affect on CCleaner.  It is not frequently executed by the majority of Winapp2.ini users so I don't believe its speed is a significant issue.  

     

    JMO  :wub:

    I was gonna reply to ROCKNROLL's post, but you said it all for me, and probably more eloquently/politely lol, so will just say..... seconded ^_^

×
×
  • Create New...

Important Information

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