Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!osu-cis!killer!kcdev!gentry
From: gentry@kcdev.UUCP (Art Gentry)
Newsgroups: comp.sys.hp
Subject: buggy hp9000/800 3.01 code?
Keywords: hp,unix,image
Message-ID: <659@kcdev.UUCP>
Date: 29 Mar 89 23:13:03 GMT
Organization: AT&T Kansas City, MO.
Lines: 41

A few words to the wise on possible nasty bugs in the 3.01 release of 
HP9000/850 UNIX.

1) terminfo/curses? screens are reversed, ie: what should be inverse video
   is normal and visa versa.

2) IMAGE/9000 - new error code 8200 - suddenly started appearing about every
   20-25 transactions.  A 'gotcha' for programmers, normally we would only
   capture and print word(1) of the status array for error info.  With this
   new code (8200), you need to print all 10 words, as they contain additional
   info as to what the error is.  This is another of those infamous "call HP
   for assistance" errors.  They are supposed to be able to take the additional
   numbers and make some sense out of them.  By the way, this is a DBCore
   error.

3) several new programs - PATH conflicts - HP has released their menu driven
   system management package.  Nice, BUT, they stuck several new programs 
   into /usr/bin which can conflict with program/script names you may already
   have in directories defined after /usr/bin in $PATH.  I had one that drove
   me buggy trying to figure out why a previously perfectly acting program
   was suddenly giving me "permission denied".  Turned out I was grabbing one
   of thier new programs, not mine.  Moral of this story, put your directories
   ahead of the system default directories in $PATH or check VERY carefully
   the program list in the update manuals (which by the way are a TREMENDOUS
   improvement over previous issues).

In our case, HP could not readily figure the cause of items 1 & 2 so we
ended up reinstalling (read that - restored backups) for 2.1 and all is
happy again.

On the subject of restoring, learned another valuable lesson.  If you restore
root and/or /usr while in single user mode, do NOT do an INIT 2 to restart
the system!  During the restore, you will have overlaid several "in use"
system files and the INIT 2 will drop you back to 'login'.  One of the files
overlaid is utmp and login will barf as you no longer have a valid entry in
there and WILL NOT LET YOU LOG IN!!!  Always do a 'shutdown -r' to bring the
system back up after a restoral. That will get everything back into sync.

Like, later kids......
Art
opinions are my own, etc......