[mod.computers.vax] 8600 mbox eco

SYSMSH@ULKYVX.BITNET.UUCP (03/28/87)

The fix for the 8600 memory bug that is tickled by DEUNA/LAT changes the
cpu serial number.  Field service usually neglects to tell you that your
serial number is going to change.  When you re-boot, some of your third
party proprietary software may no longer work......

Mark Hittinger/systems programmer iv/ocis south center
University of Louisville/Louisville, Ky 40292
sysmsh%ulkyvx.bitnet@wiscvm.wisc.edu

oberman@LLL-ICDC.ARPA.UUCP (03/29/87)

>The fix for the 8600 memory bug that is tickled by DEUNA/LAT changes the
>cpu serial number.  Field service usually neglects to tell you that your
>serial number is going to change.  When you re-boot, some of your third
>party proprietary software may no longer work......

VAXs have no software readable cpu serial number. The do have a system ID
number. This number is for DEC use in determining ECO and FCO status. Any
FCO will change the system id. That's why it's there. On some processor
type a lot of CPU have the same SID. And I don't believe all of the new CPUs
even have them. They are some times even settable by DIP switches.

I wish third party software vendors would get to understand this and NOT
use them as keys. It is my policy that is several systems are bid, I reject
any using this silly scheme unless the cost of any alternative is totally
prohibative. The time and effort involved in fixing this when you have
virtually every type ov VAX CPU DEC has ever made is absurd! (Have you ever
had to enter an ISSCO system password? It's several lines of random characters
which have to be exactly right!)

						R. Kevin Oberman
						Lawrence Livermore Nat'l Lab
						arpa: oberman@lll-icdc.arpa
						(415) 422-6955
------