Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hp-pcd!hpfcso!stroyan From: stroyan@hpfcso.HP.COM (Mike Stroyan) Newsgroups: comp.sys.hp Subject: Re: HP 700/X terminal and starbase sox11 Message-ID: <7370261@hpfcso.HP.COM> Date: 27 Nov 90 18:35:16 GMT References: <1990Nov27.030807.15056@sunee.waterloo.edu> Organization: Hewlett-Packard, Fort Collins, CO, USA Lines: 31 > 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. 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 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 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. Mike Stroyan, mike_stroyan@fc.hp.com