HP3000-L Archives

February 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James R. Alton" <[log in to unmask]>
Reply To:
James R. Alton
Date:
Thu, 1 Feb 1996 14:16:44 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
On Thu, 1 Feb 1996, Denys Beauchemin wrote:
 
> In a message dated 96-02-01 11:30:38 EST, [log in to unmask] (Bruce Toback)
> writes:
>
> >I'm curious now... what constitutes a WELL-timed hardware problem? :-)
> >
> >-- Bruce
>
> That's easy.  It is a hardware problem that manifests itself only during a
> regular maintenance inspection by an ultra-qualified CE equiped with all the
> diagnostic equiment, which can be repaired without any tools, by merely
> swapping a board (not inside the system so it does not have to be opened up)
> pulled from an extensive spare part kit brought along by the aforementioned
> CE.
 
 
 Or... to lower the level of the conversation... hardware problems could
be thought of as being the inverse of sex.
 
 There is no such thing as a good hardware failure, just some are better
than others.
 
 A bad failure happening at fiscal year end, a less bad failure happening
at month end.
 
 ... hold on....
 
 I just thought of a good failure....
 
 The one that occurs at 3:00 pm on a sunny Friday afternoon sometime in
April or May  (I'm in Canada) and you tell people to go home 'cause your
CE won't be onsite until 6:00 pm.  Yes... it's bad for you but the users
don't seem to mind as much.
 
Jim

ATOM RSS1 RSS2