Is Explorer copy the same as "copy /v" (Verify)?

>From my experience, the behaviour of "copy /v" seems to be that once
the file is copied, it verifies (checksum?) whether it copied ok, and
if verification fails, it'll recopy or correct it. However it's
implemented, the end result is the copy you get is guaranteed to be
identical as the source.

Am I right in saying that without the /v option, you can end up with a
corrupted file?

When you copy a file in Windows Explorer (drag and drop or Ctrl-c/x),
which behaviour do you get?

Thanks!
iDon

Copy /v merely checks that it can be read, not that it is the same.

--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/ha...he_ga.html#more
=================================================
<idon.wong@gmail.com> wrote in message news:1133830377.129401.16680@o13g2000cwo.googlegroups.com...
> >From my experience, the behaviour of "copy /v" seems to be that once
> the file is copied, it verifies (checksum?) whether it copied ok, and
> if verification fails, it'll recopy or correct it. However it's
> implemented, the end result is the copy you get is guaranteed to be
> identical as the source.
>
> Am I right in saying that without the /v option, you can end up with a
> corrupted file?
>
> When you copy a file in Windows Explorer (drag and drop or Ctrl-c/x),
> which behaviour do you get?
>
> Thanks!
> iDon
>