Jump to content
CCleaner Community Forums

rschneider

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rschneider

  • Rank
    Newbie

Recent Profile Visitors

199 profile views
  1. The HDD I refer to in my original post has a highly fragmented C: drive (42%), and needs the robust defrag accorded to HDDs. ADDITIONAL INFO: Defraggler incorrectly reports all 3 NTFS partitions on this HDD as SSD - "HOWEVER", it correctly reports the FAT32 OEM Tools partition as HDD. (That's right, 1 drive with 4 partitions, with 3 being reported incorrectly as SSD, and 1 partition - the FAT32 one - reported correctly as HDD). - Maybe this info may help Piriform devs get some insight into the bug. With 42% fragmentation, I need the robust defrag accorded to HDDs. But I don't trust Defraggler to do the job right after misidentifying the drive as SSD. Why dismiss a Warning about SSD defragging, take the time to defrag/optimize/whatever, and NOT get a proper HDD defrag? I (and other users) can't trust Defraggler due to this this bug. Please, Piriform, reply with accurately researched answers to these questions (not mere suppositions): Can I use Defraggler v2.22 to robustly defrag an improperly ID'd "SSD"? Is there some Registry hack, Defraggler .ini file, or other way to change the incorrect SSD flag to HDD? If not, is there an older version of Defraggler that omits the HDD/SSD detection (i.e. no offer of Optimize vs Defrag)? I cannot be the only user of Defraggler who wants answers to these questions. My suggestion - as an engineer - is this: If the bug cannot be banished to the point that Defraggler can, with a VERY high degree of precision and consistency, differentiate between HDDs and SSDs, automatic drive detection determination of defrag algorithms MUST be removed. Present the user with a prominent WARNING regarding SSD defragging; give the user info as to how to determine how to ID their drive type; and make the user MANUALLY select "Optimize SSD" or "Defrag HDD" before proceeding - with a restatement of the danger of defragging an SSD. Do NOT take away user choice when your software relies on faulty drive detection algorithms. I'll have to use another Defrag program if this issue isn't responded to - in fact I'm looking at others RIGHT NOW, because I have a 42% fragmentation C: drive that needs attention. I loved Defraggler for years (I particularly appreciate the SETTINGS -> OPTIONS -> ADVANCED checkbox to "Stop VSS when defragmenting NTFS volume"). That "Turn Off VSS" made your product superior to 2 other defraggers I used that caused MASSIVE numbers of Restore Point creations during defrag (once exceeding 30GB), that actually made the drive highly fragmented with the new Restore Points being written as the drive was being defragged. I came for the "Turn Off VSS", and stayed for the excellent performance of Defraggler otherwise - but I may now be forced to leave. What a pity, if Piriform can't fix this. My drive's health is more important than my love of Piriform software. (And remember, Speccy is ALSO misidentifying this HDD as an SSD). Sorry if this is considered a TL;DR rant. I'm not Ranting - I'm Pleading: Piriform, please fix this Really Bad bug.
  2. BOTH Speccy v1.32.740 AND Defraggler v2.22.995 are misidentifying a WD Black 750GB HDD an an SSD. The drive is Western Digital WDC WD7500BPKX-22HPJT0. It was manufactured Aug 2014, so is nothing new to the tech world - it is a multiplatter rotatating disk HDD. WHY are both Speccy and Defraggler misidentifying it as an SSD? Defraggler has had this bug since v2.07 back in 2011, if not earlier. WHY hasn't this bug been fixed? By the way, I've used Speccy, Defraggler, CCleaner, and Recuva for MANY years, and have been a Piriform evangelist also for several years (and I install your products on computers I work on for others). But this long-running bug (misidentifying both SSDs as HDDs "AND" HDDs as SSDs) - as reported in your Community Forum by users - should have been fixed LONG AGO. When are you going to fix this bug? It is very frustrating to your users.
  3. BOTH Speccy v1.32.740 AND Defraggler v2.22.995 are misidentifying a WD Black 750GB HDD an an SSD. The drive is Western Digital WDC WD7500BPKX-22HPJT0. It was manufactured Aug 2014, so is nothing new to the tech world - it is a multiplatter rotatating disk HDD. WHY are both Speccy and Defraggler misidentifying it as an SSD? Defraggler has had this bug since v2.07 back in 2011, if not earlier. WHY hasn't this bug been fixed? By the way, I've used Speccy, Defraggler, CCleaner, and Recuva for MANY years, and have been a Piriform evangelist also for several years (and I install your products on computers I work on for others). But this long-running bug (misidentifying both SSDs as HDDs "AND" HDDs as SSDs) - as reported in your Community Forum by users - should have been fixed LONG AGO. When are you going to fix this bug? It is very frustrating to your users.
  4. I updated to Speccy v1.24.632 today; I was previously using v1.16 for more than a year. SPECCY 1.24 DOES NOT DISPLAY ANY GPU TEMP, WHILE THE OLD VERSION I USED (v1.16) ALWAYS DID, AND ACCURATELY. [Laptop Integrated graphics: 128MB NVIDIA GeForce 7000M / nForce 610M (HP)] Speccy users since about v1.20 have been reporting that Speccy no longer reports GPU temperatures - THIS IS A LONG-TERM BUG IN SPECCY THAT PIRIFORM HAS BEEN AWARE OF, BUT HAS NOT FIXED. Piriform should tell us what is going on - why this has taken so long for them to effectively address the issue - and how long users must wait before the problem will be solved. Since the old version of Speccy (v1.16) did NOT suffer from this problem, it is obvious that several newer versions of Speccy have regressed to defective program code that no longer works properly to display GPU temps - something old versions of Speccy did VERY WELL FOR A LONG TIME. By the way, I have the open-source freeware utility "Open Hardware Monitor" installed, which does just fine in displaying GPU temp (as well as each CPU core temp SEPARATELY, and hard drive temps as well), AND it displays Current, Minimum, and Maximum temps (since you last reset the temp logging memory). Open Hardware Monitor also displays Current, Minimum and Maximum CPU core loads in %, as well as motherboard bus and CPU core(s) clock speeds in MHz. It would be nice if Speccy would eventually add "Current/Min/Max" capabilities, BUT ONLY AFTER ADDRESSING THE BUG OF FAILING TO DISPLAY THE GPU TEMP !!! It would be nice to hear from Piriform in response to these bug reports - but due to the long-term status of this bug, I'm not going to hold my breath.
×
×
  • Create New...