In the beginning, parity was considered reasonable: Measurements
showed that say only one in a million bits went wrong. In that
situation, using parity is not that bad: there is just a 1 chance in a
million that a second bit error occurs in that same byte. You
possibly miss just one error in a million, 999,999 are flagged
correctly. This means that 1 in 1.25e11 bytes is incorrectly flagged
as correct while in reality it is wrong.
However nowadays we know, that it doesn't always work like that. You
might have a 1 in four million chance of a BYTE going wrong, with an
average of 4 bits wrong in that byte (i.e. the byte is completely
random). Still just one bit in a million is wrong, but a completely
random byte has a 50/50 chance of getting the right parity by
accident. So now you're getting 1 byte in 1e6 bytes flagged
as correct while in reality it is wrong.
In the first case, you get one error per day of full-time copying. In
the second case you get 5 errors per second. (Assuming 5Mb per
second).
Roger.
-- ** R.E.Wolff@BitWizard.nl ** +31-15-2137555 ** http://www.BitWizard.nl/ ** Florida -- A 39 year old construction worker woke up this morning when a 109-car freight train drove over him. According to the police the man was drunk. The man himself claims he slipped while walking the dog. 080897