Copy file utility that ignores errors

[Southridge]

Hi,
It's so frustrating when you are trying to copy a large folder, and windows hits a file that it cannot copy. Rather than allowing you to continue, windows merely terminates the entire copy request, leaving you with a partial attempt at the job. I know that xcopy has the /c option to continue on error, but I'd like to be able to do the same from an explorer type window. Does anyone have a solution for this, or know of a good 3rd party utility that can do this?

thank you.

 

[wolluf]

Servant Salamander (current version is 30 day shareware - but old versions available from site (

http://www.altap.cz)

are free - and have same copy function that prompts when it hits any situation that has a choice).

I use this all the time (much better than explorer)

http://netez.com/2xExplorer/

may have this too (freeware) - but I doubt it (haven't used it for a while).

 

[Southridge]

Thanx Wolluf, i'll give it a shot.

 

[jurgen36]

Try Total Commander or Wincommander. You find full functional downloads on many websites. It can do just what you ask for and much much more. Regards

Jurgen

 

[bcastner]

I solved a similar large copy problem by a careful study of the command line switches of XXcopy, free for non-commercial use:

http://www.xxcopy.com/#toc

Note: you will not be able to do this sort of recovery from error operation under Windows Explorer.

 

[linney]

What would happen if you were to stick it in your email program as an attachment but not send any email. Instead you might be able to save the (temporary) attachment to another folder on your system.

What about zipping the file and copying as a zip file?

Would you also get the error if you were to use the "Sendto" function instead of copy or move?

Just some useless ideas that you are welcome to ignore.

 

[bcastner]

sigh.

This linney fellow is testing my marginal hold on sanity.

I am still recovering from his suggestion last week that one could create zero length files under Windows XP with a Start, Run banana sequence: thread779-758177

No matter what you do under the Shell there is no recovery for a logical or hard file error under Explorer. This will require third-party tools with the exception (likely unsatisfactory) that you can use under CMD the "/C" switch in the case of a network error.

While I have not in fact tested the notion you can email yourself a volume of several gigabytes (note: you cannot pass this through most email servers) fundamentally the process will call on the native Explorer facilities and will fail.

You need to use a third-party utility. My suggestion of the freeware xxcopy is reasonable.

 

[linney]

Hey bill,

First of all I qualified the ideas as "useless" and "welcome to try". Secondly there is no need to email anything anywhere (in a standalone situation) just save the attachment in your destination folder.

And go and get your own banana to play with.

Directory of C:\PROGRA~1\ATTACK\TDS-3

03/02/2004 03:00 PM <DIR> .
03/02/2004 03:00 PM <DIR> ..
18/12/2003 02:55 PM 78,848 advscan.dll
03/02/2004 02:58 PM 0 banana
19/09/2003 12:12 PM <DIR> Bars
25/08/2000 06:54 PM 9 beep1.txt
28/08/2000 04:38 PM 19 beep2.txt
22/01/2001 04:52 PM 80 beep3.txt
03/02/2004 03:00 PM 0 bill
03/02/2004 03:00 PM 0 bill castner
19/09/2003 12:12 PM <DIR> Config

 

[bcastner]

Linney,

I have stated this as politely as I can. The problem you see with zero length files has to do with TD3. It is not a Windows issue.

I can &quot;linney&quot;, &quot;aussie_melonhead&quot; all I want and not duplicate the issue. I honestly believe it has to do with TD3's ambitous efforts to handle streams. (Streams are an obscure feature of NTFS file systems, and fortunately are rarely used to date by malware exploits).

Do you not find it at least a bit curious that these zero length files always end up in the TD3 directory???

I read you earlier links on the issue, and found them true believer hogwash. It is not true that if Windows XP is called with a run or CMD line (and cannot find the file reference) it creates a zero length file. Please. As I mentioned earlier the only circumstance when this would occur is if a LZ compressed file was called from a CAB and not there. And it certainly would not conveniently place it always in the TD3 folder.

I must admit a bias. I will not take Windows Shell advice from the AUS/AUK community without a fight until they return the Cup to its rightful place in the USA.