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:
John Burke <[log in to unmask]>
Reply To:
John Burke <[log in to unmask]>
Date:
Fri, 18 Oct 2002 09:19:26 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
> From: Bob J. [mailto:[log in to unmask]]
>
> > > * No plans to make SSCONFIG publicly available
> >
> > So license it to trusted third parties. Not making it
> available just creates
> > nightmare scenarios for HP's customers.
>
>  This item is getting blown way out of proportion. If in
> the rare event that (whatever part is housing stable storage)
> fails your hardware vendor can replace the SPU. Next
> you call a few third party software vendors that use the ss
> info and get whatever key they use to lock up their product.
> That shouldn't take much effort....hardly a nightmare with just
> a little planning.
>  The fact is (whatever part is housing stable storage) has proven
> to be the most reliable part of the systems.
>
This is true, though still a pain in the neck and still a potential problem
if the software vendor is out of business. Suppose, now, you want to add a
processor once HP stops selling them. I believe that the latest versions of
MPE will not make use of an additional processor unless the model string has
been updated (which requires ssconfig).

John

ATOM RSS1 RSS2