How to obtain Microsoft Windows 8, Dell Drivers, and MicrosoftOffice 2010 for free

G. Morgan wrote :
FromTheRafters wrote:

Jesus H Christ man, you have the patience of a saint. I would have told
him to DHOR a long time ago!

DHOR?

Do His Own Research.

I don't know why he requested that Dustin's answer be technically
acceptable to me. Chances are a satisfactory answer to me will be just
as incomprehensible to him as one acceptable to anyone else.

Yup, a one or two sentence answer to you would require a three page
explanation with cartoon illustrations to him.

I could start out with 7 bit ASCII and parity bits then move from error
detection to error correction by introducing interleaving into the mix
and 'lose' him before even getting to checksums. Those "integrity
checkers" he was reading about are pretty sophisticated by comparison.

I doubt the parity bit method will sink in easily for him. That's why I
encourage him do DHOR so it does not waste my time. He can spend all
afternoon learning it on his own, instead of asking questions that are
easily answered with a little reading/research on his part.

Credit to him, he *did* attempt to educate himself in this instance.
The problem was that there are "integrity checkers" all over the google
results that don't apply to what Dustin said about the reason the
corruption was detected in this instance - and "checksum" is another of
those borrowed terms like "SysOp" and "virus" that people apply to
things even though they don't really (or no longer) fit.

FromTheRafters wrote:
G. Morgan wrote :
FromTheRafters wrote:
Jesus H Christ man, you have the patience of a saint. I would have
told
him to DHOR a long time ago!

DHOR?

Do His Own Research.

I don't know why he requested that Dustin's answer be technically
acceptable to me. Chances are a satisfactory answer to me will be
just as incomprehensible to him as one acceptable to anyone else.

Yup, a one or two sentence answer to you would require a three page
explanation with cartoon illustrations to him.

I could start out with 7 bit ASCII and parity bits then move from
error detection to error correction by introducing interleaving into
the mix and 'lose' him before even getting to checksums. Those
"integrity checkers" he was reading about are pretty sophisticated by
comparison.

I doubt the parity bit method will sink in easily for him. That's why I
encourage him do DHOR so it does not waste my time. He can spend all
afternoon learning it on his own, instead of asking questions that are
easily answered with a little reading/research on his part.

Credit to him, he *did* attempt to educate himself in this instance. The
problem was that there are "integrity checkers" all over the google
results that don't apply to what Dustin said about the reason the
corruption was detected in this instance - and "checksum" is another of
those borrowed terms like "SysOp" and "virus" that people apply to
things even though they don't really (or no longer) fit.

I tip my hat to you, FTR! ;-)

Dustin brought next idea :
FromTheRafters wrote in news:krv2lg$ief$1@dont-
email.me:

Credit to him, he *did* attempt to educate himself in this instance.
The problem was that there are "integrity checkers" all over the google
results that don't apply to what Dustin said about the reason the
corruption was detected in this instance - and "checksum" is another of
those borrowed terms like "SysOp" and "virus" that people apply to
things even though they don't really (or no longer) fit.

Although true, it did fail it's own internal integrity check; I also
mentioned the PE header. The specific section that failed first was the
internal filesize counter. [g] Had BD bothered to google it instead of the
generic phrase, integrity checker; he would have gotten the results he was
looking for. So the credit you give him is null and void here.

It least he *did* try.

It doesn't really matter, as soon as the moronic twit googles for the PE
header, he'll instantly be way beyond lost.

Yep.

================================================== ==================
File might be truncated
The file is smaller than the PE section table indicates (149589504
bytes appear to be missing). Are you sure you have the complete sample?

PE checksum does not match content
The checksum calculated for this file (04A0C700) does not match the
checksum stored inside the PE header (0D8B2734).
================================================== ==================