Archived from groups: microsoft.public.windowsxp.basics (
More info?)
Pop, not all questions here are from home users. Some people are dealing
with small business or church data files and such. They need to correct
problems with the data before trying to proceed. And yes, some data copying
operations can allow continued copying around a bad file.
--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Pop" <nobody@devnull.spamcop.net> wrote in message
news:uGkJdhCJFHA.3484@TK2MSFTNGP12.phx.gbl...
> Not even if it was JUST ONE say, wedding favorite wedding photograph
> among, maybe a couple hundred? You wouldn't want ANY of them?
>
> My GOD, you people are thick! Does MVP = something I don't know about, or
> could you all be that thick?! Only one poster all the way thru here so
> far bothered to know what the OP said. The rest of you appear to be
> quacks!
> And I just got thru defending this ng to a newbie, too. Most of you are
> turning out to be warts on the ass of progress, you know that?
>
> Pop
>
> "Colin Barnhorst" <colinbarharst(nojunk)@msn.com> wrote in message
> news:%232J4JeAJFHA.2736@TK2MSFTNGP09.phx.gbl...
>> That might be cool with mp3 files, but I sure wouldn't want to let data
>> files keep copying if one of them was a bad file.
>>
>> --
>> Colin Barnhorst [MVP Windows - Virtual Machine]
>> (Reply to the group only unless otherwise requested)
>> "(ProteanThread)" <sysop@rtdos.com> wrote in message
>> news:1110302080.37be98b3e2fde18878a297a9bd293af3@teranews...
>>> "Mark Stafford" <Mark Stafford@discussions.microsoft.com> wrote in
>>> message
>>> news:05C0A81C-EA7A-4F64-9BD4-F7E1D1CA9A0B@microsoft.com...
>>>> To elaborate on what Colin said, if there is an error with Windows
>>> Explorer
>>>> copying a file, one of two things is probably happening: 1) Windows
>>> Explorer
>>>> (which provides your entire desktop experience) is corrupted, which
>>>> would
>>>> manifest itself in many more areas than simply file copy procedures.
>>>> 2)
>>> The
>>>> file(s) you are attempting to copy are corrupted or in use, which is
>>>> much
>>>> more of an issue. One example of this might be attempting to copy a
>>>> user
>>>> profile that is currently in use. Explorer will throw back a message
>>>> that
>>>> says that ntuser.dat is locked by an unspecified process. To
>>>> circumvent
>>> this
>>>> type of error, either find a way to stop using the file(s) (in my
>>>> example,
>>> by
>>>> rebooting and logging on as a different user) or attempt to use a
>>>> program
>>>> like Handle to identify and/or kill the process that is using the file.
>>> If
>>>> the file is corrupted so badly that Windows Explorer can't copy it, you
>>> might
>>>> be better off pursuing another solution entirely.
>>>
>>>
>>> But I noticed that (and this issue bugs me) it'll stop copying when it
>>> finds
>>> an error in one file in a group of file and therefore will stop the
>>> copying
>>> process even the files after that are good to copy.
>>>
>>>
>>>
>>
>>
>
>
Facebook
Twitter
Instagram