Jump to content

Willy2

Experienced Members
  • Posts

    1,748
  • Joined

  • Last visited

Posts posted by Willy2

  1. How to create and post a screenshot:

    Download ""Deskscan"" and install it. This is a program that allows you to create screenshots. Place a shortcut on the taskbar (on the bottom left of Windows). Open CC and then click on the "Deskscan" icon on the taskbar to create a screenshot. And then post it in this thread. In the text editor on this forum there's a icon ""Insert image"" (that text shows up when you place the mouse on that icon).

     

    1. When a program doesn't function anymore after running CC then the first thing to do is:

    -- untick all the boxes in the registry section (""Registry"" in the main screen).

    -- re-install the program that has been affected.

    2. for all newbies: Untick as much boxes as possible. As time goes by, you can tick more boxes

     

     

  2. A matter of trial and error. Listen to and watch your computer. One of the signs you need a larger System (File) Cache is e.g. that opening a folder takes more time than usual and when you hear/see the harddrive working. Because then Windows needs to find the location of all the separate files again and extract all the icons from those files again as well.

  3. No, it doesn't move data to the swapfile. A lot of memory is reclaimed by Cleanmem (CM), so there's much less need for Windows to move data to the swapfile. When you allow CM to collapse the System File Cache (SFC) as well, then there's even less need for Windows to move data to the swapfile. And the SFC can be huge, up to 100 MB, and that's A LOT OF memory for my laptop (Windows XP) with a mere 512 MB of RAM.

     

    Yes. I agree, active programs reclaim bit by bit more memory but they never go back (at once) to the old (huge) memory usage. And that's why CM must be reapplied every 15 or 30 minutes.

     

    After I start my laptop (Windows XP) the SFC regularly occupies some 80 MB of memory. And that's why I let CM automatically run directly after a start up. There's a neat little program available that allows the user to manipulate the SFC and show the peak size of the SFC (even in XP) : Cacheset

    http://technet.micro...s/bb897561.aspx

  4. Here's the content for a 32 bits OS (name: Apply_log_settings_32bit_OS.bat)

     

    ECHO Copying Files...

    echo.

    del %systemroot%\system32\cleanmem_log_settings.txt

    copy cleanmem_log_settings.txt %systemroot%\system32\ /y

    @echo off

    exit

     

    And here's the content for a 64 bits OS: (name: Apply_log_settings_64bit_OS.bat)

     

    ECHO Copying Files...

    echo.

    del %systemroot%\syswow64\cleanmem_log_settings.txt

    copy cleanmem_log_settings.txt %systemroot%\syswow64\ /y

    @echo off

    exit

     

    If one or more files is missing then post a message on the forum over there.

    http://forums.pcwintech.com/index.php

  5. Some Cleanmem (CM) suggestions:

     

    1. Create a shortcut to CM and place it in the Windows ""Start up"" folder, then CM already has run before a user starts using his computer. I have placed an additional shortcut on my desktop, so, I can perform an extra ""clean up"" if I want to.

    2. The user also can tell CM in which folder the logfile should be stored. These two lines in the ""log_settings"" file control the logging.

     

    -- logging_enabled=true

    -- log_location=C:\Program files\Cleanmem\cleanmem_log.txt

     

    The first line (.....=true) tells CM that it should start to log its activities.

    The second line determines where the log is stored and under which name. So, you could use a path that points to a USB thumb drive. But is that path to the USB thumb drive always the same path ?

    The best way is to place the log in the root folder (C:\) and add that logfile to the ""Include"" section of CCleaner !!!

    3. Add the line ""file cache"" to the ""ignore"" list and the System File Cache won't be reduced/collapsed in size.

     

    About Real Player:

    Two websites I regularly visit require me to have a Real Player plug in, in order to be able to play audio clips. That's why it became my standard player for audioclips.

  6. This is a response to the discussion in posts #457 through #461 of the thread "Freeware !"

    http://forum.pirifor...showtopic=17921

    I thought it was better to discuss Cleanmem in a separate thread.

     

    So, cleanmem is a memory manager that uses Task scheduler to start every 30 minutes (the default setting). But the user can change that value by simply going to Task Scheduler and change that setting to whatever he/she wants it to be.

     

    After it has started and has performed it tasks the program closes and doesn't start again until it's (re-)started again by Task Scheduler. Just take a look at Task Scheduler and you'll see Cleanmem has added a task to the Task list.

     

    To be able to see what Cleanmem does the user can tell the program to record its actions in a log, a text file. That log reveals which processes (as in displayed in Task Manager) are curtailed in their memory usage by Cleanmem and by how much. And the default setting is that Cleanmem reduces/collapses the size of the System File Cache as well.

     

    I DO see a significant difference in performance ! Previously, it could take Real Player a significant amount of time to start playing a *.mp3 file but after installing Cleanmem that time has been reduced significantly by, say 50 to 90%.

     

    Cleanmem can be downloaded here:

    http://www.pcwintech.com/cleanmem

    Here the user can find a lot of additional program info.

     

    And the most important thing: it's freeware !

  7. No no, this memory manager works differently. This actually releases memory for use by other applications. Read all the details here: http://www.pcwintech.com/cleanmem

     

    It uses the Windows Task scheduler in combination with a special Windows API. Without moving info to the swapfile (!!) memory use of IE 8 was reduced from 38 MB to under 1 MB.

  8. 1. Don't you have a box called ""Adobe reader 9"" in the application pane ? Because Adobe reader 9 is already supported/recognized by CC from (at least) version 2.27 onwards.

    2. Perhaps you wrote your own winapp1.ini file but you forgot to add the entry for Adobe Reader 9 ?

    3. Perhaps the registry got corrupted (somewhat) and then CC didn't recognize you were using the Adobe Reader 9 ?

  9. I have already done a lot of the things suggested above to aleviate the burden on the CPU and the harddisk. One thing I never do anymore, is defragment an entire disk with DF. It simply puts too much strain on my harddisk and the benefits seem to be minimal. Though I manually defragment regularly files as much as possible.

     

    Recently I installed Cleammem and that program does seem to help to aleviate the burden on the CPU and the harddisk as well. It clears the memory of tasks that are not active and reduces the claims for memory, and therefore reduces the need for Windows to write information to the swapfile.

     

    But again, according to my experience, there's - most definitely - a difference in CPU usage between DF v1.10 and DF v1.20. Perhaps there's some combination of programs (including DF v1.20) that doesn't work out so well.

  10. In CC v2.33 the user can select to wipe the MFT. But CC won't wipe the MFT when the option ""Wipe Free Space"" (WFS) hasn't been selected. When both options are selected then CC will wipe the MFT first and execute WFS afterwards. And both processes can take a (very) long time.

     

    It may sound weird but the time it takes for these two processes can be reduced (significantly). Let a future version (v2.34 ?) of CC perform WFS first and then wipe the MFT afterwards.

  11. Welcome to the forum.

     

    I think it's most likely that you wipe too much items from the registry using the CC registry cleaner. Unticking all boxes or a lot of boxes less in that section could be the solution.

     

    Do not always wipe an item from the registry because CC says you can. Before wiping CC gives a description of the item to be removed. If you recognize that item to be a part of PSPVC then don't delete it.

  12. Billjf,

     

    I hope you understand that now you have added that line to the Exclude section you can tick that box Office XP again. Then CC still will wipe a number of Office XP settings but that particular setting will be spared. wink.gif

     

    There's - at least - someone who benefitted from your efforts and that's me. I use Office XP as well. wink.gif

  13. Here's another suggestion for CC v2.33:

    1. Save your current settings (ccleaner.ini).

    2. Click on Options, Advanced.

    3. Select first Restore default settings and then tick Save settings to INI file.

    Perhaps then the Include option works like it should.

     

    One important point is that CC doesn't store ALL the settings. It only records which settings have been changed. So, e.g. you could have ticked the box Recent documents but that setting doesn't show up in ccleaner.ini until you have changed it at least once.

     

    The delete folder itself option was introduced in v2.30. Then the complaints started to come in. So, the find and delete algorithm works well. But CC can go ""off the deep end"" when it's told to delete a folder itself when empty. Because it not always works properly on different computers makes me think that this is a ""memory"" issue.

     

    I have installed a memory manager (RAM Idle) and that could be the reason why I don't have any problem using the Include option. A memory manager forces Windows (XP) every now and then to write info from the memory to the swapfile and that's - IMO - beneficial for CC.

  14. I don't use this program but I have a pretty good idea of what could have happened. CC wipes in a number of cases simply too much.

    1. I don't see a box called Free Download Manager in your Application pane. It seems CC didn't recognize you installed that program and then it won't wipe those settings as well.

     

    2. Search for Free Download Manager on this webpage

    http://forum.pirifor...?showtopic=1110

    It details which entry/lines you must add to Winapp2.ini in order to wipe data from this program. It gives you some clues where this program stores it settings, e.g. in the registry and in what folder(s). One or more of these lines from this entry is responsible for wiping your settings. There're two different solutions:

    -- Write your own Winapp2.ini entry and leave out those lines which wipe the settings you want to keep.

    -- Add the lines that wipe the settings that you want to keep, to the Exclude section of CC.

  15. I had an email exchange last month with ""Mike Kennedy"" discussing the ""Include"" option issue. He ran a number of tests on two different computers. On one computer the ""Include"" option worked like it was supposed to. But on another computer the ""Include"" option always (incorrectly) wiped a folder itself as well when that folder was empty.

     

    It seems the temporary data CC compiles for the wiping of folders themselves (stored in the computer's memory ?) on certain computers gets corrupted. It seems other software interferes with that list.

  16. Unregistering those Adobe Flash files allowed me to delete those files and to perform a new ""clean"" installation of Flash 10.1. Even a re-installation of the latest Flash RC 10.1.53,64 version went well. This ""clean"" installation also solved the problem of CPU usage going up to 100% and staying there, in Windows Explorer. CPU usage now also sometimes can go up significantly but not to the extreme levels as seen before.

     

    I think there were some remnants of older versions of Flash and that caused - IMO - the problem to occur. So, it's VERY important to get rid of the old Flash version(s) before installing a new version.

  17. PB2007,

     

    1. It seems CC simply wipes too much Office 2010 settings. CC uses an embedded script that tells CC what to wipe. You can finetune how CC cleans the settings for Office 2010 by writing your own script which tells CC what to wipe and what not. This webpage provides clues how to do it.

    http://docs.piriform...leaner-to-clean

     

    Paste the info in the attachment into your own Winapp2.ini file and store it in the folder where Ccleaner.exe is installed. By a process of elimination you must find out which of these lines is responsible for wiping the settings you want to keep. A matter of trial and error.

     

    2. CC does adress the Jump Lists. Don't you have a box called ""Jump Task Lists"" in the ""Windows"" pane ? That's the box to be ticked.

×
×
  • Create New...

Important Information

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