Newsgroups: comp.sys.hp
Path: utzoo!utgpu!watserv1!sunee!maxwell!gordon
From: gordon@maxwell.waterloo.edu (Gordon R. Strachan)
Subject: Re: HP 700/X terminal and starbase sox11
Message-ID: <1990Nov28.013400.28774@sunee.waterloo.edu>
Sender: daemon@sunee.waterloo.edu
Organization: University of Waterloo
References: <1990Nov27.030807.15056@sunee.waterloo.edu> <7370261@hpfcso.HP.COM>
Date: Wed, 28 Nov 90 01:34:00 GMT
Lines: 55

In article <7370261@hpfcso.HP.COM> stroyan@hpfcso.HP.COM (Mike Stroyan) writes:
>>                                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
>
>The older MIT sample servers, (and possibly the terminal's software),
>would not consider a window id valid for other connections until the
>window was mapped for the first time.  The sox11 driver has a separate
>connection to the display, so it could run into this problem.  To avoid

Hmmm.... I had suspected that it had did this thanks for the confirmation.

>the problem map the window and wait for a MapNotify event before calling
>gopen.  You actually have to wait for a MapNotify because the window

Double checking my code I did find that I wait for the MapNotify event. I
used to call XSync and this didn't work at all (obviously because of the
different display connection).  Still, even with the MapNotify I will
occasionally get into trouble.

>manager can redirect an XMapWindow request and delay the mapping
>indefinitely.
>
>The bitmap_to_file function uses block_read to get data from the server.
>There was a correction to the block_read function in the sox11 driver
>made last January.  It corrected block_read data problems on the four
>plane HP X terminals.  The first release with that fix was 7.03.
>
>Neither of these problems are known to make the server die.
>
>>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.
>
>Go ahead and send it to the HP-UX guys.  They can talk to the HP 700/X guys.
>Full version numbers and short source code examples are much appreciated.
>


Tell you what, I'll talk to my SE and try to get v7.03 of the sox11 driver.
That might fix my problems.  If it doesn't I'll try to put together some
sample code.  But like I said it's kind of random so its hard to figure out
the minimum amount of code required to hit it.

By the way, we used to kill the 7.0 server running one the workstation consoles
a lot when doing starbase graphics using the 300h device driver.  I grabbed
the 7.03 server off the net a while back and besides being a lot faster, it
seemed to fix that problem.  All in all, the 7.03 server seems to be quite
stable.

>Mike Stroyan, mike_stroyan@fc.hp.com

Thanks for the help
Gordon

