Trying to recall where a checksum setting is

[Guest Pete Puma]

Once in XP I came across a setting that allowed the data copied or written to

be "checked" or verified something like that in some general preference box.

Even at the risk of slowing down any copying function, I would prefer this.

 

Can any one help me with this--sorry to be so vague...

 

1) I was trying to remember where it was

2) I wondered how it was performing the parity check--but I guess it was

doing checksums of some type

 

Thanks for reading

[Guest GHalleck]

Re: Trying to recall where a checksum setting is

 

 

Pete Puma wrote:

> Once in XP I came across a setting that allowed the data copied or written to

> be "checked" or verified something like that in some general preference box.

> Even at the risk of slowing down any copying function, I would prefer this.

>

> Can any one help me with this--sorry to be so vague...

>

> 1) I was trying to remember where it was

> 2) I wondered how it was performing the parity check--but I guess it was

> doing checksums of some type

>

> Thanks for reading

 

Thinking of CRC, Cyclic Redundancy Check? There are applications that

provide this additional feature, such as disk-imaging software.

[Guest HeyBub]

Re: Trying to recall where a checksum setting is

 

Pete Puma wrote:

> Once in XP I came across a setting that allowed the data copied or

> written to be "checked" or verified something like that in some

> general preference box. Even at the risk of slowing down any copying

> function, I would prefer this.

>

> Can any one help me with this--sorry to be so vague...

>

> 1) I was trying to remember where it was

> 2) I wondered how it was performing the parity check--but I guess it

> was doing checksums of some type

>

> Thanks for reading

 

You may be thinking of the "Verify" option of the COPY command (COPY X Y

/V).

 

A better techinque is the COMPARE command after finishing the copy (COMP

Xfile Yfile).

[Guest Pete Puma]

Re: Trying to recall where a checksum setting is

 

HeyBub wrote:

> Pete Puma wrote:

>> Once in XP I came across a setting that allowed the data copied or

>> written to be "checked" or verified something like that in some

>> general preference box. Even at the risk of slowing down any copying

>> function, I would prefer this.

>>

>> Can any one help me with this--sorry to be so vague...

>>

>> 1) I was trying to remember where it was

>> 2) I wondered how it was performing the parity check--but I guess it

>> was doing checksums of some type

>>

>> Thanks for reading

>

> You may be thinking of the "Verify" option of the COPY command (COPY X Y

> /V).

>

> A better techinque is the COMPARE command after finishing the copy (COMP

> Xfile Yfile).

 

Not sure WHAT it did, but there was a checkbox SOMEWHERE in XP during one of

my setups--I'll find it if I have to reenact the 3 Stooges as plumbers.

I remember years ago that all computers sold to government contractors and

military-related desktops had to have 9-bit--as opposed to standard 8-bit,

RAM installed, the last bit being used for parity checking (over my head a

bit, but I get the concept). This was chiefly to prevent bad data in the

delivered files that the gov paid for.

I recall RAM companies selling them in either 8- or 9-bit versions when they

listed their ads.

Back to my magic button: if I can locate that, I will research it on MS to

find out precisely what it does and post back. What I'm ultimately looking

to do is keep the direcotry and copying function stable without the system's

nodes and indexes getting whacky. If you control that, you could run XP for

another 10 years. I hope so.

 

--

Cynic, n.:

One who looks through rose-colored glasses with a jaundiced

eye.