Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About daveyboye

  • Rank
  • Birthday 19/05/1983

Profile Information

  • Gender
  • Location

Contact Methods

  • Yahoo
  • Skype
  1. My topic has got locked, but MrT has been in contact with me. This is what I wrote back to him: Well, we stopped the testing after confirming it with 3 SSDs on a Win 7 x64 platform. My writer's assistant has been doing some research on the specific Write File Windows API, and actually has found that it is frowned upon the SSD community. What that API does is write to any space on the hard drive that currently has no files, or files that aren't allocated by windows resources or programs...then completely delete that space. My contact with OCZ in their inspection of the returned drives h
  2. LoL, most enterprise businesses don't need an attorney to say whether or not they would take on the case. Most enterprise businesses have attorneys of their own or attorneys under retainer. We have seen many many similar suits under the same conditions. The vast majority don't win, but they do create wonderful attorney and court fees for the defendant. Getting back to the true issue, is actually having the developers recognize even the slightest problem WFS has on Solid State Drive. Then after considering that the feature isn't beneficial anyway to Solid State Drive, to take the neces
  3. Absolutely, WFS is not needed on Solid State Drives. That's why I believe Piriform should take the necessary action to permanently disable the feature when it detects a SSD. Also ishan, just like I mentioned before, I did not intend to make any threats. What I meant about the legal action statement is that enterprise businesses and even mainstream users who find themselves in this mess can file legal action against Piriform. This doesn't mean they will win or anything, but it can cause quite the hassle. Enterprise solutions who come across this problem have a lot on their plate to lose.
  4. Guys, let's start by saying I am not making any threats. I love CCleaner and the developers who put such quality time into it. I came onto these forums to shed light on a major catastrophic bug that CCleaner has in regards with Solid State Drives. The site that I write for has often featured CCleaner and all of our staff use it. However, since there is a major move from traditional hard drives to solid state drives as of lately, this incompatibility needs a lot of attention. One of my writer assistants came across this and brought it to my attention. We then proceeded to test it on a mul
  5. Can you please explain the process of how you tried to reproduce this problem. What was the configuration used and what Solid State Drives did you test? I am a writer for a review/news site and we have tested this with an OCZ Vertex with firmware 1.5, and OCZ Agility with firmware 1.5 and also a Kingston SSDNow M-Series all on a MSI 790fx-gd70 board using Windows 7 x64 Ultimate. Each "Wipe Free Space" operation would get stuck approx at 5%. After about 5 minutes of nothing, the computer reboots and then a Windows boot error displays. On further investigation, the bios doesn't even recogni
  6. Has this been investigated. I have confirmed this on two SSD's. This is a very major issue and one that could also cause legal action against Piriform.
  7. I have been using CCleaner for quite some time. I love the program. I however ran across something that could be detrimental to SSD users. Your option to "wipe free space" completely renders a SSD useless. Solid State Drives have reserved space on the drives for firmware and extra space. The "wipe free space" doesn't see these files as allocated by the operating system, thus removing them. Without any firmware on the drive, there is no way to flash firmware on it because both the bios and the operating system can not locate the drive. The only way for this problem to be fixed is for the drive
  • Create New...