Jump to content

magic144

Experienced Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by magic144

  1. looks good so far in 5.78 - thanks to all who worked on remedying this
  2. Same import issues persist in v5.77.8448
  3. sounds good , thanks for the confirmation too
  4. Have replied with these findings to support team re :v5.76.8269 It's better, but still fails to handle hostname-only (no domain suffixes) cookie names like: localhost mydesktop2 mydesktop2:<port> etc. Hopefully these will get addressed in the next version.
  5. cookies previously accepted/working in v5.74 can no longer be imported/added in v5.75 Examples include cookies with port number suffixes, e.g. hostname_or_IP:port also cookies with URL path suffixes, e.g. bbc.co.uk/iplayer These were both working in import/export/add fns in v5.74. Please fix. Thanks.
  6. I'm not having that problem - I can get it to leave the cookies alone alright are you sure you've added all the cookies you want to keep? do a clean to the point where you think your good cookies have been deleted, then visit the site that needs the cookie to recreate it immediately, go into CCleaner and check the cookies again - if you see another URL like the cookie you need to keep, add it into your keep list and try again my only problem is when deleting index.dat files, the cookies get obliterated - I'm still waiting for a developer to chime in here and say if this is on the mend in future versions (or if it's even possible to work with IE7 RC1 and future versions)
  7. ...as long as you either don't use IE7b3 OR don't use CCleaner to delete index.dat files... I am (still) wondering if anyone is addressing the IE7b3 cookie + index.dat CCleaner issue...
  8. so is there any progress on upcoming versions of CCleaner regarding IE7 cookies?
  9. "Marked for deletion" means the files in question are in use by the operating system at the time and so cannot be deleted "immediately" instead, Windows has a special registry setting where files can be set to be deleted on the next boot - that's what happens to these index.dat files - they only get deleted when you next boot the PC (but rest assured, they do get deleted!) - Internet Explorer will subsequently recreate new versions of these files when you start using it again.
  10. hi just to address the current issue where cookies I nominate to keep still get deleted by CCleaner's actions when using IE7 Beta 3... I've found that if I disable CCleaner's deletion of index.dat files, the cookies of my choice will be deleted and those I want to save will remain intact after a reboot it seems there is some issue between CCleaner's deletion of C:\Documents and Settings\User\Cookies\index.dat and the retention of the cookies a user wants to save - if the index.dat file gets wiped, then even if the cookies have been left untouched and intact by CCleaner, they will disappear after a boot as a workaround, I've disabled CCleaner's "Delete index.dat files" option under "Internet Explorer" I can remove the other two index.dat files that CCleaner would have deleted using the excellent free MoveFile utility from Sysinternals in a simple batch file:- movefile "C:\Documents and Settings\User\Local Settings\Temporary Internet Files\Content.IE5\index.dat" "" movefile "C:\Documents and Settings\User\Local Settings\History\History.IE5\index.dat" "" (NB you will need the movefile.exe executable in the same directory as your batch file, or in your system path) - the utility can be found here:- http://www.sysinternals.com/Utilities/PendMoves.html just wondering if there is any progress/effort in remedying this incompatibility in CCleaner?? I guess an option would be to make these index.dat files individually selectable from CCleaner and NOT select the Cookies\index.dat if you've got IE7 installed... cheers in advance for your answers m
×
×
  • Create New...

Important Information

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