Re: Since weekend update, small files up to 4096 bytes get corrupted
- From: "lily" <lilybristol@xxxxxxxxxxxx>
- Date: 12 Sep 2006 07:26:36 -0700
We are experiencing something very similar at my company, but it's our
customers that are having the problem, not us.
Our product is a Windows-based product that is currently being
supported back to Windows 98. One of the things we do is save
information (data, graphs, etc.) using OLE structured storage. We
compress some of the larger data streams using a third party package.
Since Sept 5, 2006 our Tech Support staff has received three corrupted
files which, upon further review by the Software Development team, show
the presence of 0xdf at the end of the compressed stream.
Some information about the occurrence and amount of 0xdf:
Corruption 1: Compressed data stream size - 214749 bytes
0xdf starts at byte 210944
Total 0xdf bytes - 3805
Corruption 2: Compressed data stream size - 901867 bytes
0xdf starts at byte 898048
Total 0xdf bytes - 3819
Corruption 3: Compressed data stream size - 98889 bytes
0xdf starts at byte 95232
Total 0xdf bytes - 3657
This is devastating to our customers because subsequent attempts by our
software to open the saved file fail because the "decompression"
algorithm fails.
We are currently gathering information from the affected customers to
see if hot fix KB920958 is a possibility.
KeithMail wrote:
YES I have been in a losing battle with Msoft support since thursday last
week.
For me, Its KB920958 and it can be forced to happen if the data folder is
compressed (with explorer) and trigger it to happen immediately with a
chkdsk c: /f and a reboot
otherwise you have to wait for a while for it to go bad. We assume the
compressoin is done by a LAZY process and sin't immediate.
I don't think its the length as once the file is corrupt I have edited the
contents to other values and replaced it without a problem, there must be a
trigger byte sequence or something.
If you look at the file with the 2000 resource kit dskprobe sector editor it
complains about the length.
Are you using compressed folders for yourr data cos I can't get it to fail
otherwise and that seems to be my key trigger.
We have disabled antivirus and gone through hoops to prove the point.
Keith
"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:urNFVhyxGHA.4972@xxxxxxxxxxxxxxxxxxxxxxx
Multi-posted - see your other posts. Please use cross-postingappear
if you wish to address several newsgroups. Multiposting wastes
everybody's time.
"Andy Schmidt" <AndySchmidt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D826AFE9-2AB1-4B2F-AE11-CC27702F574A@xxxxxxxxxxxxxxxx
Hi,but
I have two different servers (different models and manufacturing years),
both of them running Windows 2000 server with software mirrored NTFSdrives,
which suddenly corrupt small image thumbnail files after an hour or two.
No larger file sizes seem to be effected. The file content is set to all
binary 0xdf.
If we replace those files with valid copies, then those files will
totime
be correct for a while (probably read back from cache) but after some
samethey will "revert" back to all 0xdf.
I have since been in contact with another customer who has the exact
productproblem with his Windows 2000 server also since around the past weekend.In
the days prior we did install recent security fixes and Microsoft
updates that were released in the past month.
Is there anyone else out there with the same problem?
.
- Prev by Date: Re: Since weekend update, small files up to 4096 bytes get corrupt
- Next by Date: Re: Microsoft confirms Hotfix 920958 garbles compressed, binary files
- Previous by thread: Re: about drive remap?
- Next by thread: Re: Since weekend update, small files up to 4096 bytes get corrupted
- Index(es):
Loading