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: Re: buggy hp9000/800 3.01 code?
Summary: going back fixed our problems...
Keywords: hp,unix,image
Message-ID: <668@kcdev.UUCP>
Date: 2 Apr 89 19:40:07 GMT
References: <659@kcdev.UUCP> <1370@prcrs.UUCP>
Organization: AT&T Kansas City, MO.
Lines: 34

In article <1370@prcrs.UUCP>, paul@prcrs.UUCP (Paul Hite) writes:
> In article <659@kcdev.UUCP>, gentry@kcdev.UUCP (Art Gentry) writes:
> > 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.
> 
> We are running 3.01 on our 850.  We have not experienced this problem with
> curses.  We "ported" a curses program to the 850 and it worked fine.  The
> program has inverse-video regions on the screen.  The same code works on
> several different versions of hp-ux.  Can you provide more info on your
> problem?   Could it be your terminfo entry?  Have you tried it more than
> one type of terminal?  Can you post a small sample program that illustrates
> the problem?
> 
Hmmmm, interesting.  We tried both the "standard" terminfo entry that came
with 3.01 and our own, which are slightly modified (for printer usage).  Both
caused the inverse video to be reversed on 3.01 and worked correctly when we
went back to 2.1

As a follow up to the bug I reported in HPImage, we have discovered 5 chains
that appear to have been corrupted by 3.01.  On doing a hpifind to locate the
head of the chain and then doing a chained hpiget, Image returns an 8100
error code (and, yep, ya gotta print out the rest of the status array to 
find out what the problem is!)  Status(2) returns a 13137 DBCore internal
error - missing tuple.  Remedy is to unload the database, erase the database,
recreate the database and reload.  And you MUST do a SERIAL unload, by doing
a defaulted CHAIN unload, you'll get the same 13137 error and the unload will
abort.  Priliminary investigation suggests that 3.01 caused several chains
to lose their pointers from MASTER to DETAIL datasets.  More to follow as
we discover more.

Art