Jump to content
CCleaner Community Forums

Willy2

Experienced Members
  • Content Count

    1,614
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Willy2

Profile Information

  • Gender
    Not Telling
  • Location
    The moderators know

Recent Profile Visitors

3,264 profile views
  1. - I have seen that my bug reports (plural) were used to improve the Piriform programs in the past.
  2. - Run Antibody's wizTree. And sort the results on filesize. Any files that are VERY large ? - What's the size of the folder "System Volume Information" (There the System Restore Points are stored) ?
  3. - I think you need to reset your password. Many websites allow you to do so. - I Always send an email to myself with the (new) Username & (new) Password after I have changed my log-in info and store that email in a special place.
  4. - CCleaner is a very powerful tool. When you use the program for the first time then I would recommend to untick ALL boxes and then step by step tick more and more boxes and see how your system reponds after each step. - The default setting is that cleaning / removing of all cookies is enabled. - Just untick all the "Cookie" boxes for all browsers that show up in the list (Chrome, Edge, ............... ). Log-in for those programs / applications (again). After running CCleaner once more the cookies should be still there. - CCleaner also allows you to select which cookies must be kept and which can be removed. (Options > Cookies).
  5. - One minor detail: Email adresses in Norway end with ".no", not ".nb".
  6. - When the content of that "Windows.old" is a relic of Windows 7 on your otherwise well functioning Windows 10 system then I wouldn't hesitate. Just delete the entire content of "C:\Windows.old" folder.
  7. - Have been using DF today again and when I opened RAMMAP I saw 43 DF "Zombie" processes ("Defraggler.exe") while Task Manager showed only one process called "Defraggler64.exe". - It seems that somehow the process "Defraggler64.exe" opens "Defraggler.exe" and uses some of the subroutines and then "forgets" to tell the Operating System that the process has done its job and the process can be "closed"/"removed". - This also can be a bug in the program code. E.g. "Defraggler64.exe" has all the subroutines it needs to perform its tasks but still calls upon "Defraggler.exe" every now and then. This could be a remnant of a previous Defraggler version before there was no 64 bit version of the program. Lots of possibilities on why so many Zombie processes show up. - When I look at the size of the 43 DF "zombies" then I see that these Zombies actually don't use that much memory. RAMMAP reports that each of these 43 processes only use 20 Kb. Seems each of these processes are opened/created but then these processes each are hardly used/don't see little or no "activity". And - in general - one can say that the more a process is being used the larger the memory footprint. There the low memory usage could give a good indication of what's going on. - Another thing I noticed is that as soon as I close DF the zombie processes (seem to) disappear away as well. Odd, very odd.
  8. - When I remember well then it also only occurs when the user has told DF that the settings should be stored in an *.ini file on disk and not in the registry. - Again, needs to be fixed in the next version.
  9. - This is a known bug in Defraggler. Needs to be fixed in the next version !!!! - The only way is to manually open the *.ini file and delete / modify the list yourself.
  10. - After using DF for a while the amount of "Zombie processes" (see previous post) - as exposed by RAMMAP - reached the level of 38 instances.
  11. - Something is wrong with the memory management of DF and I think that the memory management can be improved. - There is a difference between the info provided by Sysinternals' RAMMAP and Task Manager (Windows 7). When I look at the "Process" tab in RAMMAP then I count 13 DF processes (red Arrow & red rectangle). But when I open (the dutch version of) Task Manager (blue Arrow & blue rectangle) then I only see one process ("Defraggler64.exe"). The amount of memory used by DF (Task Manager) doesn't match up with the amount of used memory by DF as displayed in RAMMAP. Odd, very odd. These 12 extra DF processes don't use much memory but there are running anyway. Again, odd, very odd. - Recently I watched a video explaining how the program called "RAMMAP" worked. They mentioned the words "zombie processes". It seems the extra DF processes (as shown in "RAMMAP") are precisely that, "Zombies". The video also gives a (possible ???) explanantion of why these zombies exist. The video can be found at https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-6-RAMMap The word "zombie" is mentioned a few times in the video from about 21:00 onwards. - Sysinternals' RAMMAP can be found here: https://docs.microsoft.com/en-us/sysinternals/downloads/rammap - See the picture attached.
  12. - Found another example where DF thinks that a file had zero fragments. See the red Arrow in the picture.
  13. - I have heard stories that the NSA is also VERY "interested" in such "weak spots" in several Operating Systems.
  14. @Cornish Dowser See my reply here in the thread below:
  15. @Cornish Dowser: - the program will continue to work when you disable the Mini Monitor untick "Show Monitor"). It's simply an extra visual tool on how CLEANMEM behaves. To see whether or not the mini monitor is running you just simply check Task Manager. - Cleanmem itself is run with the help Task Scheduler and after it has run the program closes itself. - Yes, "stealing the focus" is indeed a problem. And there are some other small tiny "inconveniences" but the program itself works well. But the author hasn't issued new updates in the last few years. The PcWinTech forum has indeed closed down (too much spam and very little responses).
×
×
  • Create New...