Re: large file copy results in corrupted copies

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Berni" <Berni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CD7445ED-5FF4-431D-828A-AECB2DF99BE6@xxxxxxxxxxxxxxxx
>I have a problem when copying large files (50MB+):
> Both the DOS copy /B and the drag/drop or copy/paste methods in explorer
> result always in a slightly different (corrupt) copy without generating
> any
> error message. Aparently everything is fine but when checking on binary
> level, there are differences. Depending on the application this result in
> unreadble files.
> The number of changed bytes is proportional to the length of the file.
>
> Example: when I copy a file of about 300MB it results in a compare as
> follows:
>> 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
>>
> There are some patterns which repeat themselves. The sequence 30 31 hex
> often appear in the adjacent positions xxxxxxxC xxxxxxxD, while 68 appears
> in
> position xxxxxxxF.
>
> I have 2 Harddisks but it does not matter which is source or destination,
> it
> can also coincide. (I first noted it when nero in verification phase found
> differences between source and masterized copy)
>
> The errors do not occure when i use DOS copy in Windows started in save
> mode!
>
> Therefore I exclude HW problems. (Anyway I already changed IDE cables and
> run memtest). Also, updating the driver VIA 4in1 did not help.
>
> please, help!

Not sure whether the D: drive you indicate is local or network.

I had problems of a similar nature about 12 years ago with Netware "lite,"
which would randomly change bytes in large copied files. The destination
file would occasionally have bytes changed - always in the same files, same
byte-offset, and the changed-to pattern was always one of a small set of
rogue bytes.

As far as I'm aware, since Novell hasn't got back to me about it as
promised, they're still working on it....

Is there anything of this nature in your setup?

HTH

....Bill


.

Relevant Pages

  • RE: DENY x REJECT
    ... >>a packetis to look for the ICMP Error Message (Destination ... >firewall dropping a UDP packet and a listening UDP socket can ... >firewall happens to drop those Unreachables. ... Unreachable error message back to the sender. ...
    (Pen-Test)
  • large file copy results in corrupted copies
    ... error message. ... > Comparing file aa.ape and BB.APE ... often appear in the adjacent positions xxxxxxxC xxxxxxxD, ...
    (microsoft.public.windowsxp.general)
  • FileCopy Command Giving "Subscript Out of Range" Error Message
    ... Both the Source and Destination files exist on the same network drive. ... "Subscript Out of Range" error message associated with the FileCopy command. ...
    (microsoft.public.excel.programming)
  • Re: Automate a mail merge in Word 2002 from a macro in Access 2002
    ... > .Destination = wd.wdSendToNewDocument ... Note, however, that the error message could mean there's a problem with ... you may have lost the link to the data source. ... reply in the newsgroup and not by e-mail :-) ...
    (microsoft.public.word.mailmerge.fields)
  • Importing a .DBF file
    ... I'm receiving the following error message: ... Query must have at least one destination ...
    (microsoft.public.access.externaldata)