Xref: utzoo comp.unix.sysv386:4641 comp.windows.x:32411
Path: utzoo!attcan!uunet!samsung!mips!sgi!zok!mark
From: mark@zok.UUCP (Mark W. Snitily)
Newsgroups: comp.unix.sysv386,comp.windows.x
Subject: Re: Can't run clients under (Roell's) X11R4 for ISC
Keywords: X11R4, comp.windows.x
Message-ID: <510@zok.UUCP>
Date: 14 Jan 91 12:12:31 GMT
References: <130@chansw.UUCP> <278E6093.15392@orion.oac.uci.edu> <1991Jan12.061432.27366@portia.Stanford.EDU>
Followup-To: comp.unix.sysv386
Organization: The distant planet Zok
Lines: 22

In article <1991Jan12.061432.27366@portia.Stanford.EDU> fangchin@elaine30.stanford.edu (Chin Fang) writes:
>According to the latest FAQ of comp.windows.x, the xclock has bug which
>prevents it from function properly in X11R4 environment (but you can run
>it in X11R3).  It has been fixed and a new src has been posted laterly.
>Check that FAQ for more details. 

Did you mean "xlock" or "xclock" ?  The FAQ mentions the problem and
recent reposting of "xlock", but I found no reference to "xclock" in the
FAQ posted on 31-Dec-90.  Is there a newer FAQ, or did we accidentally
drop/insert a character?

-- Mark

Mark W. Snitily                 Consulting Services:
894 Brookgrove Lane             Graphics, Operating Systems, Compilers
Cupertino, CA 95014             (408) 252-0456
mark@zok.uucp                   West Coast UUCP X11 archive site

If your mailer doesn't like the .uucp domain, these also work:
...!{mips,sgi}!zok!mark, mark%zok@mips.com, mark%zok@sgi.com

For an interesting symmetry, compare the 1661 and 1991 calendars.