Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About waika

  • Rank
  1. I regard CCleaner 5.00.5050 as a pleasant move away from skeuomorphism, there are still some minor eye sores that defeat the purpose of getting away from skeuomorphic design; ergo: · greater ease in avoiding mixed design metaphors that are confusing · avoiding color chaos lacking functional design cues · limitations of poor layout that offer no form that follows function · different pseudo depth effects with no continuity applied do same depth elements · conflicting pseudo light and gradient effects with ostensibly the same pseudo light source Only the last two are still conspicuously presen
  2. Well taking your questions in order; there are substantial advantages to be had with regard to security to using portable applications that are natively portable; ergo do NOT write to the Windows Registry (don't require a wrapper to redirect Registry i/o) and whatever local directories they store anything in is immaterial as long as the permissions are properly managed. That said I have all my Opera data hard-linked to a RAM disk, so the application is in effect 'sandboxed'...
  3. No Nergal, I'm not cousfued, I use the same kind of path statement. You seem to have missed the point that I am referencing portable installations of the 64-bit editions of Opera and Opera Next -- you appear from your path data appear to be using the 32-bit version... Edit: I finally got it to work, though I've been using the same path statement all along, added quotes and removed them from the path, used truncated short file names etc: CustomLocation1=OPERA|C:\Program Files\Opera x64\profile\cache When I added 'cache' to the string it was finally detected... And that's why th
  4. Yes, I understand that -- but when you use custom locations there's no audit display of the path being cleaned in Crap Cleaners output display...
  5. Thanks Nergal -- though it would be nice if Crap Cleaner could reconcile this and do it automatically as the native detection gives nice audit confirmation of what was cleaned vs. the 'custom locations' method. What's more, the x64 builds of Opera have for some months been at feature parity and have surpassed the 32-bit versions for stability and performance -- and are seeing a substantial up-tick in use.
  6. I don't see any 'custom location' entries in my ccleaner.ini or winapp2.ini... What's the exact syntax that should be used? And how is it that on a 32-bit install of Windows 7, CCleaner detects and cleans a portable installation of Opera, but can not detect the 64-bit installation Opera portable (or 64-bit portable installation of Opera Next ) on a 64-bit installation of Windows 7? Please advise?
  7. I'd like to vet support for the 64-bit portable installation of Opera as well; it appears there is support for the 32-bit version of a portable installation of Opera, but this doesn't work with the 64-bit version...
  • Create New...