Jump to content
Piriform Community Forums

JDPower

Members
  • Content count

    3,341
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JDPower

  • Rank
    May contain traces of sarcasm
  • Birthday 20/05/1977

Profile Information

  • Gender
    Male
  • Location
    England
  1. Just go back to the previous version till an update arrives. That's what everyone else bothered by it has done.
  2. Sadly this is exactly what I expected when Avast took over Piriform. When I saw the new results graphics I knew it had started, the change towards CCleaner becoming another flashy fronted, dumbed down, identikit cleaner (ie "will undergo change and we will be bold") - make it look fancy to try to sell more, regardless of whether it's of use to actual users. Next step after that dumbing down in a couple of years, style and brand it as Avast cleaner. And/or integrate it into an Avast utility program or Avast AV and CCleaner becomes ancient history. CCleaner did not become a massive success DESPITE it's basic look, that was entirely PART of it's success. And hiding results of a clean does nothing to help so called "average users". "If you ask the average person what a 'cookie' or a 'thumbnail cache' is they simply won't know". I actually disagree but, regardless, the current change means they don't even know those things exist. If they see it in the results list they can google and find out, and perhaps learn the effects. Hiding that from them means they know nothing, can learn nothing and can have no idea of possible consequences of the things they don't know were cleaned. Oh and let's not also forget the removal of links to the builds/portable version on the download page, another recent anti-user move. It's a classic route that is taken whenever a large company takes over a smaller successful one - small company becomes successful/attractive, large company takes over, thinks they can do better despite the small company having done an amazing job to beat the odds and become successful in the first place, interfered with product becomes less successful, then large company dumps it cos for some reason it's no longer providing the value it was before they interfered. I'm just keeping my fingers crossed that I will be proved wrong, but the signs so far suggest otherwise
  3. The Firefox/Mozilla Thread

    A minor ESR update to fix an issue for Italian users: https://www.mozilla.org/en-US/firefox/52.7.1/releasenotes/
  4. +1 from me on this. An option for the old view would be much appreciated Can also second the comments about major slowness scanning IE - took about 10-15 seconds, instead of the usual 1-2 (Win7 64, CC64 bit, IE11)
  5. Don't know if Piriform take any action against these sites/developers, but posting it just in case: https://www.doyourdata.com/erase-data/ccleaner-data-erasure.html
  6. Winapp2.ini additions

    Brilliant. Thanks
  7. Winapp2.ini additions

    Now we're talking. Thanks for putting the work into that, looking forward to keeping an up to date winapp2.ini again
  8. The Firefox/Mozilla Thread

    Interesting that Firefox ESR is less vulnerable to the Spectre and Meltdown bugs than the main release Firefox, so doesn't require an immediate security fix: https://support.mozilla.org/en-US/questions/1198249 Well I thought it was interesting
  9. Winapp2.ini additions

    That may be true, but my point was you can't easily copy and paste the entries from Git update page. Unless I'm missing something, you copy and paste, then have to delete a load of plus signs, minus signs, removed lines, leading spaces. Then hope you've not accidentally screwed up the entry in the process lol
  10. Winapp2.ini additions

    It would be helpful if new winapp2 releases had the changes posted here, as they used to be, so individual new entries can be copy pasted to a users own file, which can't be (simply) done from the Github change list. Not a requirement, but it'd be easier
  11. where's the portable version?

    Was only a matter of time before Avast started making Piriform products less freeware user friendly. Next step, remove the slim and portable versions altogether. Then cripple, or ad fill, the free version
  12. Winapp2.ini additions

    Many do. Especially the year named versions as they're usually giveaway versions, not 'always free' versions (even though they technically are, they're not publicised as such to potential users). And newer is not always better. I used an old version of Burning Studio for years, cos the newer version added a load of bloat and functions I didn't need, was about ten times the size, and made a simple job complicated. It sometimes seems like there's an OCD file size obsession when it comes to winapp2, even at the cost of functionality.
  13. where's the portable version?

    Actually that's not true. The portable version has always been available immediately. IMO this is a dumb move and will just lead to portable users running old versions if every time they get notification of an update, no update is available to download. I get the reason why they hold back the slim version, but doing so with the portable version makes no sense. If you use the installed version, you can use the full installer if you don't wanna wait. You don't have that option if you use the portable version.
  14. where's the portable version?

    What a genius idea
×