Benjamin Scott wrote:
>
> But the point is, it doesn't try to hide the fact that something went
> wrong. If Microsoft were to write that error message, you would see:
>
> $ rmdir foo
> The command did not complete successfully. Contact your system
> administrator if you need help. (Error code 0x0F3D97B4)
>
> (And you can bet dollars to donuts that error code wouldn't be documented
> anywhere.)
>
Unfortunately, MS didn't "innovate" this style of error messages. I
was working with mainframes early in my career. One of my people got
a wonderful error message on the order of "error 23xfoo". He looked
it up in his programming book. It said: "error 23xfoo, see system
administrator," so he turned to me to grab the sysadmin book behind
me. We looked up the error. The sysadmin book said: "error 23xfoo,
fix problem." That was it. Total description, including recommended
action.
Its nice to see standard MS innovation in action.
--
jeff smith
---------------------------------------------------------------------------------
thought for the day: In Ohio, if you ignore an orator on Decoration
day to such an extent as
to publicly play croquet or pitch horseshoes within one mile of the
speaker's stand, you can be fined $25.00.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
