Jump to content


Experienced Members
  • Posts

  • Joined

  • Last visited


0 Neutral
  1. Good to see nearly 2 months on that Piriform doesn't see fit to respond or even acknowledge the problem, nor any real discussion about the issue from the general user base. It's a sad state of affairs when posts and threads need to be censored by overzealous moderators, so as to ensure other, more capable programs, are not directly mentioned. God forbid users are made aware of more functional alternatives. I think the simple take away here is that Piriform aren't interested in improving their software with respect to competing against other offerings on the market.
  2. "64-bit machine" is completely valid, as there were CPU's back in the day that were not 64-bit compliant (i.e. old Pentium's). Yes, you're right, it is a nit pick, a completely incorrect one.
  3. Are you talking about the after defrag performance analysis? I would completely ignore it because it's totally off. It reports my Western Digital Black as getting a couple KB per second total performance, and my Samsung 951 NVME as getting less than 120MB/s, when it benches over 1.5GB/s in any other software. The performance analysis is completely and utterly wrong in every way. I'm glad your time is so valuable. Thanks for letting us know.
  4. I don't think removing the names of competing software is fair. You don't see Lenovo deleting posts that mention Dell or HP, nor do you Sony removing threads about LG or Samsung TV's on their forums. I'm using them as examples so that Piriform might look further into the issue. Defraggler is a free piece of software, and compared to "COMPETING SOFTWARE", it's much cheaper, therefore it's not really a threat to mention them. Regardless i doubt my post will make any difference, but either way it's poor form. 1. The software should be smart enough to do this. 2. I don't want to manually go through all the files it finds and defrag them. 3. Manually defragging random small files creates gaps in the drive and lowers the amount of contiguous space which will result in more fragmentation. 4. For the sake of ease of use, for new users, and for general simplicity, the software should automatically figure out what to do rather than defragging for 9 hours, then defragging again for another 9 hours. 5. In "normal" usage scenarios the software should analyze the disk map and figure out how to defrag in the least amount of moves possible. If there's a 30KB file in the middle of the drive, the 300GB of data beneath it shouldn't be moved down. Again, the software should be figuring out how to defrag in the most efficient manner (in the least number of moves possible). edit: Also, still doesn't explain the low utilisation / slow defrag speed in comparison to "COMPETING SOFTWARE". Finally, i realise you'll have counter-points to everything i mentioned, but at the end of the day it comes down to improving the software, making it more efficient, easier to use, and generally more polished. Yes we can go back and forth about how you can locate individual files to defrag them, but again, it's about the usability of the software. If we're going to manually defrag all files, why not remove the entire "defrag" option then? How many features can be stripped before the point is no longer valid?
  5. If the HDD is not being detected by either Windows nor your BIOS then it's not a good sign. Could be an issue with the PCB failing to even power up and identify itself. Defragging a large amount of data is very taxing on the HDD and can bring about failure if a drive is already nearing death. Always keep that in mind when it comes to defragging HDD's that won't see a benefit from increased seek/read performance (i.e. backup drives that aren't often accessed). In your case that's not really applicable since you were defragging your games HDD, but keep it in mind for future HDD's. Usually if you've got bad sectors or even a catastrophic physical failure, the HDD should still at the very least self identify in the BIOS. If you don't see anything and don't want to spend money recovering, start off with these basic steps. This might not be scientific but this is what i'd personally do if i was in your situation. 1. Disconnect the HDD and replace the SATA cable. Plug the HDD into a different SATA port on your motherboard and test. Try to use a port which you know is working (i.e., where another HDD is plugged in, or your CD drive, etc). 2. Failing the above, try another computer if you have access to one. If that fails, move on: 1. Disconnect all other hard drives and peripherals, and any case fans if applicable to reduce the amount of noise your computer can make. 2. Turn on your computer with the drive connected and see if you can hear it spin up, if it's making any ticking noises. 3. If you don't hear anything, try removing it from the case, but leave the power and SATA cables connected then turn it on again and put your ear up against it. Any spin up sound or ticking? 4. If you can hear ticking, is it a constant ticking/knocking noise in a rhythm? If you can hear constant ticking (i.e. the tick of death), then you've got a mechanical failure which will need professional data recovery. If no ticking noise but you can hear it spinning up OR, if you can't hear anything at all and it seems to be dead: 1. Remove the HDD from your computer 2. Install it into a USB caddy (3.5" HDD USB caddy, can be bought for cheap) 3. Boot into windows and connect the drive, test again. If still nothing, then try reseating the PCB (printed circuit board). 1. Remove the PCB from the HDD by undoing a few screws (usually little torx screws) on the belly of the HDD. 2. After you've removed the screws it can sometimes take a LITTLE BIT of force to pop off the PCB as it might be stuck down with thermal paste, light glue, or sticky thermal pads. It shouldn't require excessive force to remove. It will look like this once removed: 3. Check the gold contacts and ensure they're clean. 4. If not, clean with high purity rubbing alcohol and a q-tip then reattach. 5. Start at the top and try testing again. If still no luck, 1. Remove the PCB again, and note any part numbers, revision, firmware, etc, on the PCB 2. Jump onto eBay, or contact a data recovery centre and see if you can purchase a replacement PCB. 3. MAKE 100% SURE to find the exact same PCB again, including part number, firmware, and revision. 4. Once you purchase a new one, once again, fit it back onto the HDD (after cleaning the gold contacts), and test once more. If after all that it's still dead, you can start trying weird stuff like putting the HDD into a freezer (Google "HDD freezer") and so on, or look into professional data recovery. Hope that helps.
  6. Hi all, Long time supporter of Piriform. Even bought their software a little while back, and donated back in the day when the software used to be 100% free. I've tried for a long while to like Defraggler but i'm running into issues, namely two main issues: Defrag logic and low utilisation. First and foremost the defragging engine seems to be very slow despite using next to no resources. Right now it's defragging my games HDD (7200RPM mechanical HDD), and it has taken hours, and there are several more hours to go, but it's currently using next to no CPU, and only 1-5% HDD (screenshot below). The second bigger issue is the defragging logic. My games HDD isn't used very often, over the course of a few days it MIGHT get a few kilobytes worth of fragmented files (i.e., Steam log files or something. Usually fragmentation after a day or two is only 5 or 10 fragments totalling 100KB or less) If i defrag my games drive on Monday, it'll take several hours to finish. On Wednesday i'll analyse the drive and find a couple fragments/few kilobytes of fragmented text files and such. If i defrag the drive again, rather than moving these meainingless and small files to the bottom of the drive, or compacting the files as tightly as possible, Defraggler instead begins to defrag the ENTIRE hard drive from the very top, moving ALL files down and slowly re-ordering everything. This means that defragging with only a couple kilobytes of fragmented files equals to several hours of defragging. On top of the issue above (low utilisation, slow to finish), this also puts a lot of needless stress on the hard drive, as it's moving a bunch of files that really don't need to be moved, for what amounts to virtually zero improvement in performance and read time (i have tested with Crystal Diskmark and other software), which means that it will result in your HDD's life expectancy being reduced, again, for virtually no improvement in performance. Compare this to [competing software] -- All of these solutions are more intelligent in that they won't completely move every single file in the entire HDD in order to defrag a few kilobytes of worthless text log files. Can Piriform comment on this? See screenshot below. Defragging an already defragged HDD a day later. 1. Notice the low utilisation. 2. Notice how many hours it's going to take. 3. Notice there are 0 fragments, and rather than filling gaps with files from the bottom of the drive to make sure everything is contiguous, Defraggler is instead moving every single file on the entire HDD.
  7. Same issue, defragging is taking excessively long, with 1-5% HDD usage and virtually no CPU or RAM utilisation.
  8. Same problem. One thing to mention though, it managed to detect some APK's i had in a user created folder and was able to delete those during the clean, but the general "cache" is not cleaned. Results: Cleaned: Analysing again a few seconds later:
  9. Well it's a worthy donation anyway. It's good to support free, clean software. I've donated a few times myself. Although hopefully Piriform will offer you something in this situation (if you're looking for a refund or whatever)
  10. Ramzy

    Memory issue

    Congratulations Piriform! Bug solved in the 1.18.185 update!
  11. Yeah, ccleaner would be a lot easier if it had some sort of bootstrapper. Something that would allow it to update itself without having to manually download installers.
  12. Ramzy

    Speccy crash

    v1.00.108 ran fine, however v1.00.125 crashes during the analyzing phase. The crash occurs while analyzing CPU, RAM, motherboard, and hard drives. Operating system, graphics, optical drives and audio all display fine. Speccy creates a dump file upon crashing, however that file is 120MB. 30MB if compressed with WinRAR. I'm willing to upload it if it'll be useful. - Windows 7 x64 - ASUS P5E motherboard - Core2Quad Q9550 @ 3.6GHz - EVGA GTX285 - Corsair 8GB DDR2-800MHz RAM - 3x1TB WD HDD, 2x400GB RAID0
  13. Yup, same in Windows 7. BTW you CAN delete IE, depending on the version of Windows you're using. It'll simply remove all traces of the iexplore.exe program so that you never have to physically deal with it again (aside from programs using the rendering engine).
  14. Ramzy


    Index.dat files are a part of internet explorer and are generated automatically. They are small active databases that contain mostly trash data, but it can also store search history such as autocomplete.
  15. Internet Explorer is a core part of Windows. Developers usually use the IE rendering engine to display websites from within their native applications. For instance, Steam uses the IE rendering engine to display websites from within the Steam browser. Other programs like XFIRE, Yahoo Messenger, AOL messenger, and so on, use the IE engine to display advertisements from within their messenger windows. A lot of programs rely on the IE rendering engine in some way or another, and as a result, you'll always end up with IE cookies, temp files, and so on. You can't really prevent it, because even if you delete IE, you'll only be deleting the front end. The rendering engine will still exist, and programs will still rely on it, and there's nothing you can really do. edit: Try right clicking in a program like Steam and you'll quickly find that the context menu is exactly like the IE context menu.
  • Create New...

Important Information

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