Disk Tune Error

[jimk]

I'm getting an error when running DiskTune 1.1.27

Run-time error '28' Out of stack space

This error happens when I select both Analyze and Defrag options.

My system:
  Windows XP-SP3
  Intel Quad Code w/4GB memory
  SATA-2 drives

I run ZoneAlarm anti-virus, but I get the same error when I have it shut down.

I hope we can get this worked out as I'm very interested in running this utility which has very good reviews.

Thanks,
Jim

[Joep]

Hello,

It's the second time someone informed me of this error and I have not been able to reproduce it yet. Could you please select the drive you are trying to analyse in the right pane of the Expolorer (Windows) > then select ALL files and folders > right-click any of them while leaving the selection intact > then select properties and tell me the number of files and folders on that drive?

Also: Is this at the stage where DiskTune displays the files/folders numbers going up (window caption says "Enumerating files"), or, is it already showing the progress-bar (windows caption says "Analyzing files")? That would also help me pin down the location of the problem.

Your configuration is fine, plenty of memory and all that, DiskTune isn't very memory hungry.

[jimk]

Very strange, the error might have to do with the number of fragmented segments.  After I posted this error, I ran the standard Windows XP Defrag tool.  Now I no longer get the error.

Jim

BTW: 8774 Folders, 124071 files in 54GB ~50% of the volume.

[Joep]

Hello,

Thank you for this info. That helps, because indeed this suggests the issue is with ther analysis of file fragmentation itself and has got nothing to do with the number of folders and how deep folders are nested. The latter was what I was assuming and I have been trying to recreate the error based on that assumption creating zillions of folders and nesting them as deep as Windows would allow me. It got me no-where.

But, you can't remember exactly during which stage the error occured: Was DiskTune enumerating files or already analysing (if the latter the progressbar kicks in displaying progress)?