File ok in Win2k - all null-bytes in XP

[John A.]

We have a very bizarre situation.

We have a removeable drive, formatted in NTFS.

When we have it plugged into a Win2k system we can read it just fine.

When we have it plugged into a WinXP system a few files appear to be
filled with null (00) bytes.

Any ideas what might be causing this? Corrupt file tables/whatever
that trips up XP but not 2k? Virus/trojan/whatever on the XP system?

Booting on the XP system recently we had a couple occurrences where it
ran a check on the drive and reindexed some files or something. Could
this be part of it? How can it be fixed? We already tried copying an
affected file to another dir with the 2k system. They both read as all
zeros on the XP system but read fine on the 2k system. One text file,
however, seemed to be recovered when I loaded it on the 2k system and
resaved it as a new file. That may not really be an option for
database files, though.

Has anyone encountered this and managed to fix it?

Thanks for any insight.
JA

 

[John A.]

We have a very bizarre situation.

We have a removeable drive, formatted in NTFS.

When we have it plugged into a Win2k system we can read it just fine.

When we have it plugged into a WinXP system a few files appear to be
filled with null (00) bytes.

Any ideas what might be causing this? Corrupt file tables/whatever
that trips up XP but not 2k? Virus/trojan/whatever on the XP system?

Booting on the XP system recently we had a couple occurrences where it
ran a check on the drive and reindexed some files or something. Could
this be part of it? How can it be fixed? We already tried copying an
affected file to another dir with the 2k system. They both read as all
zeros on the XP system but read fine on the 2k system. One text file,
however, seemed to be recovered when I loaded it on the 2k system and
resaved it as a new file. That may not really be an option for
database files, though.

Has anyone encountered this and managed to fix it?

Thanks for any insight.
JA

Well, I'm suspecting now it's either the drive going bad, or we need a
BIOS update on one system. I hope it's the latter.