Jump to content

dallas7

Experienced Members
  • Posts

    21
  • Joined

  • Last visited

Reputation

0 Neutral

Profile Information

  • Gender
    Male
  1. Well, I picked up a Moto G3 yesterday and about 25 minutes after first power-up, it notified of the 6.0 update. I allowed it. Later I got around to installing CCleaner and right there in the after-analyze screen there was a message beginning "Due to restrictions in Android 6.0..." basically saying cleaning must be done manually and no more cache cleaning. Uninstalled CCleaner. Piriform's silence (web site, store, here) on this is deafening...
  2. Detect and report for Blu-ray readers/burners Cinavia support and version. Thank you.
  3. Confirmed: 3.06.1433 portable works without error. While I previously reported 3.04.1389 worked OK, factually the AVG cleaning still failed (though fixed in 3.05.1408/1409). However, it too is OK in 3.06.1433. Good work and... THANK YOU!!
  4. Confirmed that issue persists in 3.05.1409 portable same as in my first post above and as described by Stevie2507, w8sdz and... all those others. v3.04.1389 portable still works OK. Thank you.
  5. I didn't know there was a priority support version. Thanks for that link!
  6. It's not an inconvenience. CCleaner rocks. You're welcome!
  7. @Super Fast All requested info is in my original post and screen shot except 6GB free on a 9GB system (C:) partition.
  8. Thanks for your effort. I can't speak for moggy but I'm not interested in a winapp2 workaround. The point is: AVG cleaning worked just fine. Now it doesn't. Period. That's not a deal breaker when considering it's freeware. I still choose to use CCleaner since it shines. If Piriform ever goes to a paid model, my PayPal account is at the ready. Besides, AVG has its own resident cleanup tho not as thorough as was CCleaner's (Advanced Tools > Manage > Clean Up). But really, it would be nice if that bug got fixed. Or if AVG cleanup can no longer be viable effected, then remove it from the selections. Cheers!
  9. Issue is persisting with 3.05.1408. Still no AVG 10.0 cleanup. EDIT: Oops, I just noticed moggy reported this but he posted up "The AVG bug hasn't been fixed in 3.04.1408..." so that threw me a bit. And I can't readily find a way to delete this posting. Cheers.
  10. FYI: Thank you for distributing CCleaner as Freeware. I have been using the portable version since so way back when I forget when that was. Today with 3.05.1408 I experienced the first-ever error when doing a Cleaner; as Analyze or Run Cleaner. See the attached screenshot. If I uncheck IE cookies, then I get this: VA=%locallowappdata%\Google\GoogleEarth|dbcache.dat If I ucheck that, I get: VA=%locallowappdata%\Apple Computer\quicktime\downloads|*.*|RECURSE If I uncheck that, I get... well, it just keeps on going, erroring at another VA and another. I can click Close and CCleaner will continue to 100% but if Cleaner is run again, the error persists. I reverted to 3.04.1389. Cheers.
  11. Thanks again, Alan. I can assure you, and repeatedly demonstrate at will, that Hist* and Hist*.*, quotation enclosed or not, do not effect a wipe in CCleaner's Include as currently implemented. You might note the Google file History Index YYYY-MM lacks an extension and therein lies the rub. I can rename the file as History Index YYYY-MM.foo and the Hist*.* mask is effective. I have familiarized myself with CCleaner's ini files. Given the fleeting test bed that Google's browser is at this point in time, and if I were not using a portable port (pun!) I might take the time to build a Winapp2.ini. But even if I were to decide Chrome is a suitable replacement for Firefox (BLASPHEMY! ), I would used the "installed" version for which CCleaner support already exists. Right now, Chrome is merely something to play with. And yes, variables are cool. In any event, I think the subject matter has been settled and request this thread be closed. Cheers!
  12. Hist* Hist*.* "Hist*" "Hist*.*" strings no workie. This would confirm the docs which list *.* and *.<ext> as the only usable wild card masks. Over and out.
  13. In my experience I've found as long as one keeps at least the latest "bookmarks-YYYY-MM-DD.json" file in the bookmarkbackups folder, bookmarks will be safe regardless of the status or presence of sqlite files. In the event of a missing or corrupt sqlite file, the json file will be parsed. In fact, I backup that json to another directory on a weekly basis should I ever need to rebuild the browser. And it's quickie way to migrate bookmarks to another computer vs export/import. I've added these FF 3.5.1 files in my Include: content-prefs.sqlite places.sqlite places.sqlite-journal webappsstore.sqlite Think I'm missing anything? I'm seriously into overkill. Thanks!
  14. Thanks Alan. That will work and I did actually use that strategy with a portable version of Opera some time ago. The Chrome directory however is a critical component of the user profile and I tend to shy away from wiping the whole thing as routine. And as new releases roll out, I can simply browse it - anything new will jump out as did this incremented history file. It would be far safer to maintain that as needed even to the point of deleting a file and building a new rule every month. A *.* wipe might find me at a point where Chrome is unexplainably "broken" after a CCleaner run. Not critical as I do keep a backup of profil and, after all, it's just a browser. But keeping the eeeeeevil personal data harvesters at bay, for me, is half the fun of playing with CCleaner. Its default rules are adequately safe out of necessity, but you can tell I feel the need for lots of additional includes; there are plenty more after Include40... However, your reply did give me an idea. I've been building the rules with CCleaner itself and, as you may know, the creator dialogue doesn't permit the manual entry of text as "Hist*" or "Hist*.*". I didn't think of editing the ccleaner.ini file itself until now. My duh! I'm going to give that a try and see if that will work. And report back. In the meantime, I'm still open to suggestions or further insight into the secret innermost workings of ccleaner.ini. Thanks!
×
×
  • Create New...

Important Information

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