I never let any defraggers run on a schedule, I always run them manually.

So it's curious to hear that it allows such a high amount of fragmentation to occur before acting.



Maybe they ran out of plates....

Originally Posted by smarteyeball

I never let any defraggers run on a schedule, I always run them manually.

So it's curious to hear that it allows such a high amount of fragmentation to occur before acting.

Maybe they ran out of plates....

I felt the same way. I used one in the past that actually started defragging as soon as you stopped typing. It was almost hilarious. You'd copy a bunch of files or whatever, then as soon as you quit inputting to the PC it would move the stuff around. Talk about crazy!! It was working the disk like an order of magnitude more than normal in order to "save" it. I can't recall the name of the defrag program but I think it was a single programmer freeware.

There are times when I let the machines sit so if I thought I could trust the "idle" detection to take disk activity into account and the app was stable, I might go for automatic. But I think it's still too soon. I'm hoping one or two revisions and Auslogics will get it right.

Yeah, it's usually one extreme or another. Overly aggressive or it never starts (built in Windows defrag is a prime example)

Fingers crossed they can get it sorted.

Originally Posted by TeamanFL

The version I have is 2.1.2.45. This is newer than yours. 2.1.2 comes after 2.1.1, and is newer. Am I wrong?

Sorta! Check out time-span between posts #1 and #5. An unusual event for Auslogics who went from one new version, to an even newer one in a short time.

Heading right at the start should have been 'Auslogics Disk Defrag - a newer version is released'., leaving the ability to include the newer version number, release date and a link, in the text.

Originally Posted by smarteyeball

Yeah, it's usually one extreme or another. Overly aggressive or it never starts (built in Windows defrag is a prime example)

Fingers crossed they can get it sorted.

I got an answer back from Auslogics support. They say currently a fragmentation level trigger of 5% is hard-wired into the program. Not adjustable by the user.

I've had it sit idle, do the analysis, and do nothing, with levels as high as 25%. In fact I've never seen it fire automatically yet other than to analyze. That's what I said in my reply.