Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!edcastle!spider!raft.spider.co.uk!mark
From: mark@spider.co.uk (Mark Valentine)
Newsgroups: comp.sys.mips
Subject: Re: /usr/X11/contrib/bin/xlock under RISCwindows4.0
Keywords: xlock RISCwindows4.0 RISCos4.52 RS2030
Message-ID: <1991May27.092652.13584@spider.co.uk>
Date: 27 May 91 09:26:52 GMT
References: <1991May25.091811.5484@spider.co.uk>
Sender: news@spider.co.uk (USENET News System)
Organization: Spider Systems Limited, Edinburgh, UK.
Lines: 25
Nntp-Posting-Host: redknee.spider.co.uk

In article <1991May25.091811.5484@spider.co.uk> I wrote:
>Anyone had any success with the xlock supplied in the contrib section of
>the RISCwindows4.0 release?  I always get the following error from X when
>I run it.
>
>    X Error of failed request:  BadValue (integer parameter out of range for operation)
>     [...]

I just answered this one for myself whilst investigating another problem.

From the latest comp.windows.x FAQ:

    Subject:  39)  Why doesn't xlock work on my R4 server?

            The version of xlock that went out on the R4 contrib tapes was not
    quite R4-conformant; when built and run, it will produce an X_GrabPointer
    protocol error. This can be fixed by making the R4 server run in bug-
    compatibility mode; just say `xset bc`.
            xlock has been fixed since; in addition, a major revision just came
    out (to comp.sources.x) and can be used instead.  [10/90]

		Mark.
-- 
Mark Valentine, Spider Systems <mark@spider.co.uk>            /\oo/\
  "I'll be mellow when I'm DEAD."