Jump to content
CCleaner Community Forums

martinu

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About martinu

  • Rank
    Newbie

Recent Profile Visitors

90 profile views
  1. Version V2.22.995 (64-bit) I've noticed recently that on several NTFS drives on my Windows 7 Home Premium PC, there are blocks which are shown as being allocated on the map but which do not display an associated filename if I left-click on a block or mouse over the block. The presence of the blocks still prevents a file from being defragmented to use them, but they cannot be moved to the end of the disk or any other operation. Contrast "No files in this block.png" and "1 file in this block.png". The files showed up previously when I clicked on then, but after moving a few other files, they became "orphaned". I've been using the same version of Defraggler (the latest) since long before the problem was first noticed. Rebooting (to force a dismount/remount) does not cure the problem. I've seen it both with SATA drives and with external USB drives (which probably have USB-to-SATA converters internally). I've seen it on drives with plenty of disk space (eg the C drive that has about 50% free). Moving folders to another drive does actually remove the "stuck blocks", so they really are being used by files (they are not orphaned) but the stuck blocks return (though not in the same place) if I copy the folder back again. I've used Defraggler for many years (both doing full and freespace defragging) but I've only noticed this symptom in the last few months. Is this a known problem?
  2. I'm using Defraggler 2.18.945 (64-bit). I noticed that a recent update has added the Statistics tab, so I used it to measure the performance of all my drives. And they are not at all what I'd expect. My PC has three SATA/300 drives, C, S and T. There is also a USB2 hard drive plugged in - drive J. I'd expect C, S and T to have fairly similar speeds, and J to be somewhat slower. But the graph of the speeds (see attached) shows the C drive to be very slow and the speeds of S and T to be much faster. On several different runs, S is sometimes faster than T and sometimes slower: the example shown here has S=116 MB/sec and T=84 MB/sec. C, the system drive, is 1.3 MB/sec - VERY slow. When I've copied large (eg 1GB) files between two folders on the same drive, I've found that all three drives are about 30-50 MB/sec. J, the USB drive, is about 20 MB/sec. Sadly the help files at http://www.piriform.com/docs/defraggler don't mention the various tabs such as Health and Statistics - I wonder if they need to be updated to keep pace with the product :-) All four drives are NTFS, by the way.
  3. Ah, I'd fallen into the trap of assuming that the moderators were Piriform staff who had access to the bug-reporting and -monitoring system that the dev team used. Maybe I'm used to forums such as the one for VideoRedo where bugs usually prompt a quick reponse by a staff member and often a new version, fixing the bug, within a day or so if it's a straighforward bug. Anyway, let's see what the next build brings, maybe after the Christmas break.
  4. Has this bug been officially confirmed and logged by the support team at Piriform? I'm surprised there hasn't been an update, incorporating a fix for this regression bug first noticed in the current version, 2.16.809. Administrator: You could merge this topic with the other one on the same subject, http://forum.piriform.com/index.php?showtopic=39693
  5. Has this bug been officially confirmed and logged by the support team at Piriform? I'm surprised there hasn't been an update, incorporating a fix for this regression bug first noticed in the current version, 2.16.809.
  6. See also thread http://forum.pirifor...12 which someone else raised independently of you. I'd come to the same conclusion as you that the "Defrag progress" popup has accidentally been made modal in the latest V2.16.809 version.
  7. How weird: two of us are experiencing the symptom and two of us aren't. I've just installed it on another Win 7 SP1 64-bit PC and that is experiencing the same fault with the latest version but not with any earlier ones. I don't have a Windows 8 PC to try it on. When I get chance I'll dig out my Windows XP PC and try on that. Thank goodness for being able to roll back to an earlier version. In case it's relevant, both my Windows 7 PCs are Home Premium. They both have AVG 2014 (free) installed and running. They are both running the free (not Pro) version of Defraggler. It's only a problem if you do a file defrag (File tab, select one/many/all tick boxes, Defrag Checked button) and not if you do a disk defrag (Disk tab, Defrag button) because only in the former case does the "Defrag progress" box appear. For older versions, this box has a grey (unselected, non-focus) stripe whereas for V2.16.809 the "Defrag progress" dialogue box always has a blue (selected, focus) strip which flashes if I try to select the minimise/maxmimise window-control buttons or any of the tabs such as Disk, Health etc. If Piriform need any further info on PC setup in case it's a strange interaction with something else, let me know.
  8. Confirmed here. The fault exists in 2.16.809 and did not exist in 2.15.742 or any previous version. This is with Windows 7 x64 SP1. Having installed 2.16 and experienced the fault, I installed an older version (thanks FileHippo for keeping older versions!) and normal service has been resumed. It seems that the progress box that appears in the middle of the screen is now modal and does not allow any other controls (eg minimise/maximise window button or tabs for changing between Drive, File List, Search, Drive Map, Health) to be clicked on once defragging has begun, whereas this was possible with earlier versions. It is frustrating not to be able to minimise the window to an icon or to be able to start a File defrag and then check the progress on the Drive tab of the number of files remaining to be defragged.
×
×
  • Create New...