Hot to keep file copy from stopping?

[John Schmidt]

This has driven me crazy ever since the beginning of Windows Explorer.

Why the heck do copy operations force you to cancel when finding even one
"access denied" file??? How can you get Windows to skip that one and
continue copying the rest???

I need to move about 50 gigs of files to a new drive, and every now and then
it comes across one of these, forcing me to track it down, then start the
operation all over again, since you have no idea where the copy operation
left off. This is ridiculous!!!! There were only 16 minutes to go out of
over 4 hours, and this is the 3rd time I've had to start over!! (I thought
I'd fixed all the files, but a new one just popped up.)

How can I keep these few files from aborting file copy operations??? I can't
believe that Explorer thinks because you find even one file like this, it
cancels the whole operation. There must be a way around this.

Thanks for any suggestions.

John

 

[GTS]

It's a matter of inept programming. I suggest using xcopy instead. Here's
a batch file I use when I want to ensure that anything and everything
possible is copied. Run xcopy /? in a command prompt to see meaning of the
switches. The /c switch is particularly significant - Continues copying
even if errors occur.

:: xc-all.cmd 09/02/02 Mon 6:39 PM
:: these switches ensure hidden, rdonly, empty dirs, etc all copy.

xcopy /d /s /e /h /r /c /k /y %1 %2

 

[John Schmidt]

Thanks - I was wondering if xcopy would work.

I still can't believe MS programmed Explorer to work this way, to just
cancel the operation instead of giving the option to skip...

John

 

[cquirke (MVP Windows shell/user)]

On Mon, 17 Oct 2005 06:06:46 -0700, "John Schmidt"

This has driven me crazy ever since the beginning of Windows Explorer.

Yep - me too.

Why the heck do copy operations force you to cancel when finding even one
"access denied" file??? How can you get Windows to skip that one and
continue copying the rest???

No-one at MS thought of that, just as no-one thought beyond successive
ad-hoc "x is read-only", "y is a program" nags.

There's no best-choice auto-behavior here, so what you want is a
dialog that lets you set anticipatory behaviors for the operation you
are doing. Saving these as "always use..." would be dangerous tho.

For example, the file operations dialog could have a "Behavior..."
button next to the usual "Cancel". When clicked, a dialog pops up in
which you can preset whether to abort on errors, and what to do when
various situations are encountered that current prompt nags. If you
populate this dialog, then a summary of what happened appears when the
operation is completed.

I need to move about 50 gigs of files to a new drive, and every now and then
it comes across one of these, forcing me to track it down, then start the
operation all over again, since you have no idea where the copy operation
left off. This is ridiculous!!!! There were only 16 minutes to go out of
over 4 hours, and this is the 3rd time I've had to start over!!

Yup. My SOP there is to:
- note which "folder" (or file) was being copied
- deselect all completed items as well as the "problem" one
- repeat the remainder of the copy operation
- drill into the failed folder and repeat within there
- when done, highlight all, Properties, in both windows
- if folder, file and byte counts not the same, chase up

How to chase up; select matching blocks of content in source and
destination panes, and do the Properties thing, compare. If same,
move on to next block, else highlight half of what you selected
previously and repeat. If same, check other half; else check half of
the half you had selected etc. until you drill down to the bad file.

It's annoying that the file operations dialog shows only the last
folder name in the file spec, instead of the full path. It's also
annoying that MS's in-house testing seems to be done with trivial file
loads that hardly push the scalability envelope.

Honestlty, I've have folks tell me with a straight face that "copying
thousands of files is an unusual 'geek' activity for which you need
special tools; Windows is for 'normal' people". Pathetic.

See http://cquirke.blogspot.com/ right back to 23 March 2005.

How can I keep these few files from aborting file copy operations???

Skip them and come back to them later. Usually you will find they are
corrupted at the disk or file system level, and that's why they can't
copy - insane start cluster or size, invalid characters in name, etc.

I can't believe that Explorer thinks because you find even one file
like this, it cancels the whole operation.

Think about it - there are contexts when that is exactly what you'd
want. That's why one needs more options and UI control.

There must be a way around this.

FoxIt (or is that RoadKill?) has a tool called "unstoppable copy", but
I haven't logged enough mileage to trust it as yet.

 

[John Schmidt]

Well, I've determined I can use our Veritas backup software to first make a
backup of the specific data I want copied, then restore it to the new
location, (backup is disk based here). While slower than a simple copy
operation, the backup software is able to back up and restore *all* the
files to the new location, with no interaction whatsoever, regardless of
security, read-only, etc..

I really do like your "options" idea. It's so frustrating that software
companies go out of their way to try giving us the latest and greatest, but
can't provide for basic functionality missing for years...

John