i noticed yesterday in defragger when i highlighted a fragmented file to see what blocks it was in it was always marking first one but the file it not even listed in it
even after fragmenting drive then updating Microsoft security signatures again same thing happens
it clearly marking wrong blocks for the file
i did screen shots to show you
please fix this issue soon
thanks
might be more of a 'rounding error'.
the cluster block usage and the file representation is not an exact match up.
sometimes selecting a file and seeing its blocks or selecting a block and seeing its files gives mixed results. treat it more like a guide than an exact science.
for example, there is some sort of threshold DF uses, say a file has a frag in one block, it may not show that until it has, say, 3 frags in that block. (that's just an example but it seems to fit with what I've experienced DF doing)
but this issue should be able to be fixed i never seen it do this before
the good news is the Dev Team see all these bugs and suggestions, so be assured they will be aware of your post.
i will be waiting for Dev team to reply
While MTA is correct, that the dev team does read all threads, they rarely sound off in the forum unless they need more information on the bug.
dear dev
i need this bug fixed soon as you can
is this problem preventing you from using DF? (just asking)
what version of DF are you running?
if so, do you remember the previous version it didn't happen with? (you say you hadn't seen it before)
personally I think it's always done it (what I call the rounding error) but if you can't use the version try reverting back to an earlier version until DF behaves the way you'd prefer.
previous versions can be found at FileHippo, as one example. Just be wary of 'fake' download buttons.
i just noticed this bug on a windows 7 64 currently using this system
sorry i forgot i used it before on windows xp
i am sure there a fix for this bug
when will this issue be solved
i need this problem fixed soon as you can
i need a update on this soon
don't hold your breath.
first, if it is a bug, the Dev Team read these post so will be aware of your issue.
second, it has been around for a while.
third, probably not high up on their list.
well, tell DEV to get on the stick! I'm sure its an easy fix. I submitted this as a bug too, without realizing the bug was found 3 months ago and never fixed.
-faye kane ♀ girl brain
easy or not, bug or not, who knows.
all you can do is make them aware - and wait.....
luckily it's small fry in the greater scheme of things.