Jump to content

KMazz

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Okay, I figured it out. All the cookies were "flash" cookies. I went into CCleaner on the "Cleaner" page and selected the "Applications" tab. I then went down to "Multimedia" and selected "Adobe Flash Player". It was not selected. After that, CCleaner cleaned the flash cookies. Hooray!! [i dun lern'ed sumthan todey!]
  2. I was using IE 6, but I'm using FireFox now. All the "undeletable" cookies, when selected, show an icon that is a bright red square with a lower case script 'f' in it (see attached screen snip). Does that mean, what the other poster mentioned, that they are flash cookies? How do you delete "flash" cookies?
  3. I already have the latest version 3.01.1327.
  4. I've notice for some time now (months) that the list of cookies under "Cookies to Delete" are still there after I run the cleaner. Previously, this list would be cleared after I ran the cleaner. I don't know if it is failing to delete the cookies or failing to clear the list (I suspect the list, but haven't checked it.)
  5. 1. The new version 2.17 of CCleaner does not allow you to scroll down in the "Options-Settings" window. 2. Also, when I start CCleaner from the start menu with IE running, CCleaner is started behind IE. 3. A sidenote: I tried to use the websites "contact" page and got a RUNTIME ERROR on the website. Here it is: Server Error in '/' Application. -------------------------------------------------------------------------------- Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
×
×
  • Create New...

Important Information

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