How to set "Verify On" at XP startup ?

The documentation being used as a reference is incorrect (or at least
misleading).
http://support.microsoft.com/kb/126457
--
Jeff Richards
MS MVP (Windows - Shell/User)
"mm" wrote in message
...
On Sat, 6 Dec 2008 09:17:53 -0500, "Don Phillipson"
wrote:

snip

So if one sets Verify On within Autoexec, does that effect copies done
through Win98? Or are the DOS and Windows environments unrelated on
something like that.

In message , Don Phillipson
writes:
"Hari Hari Mau" wrote in message
...

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.)

Indeed: it runs it if it is there.

3. AUTOEXEC.BAT never requires any COPY functions
with or without /V

However, it is quite possible that a system variable can be set which
affects how all subsequent copy operations behave; that is what the OP
wants. I do not know the copy command, but for example the dir command
can be set to always list in certain orders by setting the DIRCMD
variable. In fact I've just checked, and there is an (optional) COPYCMD
variable, though it may not include the /v option ("copy /?" suggests it
may only be able to hold the /Y option, which is to do with
overwriting). The "verify on" command the OP mentions seems to set a
toggle that might be a similar thing.

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.

I agree he's be better asking in an XP newsgroup. But he doesn't want to
run any COPY processes *at boot* - he wants to invoke something at boot
that affects how all _subsequent_ copy (and move) operations operate.

Oops - he _is_ posting to rather a lot of newsgroups. I've left them all
in for now, but it would probably be better to remove the 98 one at the
very least.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL(+++)IS-P--Ch+(p)Ar+T[?]H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **

"Does Barbie come with Ken?"
"Barbie comes with G.I. Joe. She fakes it with Ken." - anonymous

VERIFY ON is a command that is frequently used within AUTOEXEC.BAT. It does
not require AUTOEXEC.BAT to use a COPY command in order to function, but
remains effective until changed.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Don Phillipson" wrote in message
...
"Hari Hari Mau" wrote in message
...

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.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

"Don Phillipson" wrote in
:

"Hari Hari Mau" wrote in message
...

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.

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


--
(setq (chuck nil) car(chuck) )

Hari Hari Mau wrote in
:

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.

--
(setq (chuck nil) car(chuck) )

Scott Seligman wrote:
"John John (MVP)" wrote:

Scott Seligman wrote:


"John John (MVP)" wrote:


Scott Seligman wrote:



John Holmes wrote:



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).

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.

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)

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

"John John (MVP)" wrote:
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 scott at firstname and michelle dot net ---------
When the gods choose to punish us, they merely answer our prayers.
-- Oscar Wilde

In message , John Holmes
writes:
[]
Windows Explorer will always copy with verify ON

Quite apart from the doubts that others have expressed over the above
statement, do you mean just verify-that-the-written-file-can-be-read, or
verify-that-the-written-file-matches-the-source-file? (Someone in this
thread has pointed us to a MSKB article which says that the /v switch -
and verify on command - only does the first sort of verify.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL(+++)IS-P--Ch+(p)Ar+T[?]H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **

"Does Barbie come with Ken?"
"Barbie comes with G.I. Joe. She fakes it with Ken." - anonymous

On Sun, 7 Dec 2008 13:05:39 +0000, "J. P. Gilliver
(John)" wrote:

In message , John Holmes
writes:
[]
Windows Explorer will always copy with verify ON

Quite apart from the doubts that others have expressed over the above
statement, do you mean just verify-that-the-written-file-can-be-read, or
verify-that-the-written-file-matches-the-source-file? (Someone in this
thread has pointed us to a MSKB article which says that the /v switch -
and verify on command - only does the first sort of verify.)

Apparently that post didn't make it to all the NGs
in the list. But if the claimed behavior is true,
it would indicate a change in the meaning of the
term "Verify" by Microsoft. Old DOS versions (I
have the v5.0 manual open in front of me) clearly
state that the /v switch or Verify On command
"Verifies each file as it is written to the
destination file to make sure that the destination
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.

Best regards,


Bob Masta

DAQARTA v4.51
Data AcQuisition And Real-Time Analysis
www.daqarta.com
Scope, Spectrum, Spectrogram, Sound Level Meter
FREE Signal Generator
Science with your sound card!

wrote:
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.


--
--------- Scott Seligman scott at firstname and michelle dot net ---------
The avalanche has already started. It is too late for the pebbles to
vote. -- Ambassador Kosh Naranek in Babylon 5:"Believers"