Jump to content


  • Posts

  • Joined

  • Last visited


0 Neutral

Profile Information

  • Gender
  • Location
    Northern California, USA, Earth, Milky Way
  1. Apparently, CCleaner 4.x is no longer compatible with Windows 2000. (I don't know that it WON'T work, just that the installer prevents it from installing.) Version 3.28.1913 is the latest pre-4.x version listed in the release notes, so I'd like to download it and install it on my Windows 2000 virtual machine. But I cannot find a link to any archived older versions anywhere on the Piriform website. If Piriform has chosen to end support for earlier versions of Windows, that's their right. It's a free program, after all. But it would be a decent gesture to keep available the latest versions that WILL work on older OSes. I may not be able to use the latest and greatest version, but I should at least be able to obtain the latest version that will work for me.
  2. 1) I know better than to try to recover files to the same drive. I have been scrupulously careful throughout the entire recovery attempt (before and after trying Recuva) not to write anything whatsoever to the "bad" drive. I wouldn't even let the OS attempt to boot from it. 2) I don't care about sorting through them - I welcome that challenge, IF I can get them all back in the first place. 3) It's irrelevant how many files are there. The recovery utility (in this case, Recuva) should not hang/crash during recovery. At the very least, if there's a problem, there should be an error message of some sort. If it gets stuck on one file, it should flag that file and move on to the next one. Additional info: during a deep scan attempt, it sometimes fails with the message "Data error - cyclic redundancy check" rather than hanging. When this happens, the scan stops. I think it should complete scanning the drive and flag the file that generated the error.
  3. Hi, all - I have a few ideas about how Recuva could be made more helpful: 1) First, I agree with BobDrivesTruck - in the file listing, make the whole row selectable, not just the first column. It is frustrating for me to click in, say, the third column and have nothing happen. Maybe this could be an option or preference? 2) I'd like some way to select the files to recover using some kind of search or wildcard (regex?). For example, I might want to attempt to recover all files with a file extension of ".jpg" whose State="Excellent". As it stands now, I must manually select all of these files, and I do not even have a way to sort by file extension/type. Which brings me to: 3) Provide some way to sort files by file type/extension. Maybe add a new column for this, for files where the file extension can be recognized? 4) (Dare I dream?) Add into Recuva (or into a separate utility) the ability to recover not just files, but an entire partition/logical drive. This way, the next time my sister's boyfriend's idiot brother accidentally reformats her hard drive while surfing for pr0n on the Internet, I can use Recuva to recuva her drive for her.
  4. Hi, all - I'm having a problem where Recuva 1.15.327 hangs early in the recovery process. The scan (quick, not deep) goes smoothly, and the analysis results in about 22000 files found, about 70% of which have a prognosis of "Excellent". I select all of the "Excellent" files and hit Recover... and it starts to recover the files, but anywhere from 1% to 26% of the way through the recovery, it hangs. I've waited two hours and seen no change in the recovery progress. I've manually gone through the list of files to recover and made sure there were no huge ones there (no .VOBs, no pagefile.sys, etc.), but it doesn't seem to make any difference. I don't know what other information might be useful to track down this hang. I'm using Recuva in a rather unusual situation that it doesn't really claim to work under - my sister's hard drive was partially reformatted by mistake, and now the partition shows up in Windows Explorer but claims it needs to be formatted when clicked upon. But the scan and analysis proceed as smoothly as if the drive were normal - the only problem is during the recovery. I tried deep scan once and that hung during the scan process itself. Could it be running out of memory somehow? It's the only application running at the time so that seems unlikely. Also, I don't know if this is significant... the hard drive I'm trying to recover was formerly a Windows XP boot drive, but is now the second drive in a Windows 2000 machine while I try to recover it.
  5. For what it's worth, the new build helps me. Beta 1.01.032 crashed immediately upon launch on my Win2K SP4 computer. Beta 1.01.037 loads and seems (so far) to run fine on the same computer.
  6. This simple feature would make CCleaner even more useful for me. Even a way to select the text of the issues list so that I could paste it into a text document would be very helpful. Well, that's what I claim, anyway. I dare you to prove otherwise! p.s. My what is from Earth?
  7. Hi, all - I hope this hasn't been suggested a million times before... I know CCleaner was intended primarily as a cleanup tool, but it could be very useful for diagnosis as well if a couple of minor features are added: 1) Some way to print or export (save to a local text file) the list of issues CCleaner finds in the registry. This way, I could refer to this list when repairing a system with registry problems and/or missing system files. 2) Some way to select (highlight) a number of specific issues and check/uncheck them based on my selection. Currently, the only ways I can check/uncheck issues are either Select/Deselect All, Select/Deselect All of Type, or check/uncheck individual issues, one at a time. I'd like to be able to use Shift- or Control- clicking to highlight a number of issues, then (perhaps) right-click on the selection and choose "Check selected issues" to check only the ones I've highlighted. Other than this, CCleaner is one hell of a product - thanks for making it!
  • Create New...

Important Information

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