HP3000-L Archives

December 1999, Week 2

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:
Matt Shade <[log in to unmask]>
Reply To:
Matt Shade <[log in to unmask]>
Date:
Tue, 14 Dec 1999 11:23:57 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Except that it wasn't a simple processor replacement. It was a complete change
from a 969-400 to a 989-650, or something like that. HPSUSAN and related info
WILL be different.

Mark Landin wrote:

> On Tue, 14 Dec 1999 02:34:23 -0500, Kevin O'Sullivan
> <[log in to unmask]> wrote:
>
> >Hi all,
> >
> >I'll make the assumption that Omnidex complained that the SUSAN number had
> >changed.
> >
> >I have heard that under extreme circumstances, the SUSAN number can be
> >changed by the CE, which if you have a
> >LOT of targeted software installed, could be very handy indeed.
> >
>
> Actually I think changing the SUSAN and related information after a
> CPU replacement is supposed to be the rule, not the exception. Right?

ATOM RSS1 RSS2