HP3000-L Archives

June 1997, 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:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Reply To:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Date:
Wed, 11 Jun 1997 07:59:22 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
In article , Jerry says...
>
>At 10:46 AM 6/10/97 EST, you wrote:
>>Sigh!  We had one of those head-shaking incidents with the Response Center
>>today.
>>
>>In less than a month, we are upgrading our 967 to an 987.  We were told
>that we
>>could obtain the HPSUSAN number for the new system after the ship date and
>>order were confirmed.  They were, so we called.
>/snip
>
>I seem to recall that under some circumstances it is possible to retain your
>HPSUSAN number during the upgrade.  This makes it easier in terms of
>contracts/etc.  There indeed is a way to do this as how else would HP
>retain the HPSUSAN when the CPU board fails and is replaced under
>maintenance....
>
>Might want to follow-up with your hardware engineer folks....

The portable pc the se carries has a program to compute the magic code for
changing the HPSUSAN to any value. Be sure to record the HPSUSAN before the 967
is shut down.  Check afterwards.  I did the same upgrade and  one digit of the
HPSUSAN was wrong.

ATOM RSS1 RSS2