From: "Rich Gauszka" 


"Mike N."  wrote in message
news:daqre2h7sua804p12n61mp4doi5j63eo4l{at}4ax.com...
> There are rumors from several customers that KB920958 and folders with the
> NTFS compression attribute will occasionally result in corrupt files in
> which the last 4 K of the file is set to the value of 0xDF.


There are some postings of it in microsoft.public.win2000.file_system
http://groups.google.com/group/microsoft.public.win2000.file_system/browse_thre
ad/thread/e4b7037b0a73dcd5/a56ac72f779e1f25?lnk=st&q=KB920958+compression&rnum=
1&hl=en#a56ac72f779e1f25

Hi Keith,

okay, I will attempt to uninstall Kb920958 tonight! That's the best lead yet.


I will also test the "compression" theory as soon as one of my
customers reports another failure with one of their files.


I definitely have seen at LEAST two files that are larger than 4096.
However, both are very close to a MULTIPLE of 4096 (close to 8K in one
case, in the other case 167,564 bytes = 163K).  I inspected the files. In
each case
the beginning of the files are good, and ONLY the last 4000 or so bytes
have the 0xDF byte pattern.


I too created a small TXT file (just one line) and it never corrupted,
while other files around it repeatedly did.


I can say, that I have seen corruptions with the following file types: .JPG
.GIF
.SWF


where the vast majority are small .JPG and .GIF thumbnails and so far I've
only found few files that are larger. But that may be deceiving, because
you simply may not notice the end of a larger file being corrupted, because
the it "starts" out correctly!

--- BBBS/NT v4.01 Flag-5