Jump to content


Experienced Members
  • Posts

  • Joined

  • Last visited

Posts posted by Willy2

  1. When the user wants to start Defraggler (v1.21) for a second time then a message appears/shows up "Defraggler is already running" and the Defraggler simply refuses to start up for a second time. But when the user wants to start CC (v.2.35.1223) or for that matter, Recuva or Speccy for a second time then no (error) message appears/shows up and then CC (but Recuve, Speccy as well) starts up again.



  2. A.: Is the current version of CC really to blame ?

    Go back to a previous version of CC and see whether CC gets stuck again. (Currently, I have installed the four last versions of CC !)


    B.: Perhaps too much registry entries were deleted (with CC) ?

    1. Save your favourites, settings etc.

    2. Uninstall the program (e.g. Google Earth, Firefox, and perhaps even CC), clean (e.g. Eusing registry cleaner) and compact the registry (e.g. NTREGOPT), install ERUNT, and re-install all the programs.

    3. Activate System Restore Points (Windows XP). In Windows 7 and Vista this has a different but similar name.


    One has to keep in mind that even when the user doesn't use the CC Registry tool, CC removes a number of program (e.g. MS Office) related registry keys/entries/info, even though this isn't being reported in the CC result screen.


    ERUNT is a program that makes a copy of the registry once a day, upon start up and therefore allows the user to reinstate a previous (undamaged ?) version of the registry. http://www.larsheder...nline.de/erunt/

  3. @Andavari:


    I use the same trick but I took/take it one step further. In order to avoid typing those long sequence of characters, I do the following:

    1. I select the registry key that I want to be excluded (Regedit) and use the export function to create a *.reg file (just a text file)

    2. I then copy the registry key text to ccleaner.ini. (Yes, as you have been saying, one has to modify the text in order to make CC recognize and execute those lines in the ccleaner.ini file).

  4. I think the Piriform developers should take the opportunity when they issue CCleaner v3.xx and Defraggler v2.xx to ""clean out"" the Piriform software as well. I opened and analyzed the last versions (v2.34 and v2.35) of CC with Resource hacker


    and it seems that inside CCleaner (and Defraggler) there's (software) code that's no longer used. And that bloats the program.


    e.g. in the dialog section (Ccleaner), there're two duplicate dialog screens. (dialog, 213, 2057) and (dialog, 268, 2057)

  5. And there's another GUI issue in the CC registry section (v2.35). Keywords: gridlines. When CC has detected a lot of registry errors/issues and one screen can't show all errors then on the right hand side a scroll bar appears. So far, so good. But when the user clicks on the scroll bar (not on the scroll bar button !!) then CC completely messes up the gridlines.


    Does CC use the same ""gridline algorithm"" as (a previous version (??)) of Recuva does ? Because in the program exactly the same issue surfaces (surfaced ?).



    1. get rid of the grid lines.

    2. Improve the gridline algorithm. There's - IMO - no need to ""re-invent the wheel"" because in Defraggler (v1.21) that (gridline) algorithm works perfectly. And the Piriform folks could use that algorithm in Recuva as well.

  6. The GUI can be improved, I don't want to call this a bug. And I am talking about the CC Registry tool. Suppose CC has found 20 errors in the registry and the user has highlighted and selected the first 10 of those errors. The bug in the GUI becomes apparent when the user deletes one entry/line. The amount of selected entries/lines declines to nine. But CC continues to highlight 10 lines in the registry section.

  7. ExplorerXP doesn't work as smoothly as Windows Explorer does. That's what I should have said. Sometimes one can use the usual Windows ""tricks"" (of e.g. Copy and Paste, right or left mouse click) directly and sometimes one is forced to use the program's own commands, which takes (a little bit more effort), to handle the management of files in Windows.


    I haven't figured out what causes this eratic behaviour of ExplorerXP but when one gets to know the program it provides the user an additional tool/functionality to look beyond the limits as set by Windows Explorer.

  8. @Henriette,


    By "manually deleting SRPs" I mean that I either use CC (Section "system restore") or ExplorerXP (shift-delete) to delete those things. But, as mentioned above, ExplorerXP does a more thorough job and that's why I prefer to use ExplorerXP.


    SRPs in Windows XP are (relatively) small (30 to 170 MB) but, according to my (limited) knowledge, SRPs in Vista and Windows 7 can be (very) large (700 MB or larger).




    If you go back to a previous CC version (e.g. v2.34 or v2.35.1219), do those SRPs show up again in CC ?

  9. I would love to help and become the new dutch translator for the Piriform software. But currently there're two things that keep me from doing so.

    1. My technical knowledge of computers is (comparitively/very) limited. (Especially Speccy)

    2. I am not sure for how long I am able to have an internet connection in the coming months/weeks/years.

  10. @MrRon,



    Starting with DF v1.19, DF mixes up the ""Free space defragmentation"" and ""Free space (allow fragmentation)"". Read my replies in the thread mentioned below !!!!



    The ""Freespace defragmentation"" options also cause the fragmentation to increase.


    No, DennisD, the files and folders in ""System Volume Information"" always can be defragmented and never are the source of any problems. Even in v1.21.

  11. Some time ago I compressed all my Outlook Express (OE) files. At that time I had only some 120 MB of free diskspace. Total size of those OE files was about 100 MB (Yes, I receive a lot of emails). When OE compresses its data files it places a copy of every file in the Recycle Bin. So, after compressing I expected free space would be reduced to some 20 MB but to my surprise the total amount of free disk space was about 200 MB. After some research I discovered that I had two or three restore points less but I also knew that I hadn't manually deleted those SRPs. So, I figured out that Windows would be responsible for deleting those SRPs.



    I would suggest the following:

    1. Create manually one or two new SRPs.

    2. If CC does show those two newly created SRPs then simply delete all those old SRPs. (with ExplorerXP, shift-delete)


    I also know that when the user uses CC to delete a SRP then CC won't always wipe the entire SRP. some files are simply left behind. And that could be the case on your computer.

  12. I had a similar discussion with ""Mike Kennedy"" in june.



    When I read the posts in this thread then it seems that bug hasn't been fixed in the latest version(s). I don't experience any problems with this ""Include"" option in CC v2.35. So, the search algorithm seems to be OK. Therefore I still think that it's an memory issue. Perhaps this the result of a thing called ""memory leakage"" ?



  13. First of all, closing a program/process always results in freeing up memory that was in use by that program.


    Programs, while running (e.g in the background), claim, bit by bit, more and more memory (two notorious examples are IE 8 and Windows Explorer) and often ""forget"" to release that claimed memory when not or partially in use. So, when a new additional program is started and it claims memory as well, then Windows could decide to copy data from the memory to the swapfile, in order to free up memory for that new program. And that slows down Windows.


    Cleanmem forces all or a user defined list of programs/processes, as displayed by Taskmanager, to (significantly) reduce the claimed memory, even when that program is still running (e.g. in the background). That prevents Windows to perform the timeconsuming copying of memory info to the swapfile.

  14. I think I know what went wrong.

    1. The first line didn't work because:

    -- of that space in your username.

    -- with \xnview.db you told CC that it must look for a folder called xnview.db. When you would use xxxx|yyyy it would tell CC to look for a folder called xxxx with a file yyyy in it.

    2. The last three don't work because you must either enclose the entire string in quotation marks or nothing in quotation marks. Not only some part of the string. My suggestion: get rid of all the quotation marks.

  15. When CC continues to grey out the OK button in the Exclude section then you either made an typing error or that registry key doesn't exist. (CC checks very carefully whether something exists in the regsitry or not) If you know how to use a registry editor (e.g. Regedit) then you can check whether one or more keys exist in the registry or not.


    The line that began with Filekey...... must be entered not in the registry key part of the Exclude menu but in the either folder or file part of the Exclude menu.


    Perhaps using method #2 (like MRG7 did) is less complicated.

  • Create New...

Important Information

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