Jump to content
CCleaner Community Forums

Willy2

Experienced Members
  • Content Count

    1,619
  • Joined

  • Last visited

Everything posted by Willy2

  1. Recently I noticed that in the folder(s) in which Defraggler is installed a file called Exception.txt (see attachment) appeared. When I took a look of what this file contained it seems it's an error reporting file. Is this file created by Defraggler (v1.10, v1.20, v1.21) or is this file created by the Windows error reporting feature ?
  2. I know you're using v2.34 because that info shows up in post #1. 1. Which of the (when I'm right) four Opera boxes in CC makes CC crash ? 2. I would suggest to un-install Opera and CC, clean and compact the registry, install ERUNT and then re-install Opera and CC.
  3. Some suggestions: 1. Post a picture of the top left hand part of the CC main screen. It provides more info of your system. 2. Run a registry cleaner (e.g. Eusing registry cleaner), install and run CC again. 3. Perhaps you can come up with more details of the error by clicking on one or the other link in that message window. 4. Which program(s) did you install recently ? Un-install those programs one by one and run CC again. It could reveal which program causes the CC error. Install ERUNT, it allows you to restore the registry to a previous state.
  4. And that Updatecheck bug isn't fixed in DF v1.21. I unticked that box in the install program but in spite of that DF presumes Updatecheck=1 when I ran DF for the first time.
  5. I must add something to post #2: When CC has completed overwriting the MFT in step 2 and starts to wipe the free space (again) I always cancel the operation. I would recommend Clean Disk Security 7.8 to REALLY overwrite fileinfo. Then even Recuva can't recover any files anymore. http://www.theabsolu...re/clndisk.html It follows the sequence as described in post #2.
  6. I recommend the sequence mentioned above because it the MFT is created dynamically by Windows. It expands and it contracts (at least, in Windows XP) depending on how much free space there's available. When the MFT has expanded then it can can take a VERY long time to overwrite info in the MFT, especially when you have a lot of free diskspace. When you run WFS first without wiping the MFT then the MFT is forced to contract to a minimum size. And then overwriting the MFT takes much less time. I think the Piriform folks should take this account and reprogram the Wipe Free Space + MFT options. i.e. first Wipe Free Space and secondly wipe the MFT instead of the other way around.
  7. When you select the option Wipe Free Space (WFS) then only the free disk space is overwritten and not the MFT (Master File Table) that contains info what the file names are and where those files are stored. If you want the file names to be deleted as well, then you should select the Wipe MFT space (WMS) as well. To speed up that cleaning process I would recommend to do the following: 1. Run CC with WFS selected but don't select WMS 2. Run CC again with both WFS and WMS selected. Especially when you have A LOT OF free disk space this particular sequence can save A LOT OF time.
  8. Some suggestions. 1. Does the amount of occupied disk space increase after you delete (=move to the recycle bin) that video ? Videos can massive in size (MBs). So, it shouldn't be too difficult to find out what happened to that file after deletion/moving it to the recycle bin. Use a program like e.g. Treesize, ExplorerXP (my favourites), Windirstats or JDiskReport and look for a folder called RECYCLER (Win XP). 2. If that video can be played after running CC and cleaning the recycle bin then it should be stored somewhere. Again, use the programs mentioned above to find out to which folder where it has been stored/moved to. 3. Perhaps WMP stores that file in a location that can be accessed by all accounts/users and therefore isn't removed at all. 4. If you download a video using Rapidshare then (in IE 7 & IE 8) the file is downloaded to a temporary internet folder and after that the file is copied (NOT moved !!) to a folder chosen by the user. WMP has an option that allows it to search your entire disk for media files (including the temporary internet files folders ?). So, WMP could have found the second copy of that file and created a shortcut to that file.
  9. Welcome to the forum. Very good idea. CC has only a limited repair/remove broken shortcuts capability. It has been requested (many times) before but Piriform folks don't seem to consider it to be important. Yes, I use Empty Temp folders as well and will use it as long as CC doesn't offer that functionality as well.
  10. My last suggestion: Perhaps there's a subkey under Startupfolder (just above Startupreg) that could cause the problem ? Perhaps CC comes up with more startup items than Msconfig. Below some links to additional info, what to look for. http://www.bleepingc...tutorial44.html http://www.tweaksfor...StartupLoc.html http://windowsxp.mvps.org/Startup.htm Let me know if this helps because I am curious whether or not CCleaner digs deeper than e.g. Msconfig.
  11. In that key, ...../Startupreg, there should something like this: ab (Default) REG_SZ (No value) This is quite normal and shouldn't be deleted. When an item is disabled from the startlist then there's a new subkey created under ......./Startupreg. I have such a subkey called ""D066UUtility"" (see attachment) and that key contains all the relevant info in order for that item to be ""enabled"" again. Do you have such a subkey under ...../Startupreg ? That info/subkey could be the cause of that blank line in CC.
  12. When a startup item (stored in the registry) is disabled (NOT removed !!) then it's moved from either HKCU\Software\Microsoft\Windows\CurrentVersion\Run or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run to HKLM\SOFTWARE\Microsoft\Shared Tools\MSConfig\Startupreg (When an item is enabled then it's moved the other way.) So, one should remove some info from that last registry key. Since CC doesn't provide any name, my best guess is that there's a empty key/value in that last registry key that needs to be removed. And perhaps the CC registry tool can remove that empty key as well. Otherwise use a registry cleaner that's cleans the registry more thoroughly.
  13. Welcome to the forum. 1. Upgrade to CCleaner v2.34. 2. Don't use the Gutmann (35 passes) secure deletion. Overwriting data one time is good enough and it takes less time. 3. Download and run Treesize. It shows you where all that free space could have gone.
  14. Willy2

    Freeware!

    My favourite free software: - Editpad lite: Texteditor. current version 6.64. Can handle multiple textfiles at a time. - Cleanmem v1.5.1 - Deskscan v1.38 (v2.0 sucks): to make screendumps. - Ccleaner - Defraggler v1.10 (!!!) - GlobFx SWF player: some games/presentations are contained in a *.swf file and this program is able to play those *.swf files without e.g. IE 8 - Treesize: shows how much diskspace is used by which folders. Much simpler than e.g. Windirstats. - ExplorerXP: an explorer that shows every folder and file in Windows. Even those that are marked hidden and/or system. - ERUNT: that program saved me, at least, a dozen times. - Clean Disk Security. current version 7.8 (works with XP, Vista, Windows 7, 32 and 64 bit). Only used to overwrite (deleted) disk-files/-space and is faster than Wipe Free Space in Ccleaner.
  15. http://forum.piriform.com/index.php?showtopic=25696
  16. 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).
  17. 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.
  18. 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.
  19. The online Piriform documentation provided this weblink to the website of Microsoft. http://support.microsoft.com/kb/221435
  20. 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 ?
  21. 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
  22. 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.
  23. 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
  24. 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.
  25. 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.
×
×
  • Create New...