Image recovery: Recovering fragmented image files from flashmemory cards

cmyk wrote:
And if you took the time to study how FSI_Nxt_Free is implemented,
you wouldn't keep posting stuff like this. FSI_Nxt_Free points to the
lowest available cluster. Nothing more & nothing less.

That's not what FSI_Nxt_Free means. Microsoft gives the following
explaination:

This is a hint for the FAT driver. It indicates the cluster
number at which the driver should start looking for free
clusters. Because a FAT32 FAT is large, it can be rather time
consuming if there are a lot of allocated clusters at the start of
the FAT and the driver starts looking for a free cluster starting
at cluster 2. Typically this value is set to the last cluster
number that the driver allocated. If the value is 0xFFFFFFFF,
then there is no hint and the driver should start looking at
cluster 2. Any other value can be used, but should be checked
first to make sure it is a valid cluster number for the volume

Since it's just a hint there's nothing requiring anything to actually use
this field. However, even in places were fragmentation doesn't matter,
like a digital camera using a flash memory card, it would still speed
things up to use and update the field. As a result, I think it's safe to
assume that JPG files were allocated the Hans-Peter Diettrich described.

Ross Ridge

--
l/ // Ross Ridge -- The Great HTMU
[oo][oo]
-()-/()/ http://www.csclub.uwaterloo.ca/~rridge/
db //