OPENMPE Archives

October 2002

OPENMPE@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:
"Jonathan M. Backus" <[log in to unmask]>
Reply To:
Date:
Fri, 25 Oct 2002 14:27:59 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Cecile,

        I second that but there is a little old prayer that goes to the effect
"Give me the strength to change the things I can, the courage to accept the
things I can't, and the wisdom to know the difference."  I suspect that what
vendors have already done falls into the "things I can't change" group and
to an extent what vendors going forward choose to do is also in this group.
However, having a solution if and when it's needed fall into the "things I
can change" group, with advocacy towards HP.  That is where I would choose
to focus much of my attention.

Thanx,
        Jon

-----Original Message-----
From: OpenMPE Support Group [mailto:[log in to unmask]]On Behalf Of
Cecile Chi
Sent: Friday, October 25, 2002 2:20 PM
To: [log in to unmask]
Subject: Re: [OPENMPE] A No for SSConfig


In a message dated 10/25/02 8:55:43 AM Eastern Daylight Time,
[log in to unmask] writes:

<<  In both cases the vendor was exiting the HP3000 market and in both cases
 the customer was locked into using the application or utility only with the
 HPSUSAN/HPCPUNAME last supported by the vendor.  It happens...
  >>

And I would like to encourage vendors to not let it happen any more, at
least
with the HP3000 software.

Cecile

ATOM RSS1 RSS2