file copy corruption

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

I have a serios problem with copying large files (50MB+):
Both command line command "copy /B" and copies in Explorer of large files
always risult in a slighly different (corrupt) copy without generating any
error message.

The number of different bytes is proportional to the lenght of the original.
The size of the copy is correct.
Position and value of the different bytes vary between each copy (attempt).

Example: A copy of a 300MB file compared with fc/B gives the following result:
D:\>fc /B aa.ape bb.ape
Comparing file aa.ape and BB.APE
0054204C: 7F 31
0054204D: D8 30
03DD478E: B8 F8
0B16184E: 7F AD
0B16184F: C4 0B
0BBC620C: CA 0D
0BBC620D: D7 F0
0BBC620E: C3 AD
0BBC620F: 7E 0B
0C6A00CC: 12 31
0C6A00CD: CA 30
0DE24C8C: E7 31
0DE24C8D: 5B 30
0DE24C8E: D2 71
0DE24C8F: 78 68
0E3D05CC: 1B 31
0E3D05CD: D9 30
0E3D05CE: 2E 71
0E3D05CF: 67 68
0FD1244C: 30 31
0FD1244D: DB 30

Some patterns repeat: The sequence 30 31 hex is often found in the
consecutive positions xxxxxxxC xxxxxxxD, while 68

hex occurs often si trova in position xxxxxxxF.

Though I encountered the problem first when masterizing with nero, it also
happens when copying from HD to HD or

create a copy on the same HD.

This behavior does not occur when using copy when startin windows is save
mode!
Therefore I exclude HW problems. Anyway, I already changed IDE cables and
run memtest and chkdsk /r. An update of the driver VIA 4in1 did not help
either.

I'am desperate!
Please help!

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Third post on this subject.

Please refer to the replies in your original post. There is no
point in posting the same item time and again.


"Berni" <Berni@discussions.microsoft.com> wrote in message
news:1664AAAA-F8F5-4B0B-A38B-A340D36CB08D@microsoft.com...
> I have a serios problem with copying large files (50MB+):
> Both command line command "copy /B" and copies in Explorer of large files
> always risult in a slighly different (corrupt) copy without generating any
> error message.
>
> The number of different bytes is proportional to the lenght of the
original.
> The size of the copy is correct.
> Position and value of the different bytes vary between each copy
(attempt).
>
> Example: A copy of a 300MB file compared with fc/B gives the following
result:
> D:\>fc /B aa.ape bb.ape
> Comparing file aa.ape and BB.APE
> 0054204C: 7F 31
> 0054204D: D8 30
> 03DD478E: B8 F8
> 0B16184E: 7F AD
> 0B16184F: C4 0B
> 0BBC620C: CA 0D
> 0BBC620D: D7 F0
> 0BBC620E: C3 AD
> 0BBC620F: 7E 0B
> 0C6A00CC: 12 31
> 0C6A00CD: CA 30
> 0DE24C8C: E7 31
> 0DE24C8D: 5B 30
> 0DE24C8E: D2 71
> 0DE24C8F: 78 68
> 0E3D05CC: 1B 31
> 0E3D05CD: D9 30
> 0E3D05CE: 2E 71
> 0E3D05CF: 67 68
> 0FD1244C: 30 31
> 0FD1244D: DB 30
>
> Some patterns repeat: The sequence 30 31 hex is often found in the
> consecutive positions xxxxxxxC xxxxxxxD, while 68
>
> hex occurs often si trova in position xxxxxxxF.
>
> Though I encountered the problem first when masterizing with nero, it also
> happens when copying from HD to HD or
>
> create a copy on the same HD.
>
> This behavior does not occur when using copy when startin windows is save
> mode!
> Therefore I exclude HW problems. Anyway, I already changed IDE cables and
> run memtest and chkdsk /r. An update of the driver VIA 4in1 did not help
> either.
>
> I'am desperate!
> Please help!