Jump to content

John Gray

Experienced Members
  • Posts

  • Joined

  • Last visited

Everything posted by John Gray

  1. I fnd that caffeine no longer works in Windows 7 (Pro), whereas it did, very well, in XP Pro...
  2. Windows 7 SP1 fully-patched, 64-bit. Disk is 2 TB, 30% full. Defrag takes place, apparently successfully, but on re-execution it crashes at 43%. CHKDSK has been run on the offending disk, but the Defraggler crash still occurs. Here's the brief crash info. Can I get you any more information? Problem signature: Problem Event Name: BEX64 Application Name: Defraggler64.exe Application Version: Application Timestamp: 4e13ff88 Fault Module Name: Defraggler64.exe Fault Module Version: Fault Module Timestamp: 4e13ff88 Exception Offset: 00000000001c82c8 Exception Code: c000000d Exception Data: 0000000000000000 OS Version: 6.1.7601. Locale ID: 2057 Additional Information 1: c6e0 Additional Information 2: c6e0e25c260d29f75ab13edbfaa32dea Additional Information 3: 4006 Additional Information 4: 40061da3d83c2933fcd424e21ba4489f
  3. Another clue for the developers: these chequer-board patterns happen when C:\$MFT is the 'file' being worked on...
  4. I'm surprised that nobody appears to have commented on the unusual and rapidly-changing chequer-board-type screen pattern which often takes place shortly before the end of fragmentation. This has happened over several recent versions of Defraggler, on XP SP3 and Win7 64-bit computers, at least. It usually lasts 5-10 seconds with the pattern changing, and occupying all of the "free space" area. Eventually it stops and the defragging finishes normally. Can I do anything to assist in debugging this? (Here's one 'frame' of the pattern...)
  5. On the first run on a 280 GB disk with only 4% free space, Defraggler v2 beta crashed shortly after it put up the coloured disk map. On the second run it seems to be working. Is there any dump information that I can provide to assist? The only difference I can see with the new beta is that the squares in the disk map are pastel coloured!
  6. If you rename the INI file, try it, and rename the INI file back to its original name, you will have your answer oh so quickly!
  7. The first defrag often takes longer than you ever thought possible!
  8. That's already there! Click on Settings at the top, then in the drop-down menu click on the final option "Shutdown after Defrag"... When finished it counts down from about 60 seconds before shutting the PC down.
  9. It is not a good idea to attempt to defrag simultaneously more than one partition on the same hard disk, because of the excessive and entirely unproductive amount of disk heads movement which would be caused. Defragmenting several hard drives at a time would, of course, not have the same problem!
  10. Well, my Defraggler memory usage has stayed fairly constant at 361,024 KB (give or take a MB or so) for about half an hour while defragging. Memory leaks cause the amount of memory used to increase with time, and (some of) the memory is not returned to the memory pool when the leaky program terminates. Is this what you observe?
  11. Use something like TreeSize Free to determine which folders/directories are using lots of disk space, before running Defraggler, and after...
  12. What do you think happens when a computer starts up? Yes, files get written! All over the hard disk. So some will inevitably be fragmented. That's the way it works...
  13. For each Piriform product, choose the final download on the Builds page, which is the Slim version, toolbar-free. For example, Defraggler Builds...
  14. Did you think what could be happening to the disk heads, if you had been allowed to defragment multiple partitions on the same hard disk?
  15. It wouldn't surprise me if any active program would try to use as much memory space as it needs, if nothing else is running. Surely that's the way Windows memory allocation/optimisation is supposed to work?
  16. Another possibility is that your page file and /or your hibernate file is fragmented. These are usually big files and Defraggler counts them in the total fragmented percentage.
  17. And now for Recuva, giving the full set...
  18. I restarted an almost completely finished defrag (97%) to get some diagnostics, and left it overnight, but was amazed to find that it didn't finish for over 12 hours! The debug file is about 15 MB uncompressed, 1,1 MB zipped, and after the first 8/9 pages each line terminates with "Destination block is not free." I don't know if that has any significance... Is there an address to which I can send the debug zip file, please, so that it can be looked at? Thanks!
  19. It won't be of any comfort to the OP, but I have run Defraggler on both WS2003 and WS2003 R2 without incident...
  20. That sounds a bit vague to me. Is the external hard drive connected to one of your PCs via a USB interface, and shared on that PC , so that the other PC can see it? Or are you talking about a NAS device?
  21. I've noticed that if I Stop a Defraggler GUI run, then the Defrag button is greyed-out, and only Analyse can be done. It's necessary to terminate Defraggler and restart it again to be able to do a Defrag. Does anyone else get this (I'm on XP Pro SP3)?
  22. Much the same as most people, then, if they run it at any time when there are no obvious disk problems! The snag is that it can take a variable amount of time - but usually hours. The bigger your hard disk is, usually the longer it will take. But 15-20 years ago, under NT 3.5, we would wonder whether a CHKDSK we set off on a server's Storageworks drives on a Friday evening would finish before start of work on Monday morning! Nail-biting stuff...
  • Create New...

Important Information

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