PROBLEM / SYMPTOMS: Customers running alpha or beta 3.0 LISP.

Some problems occurred recently at a customer site that could have been
avoided if the customer had upgraded from a 3.0 "alpha I" band.

It is in the best interest of customer satisfaction to identify these
kinds of problems in the field and encourage the customer to load the
vanilla software *only*.  This is the only way to avoid problems that
were already fixed during software testing.  Any customer who is still
running pre-release software will certainly run into strange bugs, and
will probably have problems loading patches and updates.

The system revision level from (PRINT-HERALD) is only one clue to the
ancestry of a band.  Certainly if the system revision level is below
3.205 that must be a pre-release band; but a band at or above 3.205
could conceivably reflect patches on a "deviant" band.

EXPLANATION / INSTRUCTIONS:


The best way to identify the 3.0 release band is to check the login
history displayed by (SI:PRINT-LOGIN-HISTORY).  LISP "remembers" all the
logins prior to each disk-save, tracking who logged in, on what host, at
what time.  If you don't see the login entries listed below (the first
one is the last login done by Engineering on LAMBDA-A) then you can
suspect the band is not descended from the release.  This is also a good
way to find out who, at the customer site, created the loaded band.

(si:print-login-history)
  :  <customer's own logins...>
  :
LISPM   LAMBDA-A        Lambda-A                11-Nov-86 13:50:18
  :       "
robert  LMI-AMNESIA     [No Chaos Address]      15-Sep-86 17:40:13
  :     
LISPM   LMI-DJINN       Guinea Pig                  unknown