Newsgroups: comp.sys.hp
Path: utzoo!utgpu!watserv1!sunee!maxwell!gordon
From: gordon@maxwell.waterloo.edu (Gordon R. Strachan)
Subject: HP 700/X terminal and starbase sox11
Message-ID: <1990Nov27.030807.15056@sunee.waterloo.edu>
Sender: daemon@sunee.waterloo.edu
Reply-To: gordon@maxwell.waterloo.edu (Gordon R. Strachan)
Organization: University of Waterloo, Waterloo Ont.
Distribution: na
Date: Tue, 27 Nov 90 03:08:07 GMT
Lines: 31

Hello there.

We have recently acquired an HP 700/X X terminal (model C2300B).  While, all
in all this is a nice terminal and we a quite happy with it there is one
severe problem we are having.  This terminal seems to be completely allergic
to starbase.  We use starbase a lot on our system, and we have a number of
graphical programs which we wish to display on the X terminal.  In theory this
is possible through with the starbase sox11 device driver.  Indeed, I have
not had any trouble doing this on other remote X servers (both HP servers and
others such as Sun and NCD terminal).  However, on the 700/X, the terminal
will randomly lock up and die.  There seems to be a critical timing bug
associated with the opening of the window and the call to gopen.  In theory,
this shouldn't happen because I wait for server to notify me that the window
is open before I attempt to call gopen.  Also, the terminal seems to view
the bitmap_to_file function as particularly evil.  It sometimes will work,
but generally causes the terminal to die.  Now I would like to think that
HP would have tested this terminal with their own software before releasing
it so what gives?  Has anyone else seen this type of problem with this
terminal?  Any suggested work arounds?

I would submit a software report on this one but it is not clear to me who
it should be sent to, the HP-UX guys or the HP 700/X guys.  Actually I don't
even now how to submit bug reports on that terminal now that I think of it.


We are using HP/UX v 7.0 and the 700/X server version is listed as B.03.00.
I don't suppose by any miracle there is a later version of the server which
might fix this bug.

Gordon