How to set "Verify On" at XP startup ?

[Hari Hari Mau]

In Win98, an "verify on" entry inside the autoexec.bat batch file
ensures that each and every copy operation is being done by bit-by-bit
verification.

I am looking for a way to do such a thing on XP.

I tried setting up a script at the startup/shutdown script, hoping
that when the machine is booted up, the "verify on" option would be
loaded. Apparently what I did failed miserably.

So I am here looking for help.

Can any of you Gurus tell me how to automate this "verify on" thing
for XP, so that every time the PC is booted, XP loads in the "verify
on" thing automatically, resulting in each and every copy / move
operation are verified bit-by-bit ?

Would be very appreciative of any of your suggestion and/or opinion.

Thanks !

 

[John John (MVP)]

Explorer does this automatically. If you want to use this when you copy
from the Command Prompt you can use the appropriate switch in your
command syntax.

John

 

[Don Phillipson]

In Win98, an "verify on" entry inside the autoexec.bat batch file
ensures that each and every copy operation is being done by bit-by-bit
verification.
I am looking for a way to do such a thing on XP.

You may have apprehended thiings backwards.
1. This is a "parameter" of the COPY utility built into
operating systems, which may or may not be available
in any particular version of MS-DOS (as Win98) or its
avatars (e.g. XP: both have this function.)
2. Win98 may use AUTOEXEC.BAT at boot but does
not require it (as Win95 did.)
3. AUTOEXEC.BAT never requires any COPY functions
with or without /V

Can any of you Gurus tell me how to automate this "verify on" thing
for XP, so that every time the PC is booted, XP loads in the "verify
on" thing automatically, resulting in each and every copy / move
operation are verified bit-by-bit ?

Better repost in a WiinXP NG explaining which COPY
processes you want to run at boot.

 

[philo]

In Win98, an "verify on" entry inside the autoexec.bat batch file
ensures that each and every copy operation is being done by bit-by-bit
verification.

I am looking for a way to do such a thing on XP.

I tried setting up a script at the startup/shutdown script, hoping
that when the machine is booted up, the "verify on" option would be
loaded. Apparently what I did failed miserably.

So I am here looking for help.

Can any of you Gurus tell me how to automate this "verify on" thing
for XP, so that every time the PC is booted, XP loads in the "verify
on" thing automatically, resulting in each and every copy / move
operation are verified bit-by-bit ?

Would be very appreciative of any of your suggestion and/or opinion.

Thanks !

First off, you've posted to a Win98 newsgroup...
you should have kept your question on an XP group.

However, the "verify" option on XP

is simply invoked with the /V switch


If you are looking for a more robust "copy" function
I suggest you use robocopy from the XP resource kit

 

[John Holmes]

Hari Hari Mau "contributed" in 24hoursupport.helpdesk:

In Win98, an "verify on" entry inside the autoexec.bat batch file
ensures that each and every copy operation is being done by bit-by-bit
verification.

I am looking for a way to do such a thing on XP.

I tried setting up a script at the startup/shutdown script, hoping
that when the machine is booted up, the "verify on" option would be
loaded. Apparently what I did failed miserably.

So I am here looking for help.

Can any of you Gurus tell me how to automate this "verify on" thing
for XP, so that every time the PC is booted, XP loads in the "verify
on" thing automatically, resulting in each and every copy / move
operation are verified bit-by-bit ?

Would be very appreciative of any of your suggestion and/or opinion.

Thanks !

Windows Explorer will always copy with verify ON

 

[Scott Seligman]

Windows Explorer will always copy with verify ON

No it doesn't (at least not in Vista, I didn't bother to verify this
with XP).

 

[John John (MVP)]

No it doesn't (at least not in Vista, I didn't bother to verify this
with XP).

If you didn't verify with XP then why are you bothering replying to an
XP group? Windows Explorer always copies with verify on and I would be
surprised if Vista did this any differently.

John

 

[John Holmes]

Scott Seligman "contributed" in 24hoursupport.helpdesk:

No it doesn't (at least not in Vista, I didn't bother to verify this
with XP).

If you didn't bother to verify this with XP, your own verify is OFF, eh?

Anyway, the OP was asking about XP, where Windows Explorer copies with
verify ON by default. Nobody asked about Vista here so your reply is less
then useless.

 

[Scott Seligman]

If you didn't verify with XP then why are you bothering replying to an
XP group? Windows Explorer always copies with verify on and I would be
surprised if Vista did this any differently.

No it doesn't. I just verified this with a stock XP installation.
Explorer didn't very the copy after it was completed, so you're wrong.

 

[John John (MVP)]

No it doesn't. I just verified this with a stock XP installation.
Explorer didn't very the copy after it was completed, so you're wrong.

How exactly did you verify if Explorer.exe verified its file copy?

John

 

[Scott Seligman]

How exactly did you verify if Explorer.exe verified its file copy?

I ran Process Monitor while the copy was going and looked to see if
Explorer tried to read the destination file or only wrote to it. (It
only wrote to it)

 

[chuckcar]

You may have apprehended thiings backwards.
1. This is a "parameter" of the COPY utility built into
operating systems, which may or may not be available
in any particular version of MS-DOS (as Win98) or its
avatars (e.g. XP: both have this function.)
2. Win98 may use AUTOEXEC.BAT at boot but does
not require it (as Win95 did.)
3. AUTOEXEC.BAT never requires any COPY functions
with or without /V


Better repost in a WiinXP NG explaining which COPY
processes you want to run at boot.

If you don't know or can't answer, don't bother replying.

 

[chuckcar]

In Win98, an "verify on" entry inside the autoexec.bat batch file
ensures that each and every copy operation is being done by bit-by-bit
verification.

I am looking for a way to do such a thing on XP.

I tried setting up a script at the startup/shutdown script, hoping
that when the machine is booted up, the "verify on" option would be
loaded. Apparently what I did failed miserably.

So I am here looking for help.

Can any of you Gurus tell me how to automate this "verify on" thing
for XP, so that every time the PC is booted, XP loads in the "verify
on" thing automatically, resulting in each and every copy / move
operation are verified bit-by-bit ?

Would be very appreciative of any of your suggestion and/or opinion.

Found this link:

http://www.computerhope.com/verifyhl.htm

The exact same method is used in *every* MS OS since MSDOS. That is, just
put a line:

verify on

in a file called autoexec.bat in the root directory of your C: drive and
enable autoexcec.bat in msconfig.

 

[Pat]

If you didn't verify with XP then why are you bothering replying to an
XP group? Windows Explorer always copies with verify on and I would be
surprised if Vista did this any differently.

Instead of answering bullshit, remove this stupid and noob "MVP" in your
name; we are not kids.
MVP program is the most laughable shit on the net, full of complete
newbies like you who even don't understand they are suckers (I just
laughed when they wanted to put me in this shit...) to replace tech
support budget reductions.
Pathetic..

 

[John John (MVP)]

I ran Process Monitor while the copy was going and looked to see if
Explorer tried to read the destination file or only wrote to it. (It
only wrote to it)

So then we would have to conclude that other than the copy command none
of the other native file copy commands are capable of verifying the copy
operation?

I'm finding this a bit hard to believe, especially when Microsoft tells
us that the /v switch is ignored with Xcopy because the verify operation
is inherent to the operating system.

John

 

[Scott Seligman]

So then we would have to conclude that other than the copy command none
of the other native file copy commands are capable of verifying the
copy operation?

No. I'm just saying by default Explorer doesn't verify the contents of
the copy operation by default. For all I know there's some way to enable
that behavior.

I'm finding this a bit hard to believe, especially when Microsoft
tells us that the /v switch is ignored with Xcopy because the verify
operation is inherent to the operating system.

Where do they say that? /V in Xcopy isn't documented as verifying the
file contents, but rather verifying the file size, something it in fact
does if you specify the /V option.

 

[Scott Seligman]

files are identical to the source files". And (to
respond to another post in this thread) this
parameter works (or worked in v5.0) in exactly the
same way for Xcopy.

In Xcopy on XP and Vista, all /V does is verify the target file size.
It's incorrectly documented in XP, but in Vista the documentation has
changed to the following:

/V Verifies the size of each new file.

 

[Jeff Richards]

The reference you are using is wrong.

Please see:
http://support.microsoft.com/kb/126457
VERIFY ON, COPY /V, XCOPY /V Commands Do Not Compare Data

 

[John John (MVP)]

No. I'm just saying by default Explorer doesn't verify the contents of
the copy operation by default. For all I know there's some way to enable
that behavior.

I have never heard of being able to change Explorer's copy behaviour.
Explorer.exe uses the same file copy functions as the other copy
utilities, it would be interesting to know how these functions verify
their copy operations.

Where do they say that? /V in Xcopy isn't documented as verifying the
file contents, but rather verifying the file size, something it in fact
does if you specify the /V option.

Look in the Windows Help files. The Xcopy /v option is ignored by
Windows NT/2000/XP, it does nothing, it it is accepted only for
compatibility with MS-DOS. The Windows XP help files do not elaborate
any further but the Windows 2000 help files says:

" /v - Verifies each file as it is written to the destination file to
make sure that the destination files are identical to the source files.
This switch is ignored because the functionality is inherent to the
Windows 2000 operating system. The switch is accepted only for
compatibility with previous versions of MS-DOS."

By the same token, the obsolete MS-DOS VERIFY command is also ignored by
NT operating systems. This information is also present in Windows NT
4.0 documentation, I find it hard to believe that the same would not
apply to Windows XP, or for that matter Vista.

As it is, if we are to accept that Explorer doesn't verify its copy
operations, the only native tool that can verify its copy operations
would be the internal Copy command, there again I find it hard to
believe that any of the NT versions would simply do away with this for
all but the internal copy command.

John

 

[Scott Seligman]

Look in the Windows Help files. The Xcopy /v option is ignored by
Windows NT/2000/XP, it does nothing, it it is accepted only for
compatibility with MS-DOS. The Windows XP help files do not elaborate
any further but the Windows 2000 help files says:

In Vista, /V for Xcopy is documented as:

/V Verifies the size of each new file.

Something it in fact does. (Well, it calls the right command after
the copy is completed only if you specify /V, I didn't dig deep enough to
verify it does anything with the call).

/V, at least according to the command line help, is documented in XP
as:

/V Verifies each new file.

Though, even with that wording it behaves the same was in XP as it
does in Vista. It's just calling an API presumably to get the file
size, not the sequence it would need to call to verify its contents.

" /v - Verifies each file as it is written to the destination file to
make sure that the destination files are identical to the source files.
This switch is ignored because the functionality is inherent to the
Windows 2000 operating system. The switch is accepted only for
compatibility with previous versions of MS-DOS."

Interesting. The online help and the command line help don't agree.