Has MS fixed Win 2000's file copy logic, which completely aborts onencountering a problem?

February 13, 2008

Has MS fixed Win 2000's file copy logic, which completely aborts onencountering a problem?

I just upgraded from Win 98 to Win 2000 SP4, and I continued to be

sickened by Microsoft's failure to implement reasonable logic for

human users.

In copying a tree structure from one place to another--as millions of

us do regularly in order to, say, back up a USB stick to our hard

drive--Microsoft has failed to implement any error recovery.

In File Explorer, if you highlight a folder, select Copy, go to your

destination, and select Paste, then, if any error occurs during the

copying--for instance, Windows encounters a path that is too long--

then the copy completely aborts with an error message.

You must have the presence of mind to notate the name of the offending

file before you clear the error message.

I don't believe the error message tells you its full path, so you must

then search for it.

You must then do something to the file to make the copy operation

succeed.

Until of course the copy operation fails on ANOTHER file, ad nauseam.

It is the 21st century, and the world's premier software company is

incapable of advancing beyond non-recoverable error logic straight out

of the 1970's.

Do newer versions of Windows recover from copy/move errors, permitting

the operation to go on?

Thanks.

***

February 14, 2008

Re: Has MS fixed Win 2000's file copy logic, which completely abortson encountering a problem?

Re: Has MS fixed Win 2000's file copy logic, which completely abortson encountering a problem?

Learn how to work at the command prompt. The GUI makes things easier

but you cannot include all possible features in it, there has to be a

balance. If you want to use advance features you have to go deeper in

the operating system.

John

baobob@my-deja.com wrote:

> I just upgraded from Win 98 to Win 2000 SP4, and I continued to be

> sickened by Microsoft's failure to implement reasonable logic for

> human users.

>

> In copying a tree structure from one place to another--as millions of

> us do regularly in order to, say, back up a USB stick to our hard

> drive--Microsoft has failed to implement any error recovery.

>

> In File Explorer, if you highlight a folder, select Copy, go to your

> destination, and select Paste, then, if any error occurs during the

> copying--for instance, Windows encounters a path that is too long--

> then the copy completely aborts with an error message.

>

> You must have the presence of mind to notate the name of the offending

> file before you clear the error message.

>

> I don't believe the error message tells you its full path, so you must

> then search for it.

>

> You must then do something to the file to make the copy operation

> succeed.

>

> Until of course the copy operation fails on ANOTHER file, ad nauseam.

>

> It is the 21st century, and the world's premier software company is

> incapable of advancing beyond non-recoverable error logic straight out

> of the 1970's.

>

> Do newer versions of Windows recover from copy/move errors, permitting

> the operation to go on?

>

> Thanks.

>

> ***

February 15, 2008

Re: Has MS fixed Win 2000's file copy logic, which completely aborts on encountering a problem?

Re: Has MS fixed Win 2000's file copy logic, which completely aborts on encountering a problem?

Open a command prompt and type 'xcopy /?'.

Louis

<baobob@my-deja.com> wrote in message

news:b1804920-cd53-4760-b1f0-c5a748bcbfc6@d70g2000hsb.googlegroups.com...