View Single Post
  #24  
Old March 12th 04, 07:08 PM
SpongeBob
external usenet poster
 
Posts: n/a
Default


"CBFalconer" wrote in message
...
SpongeBob wrote:
wrote

... snip ...

There are three scenarios I am thinking about:

(1) Copying a partition from one hard drive on one IDE cable to
another hard drive on a different IDE cable.

(2) Copying a partition from one hard drive to another which is on
the same IDE cable.

(3) Copying one partition to another on the same hard drive.

How much effect would "over-set" memory have on these situations?

Do the answers to any of the above three scenarios change if the
copying of large amounts of data files is done from within WinXP?
Personally, I would guess that it is more likely that motherboard
memory comes into play if Windows is involved.


How about something easy...Loosen your memory timings.(CAS3)...
perform the copy...then tighten them back up...Voila! No corruption!


However the partition you want to copy has already been messed up
by the memory faults, in ways that may not show up for months. If
you have ECC installed and active you might get away with it.
Copying corrupt data does not repair it.

--
Chuck F ) )
Available for consulting/temporary embedded and systems.
http://cbfalconer.home.att.net USE worldnet address!



Well...from what was written...the question was theoretical...data
corruption has not occurred, there has been no evidence of system
instability, and he has not copied anything yet. High quality memory can
often handle tighter timings without ill effect. Test with memtest86 and
Prime95 for a few days to be sure of stability. If not...loosen the timings
and copy away! To answer the question...tighter memory timings may or may
not affect data transfer...It all depends on your memory and your system.