Path: utzoo!utgpu!attcan!uunet!steinmetz!vdsvax!barnett From: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) Newsgroups: comp.windows.news Subject: Re: Here are some easy questions... Message-ID: <4993@vdsvax.steinmetz.ge.com> Date: 2 Aug 88 13:43:11 GMT References: <2126@ssc-vax.UUCP> Reply-To: barnett@steinmetz.ge.com (Bruce G. Barnett) Organization: General Electric CRD, Schenectady, NY Lines: 24 In article <2126@ssc-vax.UUCP> dmg@ssc-vax.UUCP (David Geary) writes: |"Window display lock broken because process xxxx blocked" I don't know if this is your error, but from Page 5 of READ THIS FIRST: "NeWS 1.1 incorporates a process timeout mechanism. This prevents a single errant process from grabbing the NeWS server, preventing other NeWS processes from running. A clock counts down seconds from a global timeout value. It is reset everytime the server switches to another process. If it reaches zero, the current process gets a TIMEOUT error. The timeout value defaults to 15 seconds. If you find processes are getting timeout errors (for example when displaying complex graphics) the timeout value can be modified (globally) by using the SETJOBTIMEOUT operator described in Appendix D.6 of the PostScript Language Reference Manual. For example, statusdict begin 90 setjobtimeout end will set the timeout to 90 seconds." -- Bruce G. Barnett uunet!steinmetz!barnett