Willy2

About Office 2003: Post #4 in this thread (see below) gives a clue which registry entries are created by Office 2003. Then you know what to delete. http://forum.pirifor...showtopic=25696 About Opera: 1. Doesn't Opera have a de-installation program ? 2. Look in the %appdata% folder(s). (with e.g. ExplorerXP).

I had something similar. The advice Microsoft gives is the following: Rename the folder to which Windows downloads the update files and run Windows update again. Give that folder a slightly different name. In Windows XP that folder is called ""C:\windows\SoftwareDistribution". That folder will have in Vista a similar name. If it works (it worked for me) then you can delete the old ""softwareDistribution"" folder afterwards.

The reason this bug doesn't get more attention is that DF uses a counter to count the amount of days that has passed after a check for a new version of DF. Only after 10 days DF will check again for a new version. But for someone like "mr don" who seem to install DF on computers on a regular basis it has become obvious that DF has this bug/programming error.

The online Piriform documentation provided this weblink to the website of Microsoft. http://support.microsoft.com/kb/221435

I don't know what language code Microsoft has assigned to Bahasa Indonesia. Send a PM to ""Twisted Metal"" or one of the other bugfixers/moderators. Perhaps they know the answer. Aren't there any internet forums in Indonesia/Malaysia that can help you ?

Welcome to the forum. If you want those registry keys to be deleted by CC then you can tell CC to wipe these registry keys as well. Here're two weblinks that provide a lot of info how to do that. http://docs.piriform...leaner-to-clean http://docs.piriform...leaner-to-clean

When the user installs DF the user is asked whether or not DF must check (every 10 (???) days) for a new DF version being available. But the installer program simply doesn't store that setting in the registry. So, when the user runs the program for the first time it doesn't come across a line called Updatecheck=... and then DF presumes Updatecheck=1 and acts accordingly. i.e. check for a new version. This is a clearly a bug because the DF install program recognizes which language is being used and does store that in the registry.

The more I think about it the more I think this is a BUG in DF that needs to be corrected in a future version. http://forum.piriform.com/index.php?showtopic=28987

It's quite simple. I think, the Piriform folks want to make sure the user has the latest version. So, that check is done the first time DF runs after installation, it's done on purpose. But you've stumbled upon a bug in DF. When the user has indicated that he/she doesn't want to check for newer versions in the installer program then DF fails to remember that setting. Click on Settings, Options, General and you'll see that the box called Automatically check for updates to Defraggler is ticked. With a few extra lines of programcode the problem can be solved. But I doubt if the Piriform folks are willing to incorporate those few extra lines.

All the files included in the ""portable"" version must be copied/installed/placed in the system folder. Either in %systemroot%\system32 (32 bit OS) or in %systemroot%\syswow64 (64 bit OS) (???). Are all the files in these folders loaded into the memory upon startup ? That would explain why e.g %systemroot% folder is mentioned in the file Layout.ini in the C:\windows\prefetch folder. And Windows uses Layout.ini to optimize the startup process by grouping those files in that folder on the harddisk.

No need to post an item three times !

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

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.

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

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

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.

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 !

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.

This is currently my favourite memory manager: ""Cleanmem"". Just yesterday version v1.5.1 was released and it's freeware.

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 ?

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.

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.

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.

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. There's - at least - someone who benefitted from your efforts and that's me. I use Office XP as well.

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.