Copying files without halting on bad ones

  • Thread starter Thread starter yawnmoth
  • Start date Start date
Y

yawnmoth

I'm trying to copy some files (about 3,000) from a computer whose hard
drive is failing to another computer and am having some difficulty.
Whenver a bad file would be copied, the entire copy process stops and
the following error is displayed:

Cannot copy (filename): Data error (cyclic redundancy check).

Is there some way to copy the files in such a way that the bad files
don't halt the copy process? If possible, I'd also like it if a list
of the bad files could be made.
 
yawnmoth said:
I'm trying to copy some files (about 3,000) from a computer whose hard
drive is failing to another computer and am having some difficulty.
Whenver a bad file would be copied, the entire copy process stops and
the following error is displayed:

Cannot copy (filename): Data error (cyclic redundancy check).

Is there some way to copy the files in such a way that the bad files
don't halt the copy process? If possible, I'd also like it if a list
of the bad files could be made.
Hi
XCOPY /C
the c switch stops the program halting on errors

Chas
 
Yeh, something I would like to know also.
Would you do a XCOPY /C from start/run cmd within windows? any idea how you
would copy certian files from folders or even the whole folder using XCOPY?
 
Don't run xcopy from Start/Run. If you do then you deprive yourself
of all feedback provided by xcopy.exe. Start a Command Prompt
instead (Start / Run / cmd {OK}), then run xcopy.exe.

While under the Command Prompt, type xcopy /? to see how
the command works and what switches are available.
 
Chas said:
Hi
XCOPY /C
the c switch stops the program halting on errors

That sorta seems to help. Unfortunately, I still can't create a list
of the bad files.

I can't just output it to the screen because, for one, I'd probably
miss something if I was trying to scan it by hand, and for two, I
probably wouldn't be able to see a list of all the files that hadn't
been copied, anyway.

Redirecting it to a file via "xcopy {params} > c:\log.txt" doesn't
capture the "File creation error - Data error (cyclic redundany
check)." stuff, leaving me with a big list of files that may or may not
have been copied over.

I've started a new thread on capturing error messages in text files,
but maybe there's another solution that I'm not aware of that wouldn't
involve that? Maybe the files listed are only those that did
successfully copy?
 
yawnmoth said:
That sorta seems to help. Unfortunately, I still can't create a list
of the bad files.

I can't just output it to the screen because, for one, I'd probably
miss something if I was trying to scan it by hand, and for two, I
probably wouldn't be able to see a list of all the files that hadn't
been copied, anyway.

Redirecting it to a file via "xcopy {params} > c:\log.txt" doesn't
capture the "File creation error - Data error (cyclic redundany
check)." stuff, leaving me with a big list of files that may or may not
have been copied over.

I've started a new thread on capturing error messages in text files,
but maybe there's another solution that I'm not aware of that wouldn't
involve that? Maybe the files listed are only those that did
successfully copy?

Use xxcopy.exe (downloadable from various sites) with the same
switches as xcopy.exe, and redirect its output to log files:

xxcopy ... . .. ... 1> c:\copy.log 2>c:\copy.err

You will find that its error reporting features are better than those
of xcopy.exe.
 
Back
Top