HDTenEightyP/NetNews huggingface dataset:
From: fajner@frlv.bull.fr (Alain.Fajner)
Newsgroups: comp.windows.x.intrinsics,comp.windows.x.motif,comp.windows.x
Subject: How to change a window title dynamically ?
Keywords: title, motif
Date: 14 Dec 92 13:28:21 GMT
Followup-To: comp.windows.x.intrinsics
Distribution: comp
Organization: Cediag Bull S.A., Louveciennes, France


I'm using OSF/Motif and I have a problem...

I am looking for the way to change the title of a Shell Widget once it has
been managed. This doesn't work at all :

	XtSetArg(args[0], XmNtitle, xs);
	XtSetValues(ShellWin, args, 1);

Is something missing ???


--
                                                              ,,,
                                                             (o o)          
=========================================================oOO==(_)==OOo=====
| Alain FAJNER                  |  EMail :  A.Fajner@frlv.bull.fr         |
| BULL CEDIAG  PC 3B6           |                                         |
| 68, Route de Versailles       |    Tel : (33 1) 39 02 45 80             |
| F-78430 Louveciennes FRANCE   |    Fax : (33 1) 39 02 47 95		  |
+_________________________________________________________________________+
                                                          (__)   (__)
From: windy@pencom.com (Windflower Gilbert)
Newsgroups: comp.windows.x.intrinsics
Subject: ICCCM Compliance verification
Date: 17 Dec 92 20:14:23 GMT
Reply-To: windy@pencom.com
Organization: Pencom Software

Has anyone every done any testing to verify ICCCM (Inter-Client  
Communication Conventions Manual) compliance? I need to do some and I  
would appreciate any information you might have on it.

Thanks,
Windflower Gilbert

Pencom Software
Austin, Texas USA
windy@pencom.com
Newsgroups: comp.windows.x.intrinsics
From: amc@WLV.IIPO.GTEGSC.COM (Allen M. Cohen)
Subject: Depth 8 label pixmap
Keywords: pixmap raster label
Organization: GTE Government Systems
Distribution: na
Date: Thu, 17 Dec 92 00:54:35 GMT


-- 
<> Allen M. Cohen -- GTE Govt Sys 31717 LaTienda Dr Westlake Vlg, Ca. 91358 <>
<> 1853 Stonesgate St.            Internet:  amc@IIPO.GTEGSC.COM            <>
<> Westlake Village, Ca. 91361    Voice: (818) 706-6869 FAX: (818) 706-5050 <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
From: chaumett@labri.greco-prog.fr (Serge CHAUMETTE)
Newsgroups: comp.windows.x.intrinsics
Subject: Re: Problems positioning widgets in a Form widget
Date: 18 Dec 92 16:34:52 GMT
Organization: Laboratoire Bordelais de Recherche en Informatique

Use .fromVert and .fromHoriz resources for children.

s.c.

-- 
*----------------------------------*------------------------------------*
|         Serge CHAUMETTE          |                                    |
|              LaBRI               |                                    |
|Laboratoire Bordelais de Recherche|phone : (+33) 56 84 69 04           |
|          en Informatique         |fax   : (+33) 56 84 66 69           |
|       Universite Bordeaux I      |e-mail: chaumett@labri.greco-prog.fr|
|    351, Cours de la Liberation   |                                    |
|    33405 TALENCE Cedex, FRANCE   |                                    |
*----------------------------------*------------------------------------*
Newsgroups: comp.windows.x.intrinsics
From: iain@ee.ryerson.ca (Iain Campbell)
Subject: Overriding Key Translations in Athena Text Widget
Organization: Ryerson Polytechnical Institute, Toronto
Date: Thu, 17 Dec 1992 20:02:21 GMT

I'm having a problem overriding the Return key xlation in the
Xaw AsciiText widget.  I'm following the method outlined in
the Vol 4 X Toolkit Intrinsics Book, as follows:


String FallbackResources[] = {

.....

    "*Text*translations     : #override\n\
        <Return>            : returnPressed()",

};

...


static void ReturnPressed(w, event, params, num_params)

Widget w;
XButtonEvent *event;
String params;
Cardinal *num_params;

{

do stuff

}

...

main(argc,argv)

int argc;
char **argv;

{

...

static XtActionsRec localActions[]=
{
    "returnPressed",ReturnPressed
};

...

define widgets ...
add callbacks ...

XtAppAddActions(ApplicationContext, localActions, XtNumber (localActions));

XtRealizeWidget(topLevel);                      /* realize the widget hierarchy */

XtAppMainLoop(ApplicationContext);              /* start event looping */

}




Thanks in advance ...

Iain


dotesseyegeedotesseyegeedotesseyegeedotesseyegeedotesseyegeedotesseyegee
dotesseyegee                                                dotesseyegee
dotesseyegee     iain@ee.ryerson.ca       < now playing     dotesseyegee
dotesseyegee     iain@acsserv1.ryerson.ca < coming soon     dotesseyegee
dotesseyegee                                                dotesseyegee
dotesseyegeedotesseyegeedotesseyegeedotesseyegeedotesseyegeedotesseyegee
From: elf@ee.ryerson.ca (luis fernandes)
Newsgroups: comp.windows.x.intrinsics
Subject: Re: Problems positioning widgets in a Form widget
Date: 15 Dec 92 20:42:37 GMT
Organization: Ryerson Polytechnical Institute, Toronto

riehm@medizin.uni-ulm.de (Thomas Riehm) writes:
>Hi folks,
>
>I've a problem with Athena's Form widget [...]
>I can't specify the position of any of the Children in a Form
>widget. 

> [...bogus code deleted...]

Use the following constructs to position widgets explicitly
within a form widget:

	/*...*/

	/*...create form widget */

	/* create button "foo" at 10,20*/
	foo=XtVaCreateManagedWidget("foo",commandWidgetClass,form,
						XtNhorizDistance, (Position) 10,
						XtNvertDistance, (Position) 20,
						NULL);

	/* create button "bar" at 40,50*/
	bar=XtVaCreateManagedWidget("bar", commandWidgetClass, form, 
						XtNhorizDistance, (Position) 40,
						XtNvertDistance, (Position) 50,
						NULL);

	/* ...*/

--
elf@ee.ryerson.ca
Xref: sparky comp.windows.x.intrinsics:664 comp.windows.x.motif:8046
From: greer@euphoria.xis.xerox.com (Greer Tan Swiston)
Newsgroups: comp.windows.x.intrinsics,comp.windows.x.motif
Subject: Warning: Tried to remove non-existant accelerators
Date: 15 Dec 92 19:34:52 GMT
Organization: Xerox Imaging Systems, Inc.

I have tracked this down to be a warning coming from the Xt library
subroutine called "RemoveAccelerators" which is called by internal
routines called by Core.SetValues and Core.Destroy ... so I figure it
has something to do with my calling XtDestroyWidget ... but I am not
sure what.

It is particularly confusing to me, in that this warning seems to be
machine dependent ... even though all my accelerators are defined with
my application's resource file, on some machines, I get this error and
I don't get them on other machines ... and I do not know what
similarities or differences to look for.  On almost all the
development machines (Sun SparcStations) we do not have a problem ...
but we are seeing this error on the HP, and on some (not all) foreign
site machines (i.e. non-development machines).

Anyone have any tips/hints about this?  I would greatly appreciate it.
Thanks.

Greer Tan Swiston
greer@xis.xerox.com

P.S. By the way, we are using vanilla X11R4 (from the Consortium), and
vanilla Motif 1.1.3 (from OSF) on Sun Sparcs, IBM rs6000, Integraph
(Clipper), and HP9000.

Thanks in advance for any help!

-- 
Greer Swiston, greer@xis.xerox.com   |DISCLAIMER:  ... the opinions 
Xerox Imaging Systems, Inc           |expressed could be mine or anybody's.
9 Centennial Drive                   |Does it matter?  It's just an
Peabody, MA 01960                    |opinion ...
Newsgroups: comp.windows.x
From: cctr127@csc.canterbury.ac.nz (Jason Haar)
Subject: Need to convert R5 fonts back to R4!
Reply-To: Jason Haar <j.haar@csc.canterbury.ac.nz>
X-Newsreader: TIN [version 1.1 PL8]
Date: Fri, 18 Dec 1992 02:44:51 GMT


Help!

I've got some wonderous apps I need to display on X11R4 servers, but the
fonts in use are in *.pcf format.

Does anyone know of a pcftosnf converter? Or is there another way I can
get access to these fonts (besides upgrading the R4 servers - I can't
they're DECwindows ;-)

 --

Cheers

Jason Haar, Network Consultant
CSC, University of Canterbury, Christchurch, New Zealand
phone: +64-3-3642 2336    fax: +64-3-364 2332
Newsgroups: comp.windows.x
From: murthy_j@jhunix.hcf.jhu.edu (Jayant Murthy)
Subject: changing window titles interactively in TWM
Organization: HAC - Johns Hopkins University, Baltimore
Date: Fri, 18 Dec 1992 15:43:43 GMT


How do I do this. I looked in the man pages for twm and nothing seemed
obvious

Jayant

Xref: sparky comp.windows.x:20214 comp.sys.hp:14080
From: smr@pki-nbg.philips.de (Stephen Riehm)
Newsgroups: comp.windows.x,comp.sys.hp
Subject: Re: keyboardFocusPolicy problem
Date: 15 Dec 92 12:23:09 GMT
Reply-To: smr@pki-nbg.philips.de
Followup-To: comp.sys.hp

dkarr@sierra.com (David Karr) writes:

[... about a problem where when you have keyboardFocusPolicy set to
explicit, and you use the keyboard to move around within a given
application, certain situations lead to a loss of control via the
keyboard, while still having access via the mouse...]

>Self-followup:

>I've discovered that this problem only occurs if the application was built
>on the HP.  I tried running the application built on the Sun (Motif from
>ICS, I believe), and displaying on my 700/RX, and it does not display the
>problem.

>(I suppose this would have been better directed to comp.windows.x.motif and
>comp.sys.hp.)

[ followups being sent to comp.sys.hp now ]

I experience similar problems when using HP's datebook program, I also
have everything set to explicit, and I can bring up the datebook with a
couple of keypresses, enter in a date and message, but in order to
select an event type, I need to use the mouse (whinge number 1), and
once I have used the mouse, the focus highlight around the current
widget is lost (whinge number 2), and I am forced to continue using the
mouse in this application until I close the window (at which point I am
able to fire up another one via the keyboard again.) (whinge number 3)

If anyone has found how to fix this, I would be very grateful to know
how!

>David M. Karr
>Sierra Geophysics, Inc.
>ARPA: dkarr@sierra.com, UUNET: uunet!sgihbtn!dkarr
>Phone: (206) 822-5200 (x343)

thanks in advance

-----------------------------------------------------------------
Stephen Riehm		Configuration Management	   _-_|\ 
smr@pki-nbg.philips.de	Philips Kommunikations Industrie  /     \
Work: +49 911 526 2975	Nu"rnberg, Germany		  \_.-.!/
Fax:  +49 911 526 3678	"I was there, now I am here!"	       v 
"My company speaks another language, I CAN'T speak on its behalf"
PS: You think I am joking, I can't speak the language that well so
		PLEASE DON'T REPLY IN GERMAN!
			    thanks
Xref: sparky comp.windows.x:20384 comp.windows.x.apps:1711
From: kmiller@mipos2.intel.com (KELLY MILLER)
Newsgroups: comp.windows.x,comp.windows.x.apps
Subject: imake,XawClientDepLibs
Date: 18 Dec 92 18:24:14 GMT
Distribution: usa
Organization: Intel Corporation, Santa Clara, CA USA

Help! I am trying to make different Xtools and Xapps but I keep getting
problems when if comes to linking in the libs.
I get the error:
make: Fatal error: Don't know how to make target `XawClientDepLibs'
Which I don't have defined in my imake file.
The problem is I have no idea what libs these are or what to put here.
the cc line goes like this:
cc -o xmailbox xmailbox.o list.o message.o biff.o actions.o DrawingA.o -O  XawClientLibs

cc: Warning: File with unknown suffix (XawClientLibs) passed to ld
ld: XawClientLibs: No such file or directory
*** Error code 4
make: Fatal error: Command failed for target `xmailbox'

Any help what these libs look are and where they might be located is appreciated.







kmiller@mipos2.intel.com
From: ggh@reef.cis.ufl.edu (Greg Huey - Aymer deGregory)
Newsgroups: comp.windows.x.pex
Subject: Connecting PEX workstations to X windows via "connid"
Date: 11 Dec 92 21:05:38 GMT
Organization: Univ. of Florida CIS Dept.


  I am creating a widget with XtCreateManagedWidget of class formWidgetClass,
and then trying to get PEX SI to use this window as its drawing surface.
Follows is a code summary:
      .
      .
      .
Pconnid_x_drawable connid;
Widget dform;

{X initilaization..blah blah blah}
{tform is the parent widget}

	dform = XtCreateManagedWidget("dform", formWidgetClass, tform,
					xarg,nxarg);

	connid.display = XtDisplay(dform);
	connid.drawable_id = XtWindow(dform);

	popen_phigs(PDEF_ERR_FILE, PDEF_MEM_SIZE);
	popen_ws(1, (char *)&connid, phigs_ws_type_x_drawable);
       .
       .
       .
I then procede to try to use the opened workstation. Code that produces
a pretty multi-colored 3D cube fails to display anything -- the screen
remains black. In another program I use the same structures, the same
view representation, but I dont use X toolkit. This program works fine.
Here is what I do:
	popen_phigs( PDEF_ERR_FILE, PDEF_MEM_SIZE );
	connid.display = display = XOpenDisplay( NULL );
	connid.drawable_id = XCreateSimpleWindow( display, blah blah blah);
      .
      .
      .
	popen_ws( 1, &connid, phigs_ws_type_x_drawable );
As I said, the 3D cube gets drawn w/o problems here. It seems to be the fact
that Im using the X toolkit...perhaps Im getting the values for
connid.display and connid.drawable_id incorrectly from the widget
superstructure? Has anyone ever dealt with this sort of thing before?
Can anyone suggest a reference or sample program that might provide insight?

Thanks
Greg
ggh@reef.cis.ufl.edu
ggh@qtp.ufl.edu
From: kiki@bass.bu.edu (Keith Baccki)
Newsgroups: comp.windows.x.pex
Subject: Re: AH HAAAA.... (INQUIRE WS TYPES)
Date: 19 Dec 92 14:53:43 GMT
Reply-To: kiki@bass.bu.edu (Keith Baccki)
Followup-To: comp.windows.x.pex
Organization: Boston University

In article <1992Dec14.173431.16745@dsd.es.com> rthomson@dsd.es.com (Rich Thomson) writes:
>In article <1992Dec9.155020.19988@mintaka.lcs.mit.edu>
>	mor@xenon.lcs.mit.edu (Ralph Mor) writes:
>>In DEC PHIGS, the default workstation (specified by phigs$wstype and
>>phigs$conid environment variables) is opened at OPEN PHIGS time.
>
>OK, but what does this have to do with the list of workstations that
>are supported by the connection?  The connection is still made at OPEN
>PHIGS time, right?  When you connect to a PHIGS implementation it
>should know what kinds of workstations are supported.
>


	Well, the answer (thank you Andy Vesper!) turned out to be
quite simple. I forgot that it was emailed to me, not posted to this
group. All you do is use the X function "XInitExtension()" . Give it
the display variable and the extension name, and it returns NULL
if the extension is not running.

if(XInitExtension (display,"X3D-PEX") == NULL)
{
   printf("\n Get a better machine, loser...\n");
   exit(0);
}


Thanks again Andy.



			Keith
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: Connecting PEX workstations to X windows via "connid"
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Date: Sat, 12 Dec 92 00:22:33 GMT

In article <37896@uflorida.cis.ufl.edu>
	ggh@reef.cis.ufl.edu (Greg Huey - Aymer deGregory) writes:
>  I am creating a widget with XtCreateManagedWidget of class formWidgetClass,
>and then trying to get PEX SI to use this window as its drawing surface.

It doesn't look like you're realizing the widget before attempting to
open the workstation.  The window for the widget isn't created until
the widget is realized.  Since you're using Xt, why don't you try
using the PEXt workstation widget I wrote?  Its in contrib/lib/PEXt in
the R5 distribution.  The workstation widget opens a PHIGS workstation
on its window when it is realized.  You could just add:

>	dform = XtCreateManagedWidget("dform", formWidgetClass, tform,
>					xarg,nxarg);
	ws = XtCreateManagedWidget("ws", pextWorkstationWidgetClass,
				    dform, NULL, 0);

And then do whatever you like with the widget's workstation.

						-- Rich
-- 
		      Don't blame me; I voted Libertarian
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer
From: m@jacobi.uucp (mark mccallum)
Subject: Documentation format for transformations wanted.
Organization: Yale University, New Haven, CT
Date: Tue, 15 Dec 1992 23:31:51 GMT

I am preparing a documentation/presentation format for PHIGS viewing
transformations. I would appreciate any input. I am also looking for
examples of viewing Transformations in real applications. I am currently
developing a system that will eventually be turned over to a software
group with relatively little PHIGS experience. My goal is to come
up with a formalism to document what I have done and some examples to
give them a better feel for transformations.

thanks,
mark
Newsgroups: comp.windows.x.pex
From: death@opal.cs.tu-berlin.de (MC68332 Amir Dabui  NUKEM)
Subject: SunPHIGS 2.0 - TRANSPARENCY ?????
Keywords: transparency
Organization: Techn. University of Berlin, Germany
Date: Thu, 17 Dec 1992 16:11:36 GMT

Hai,
Who has made any experiences with transparency using SunPHIGS 2.0.
What has to be done #$$@!.
gruetzi,
death@cs.tu-berlin.de

From: shrum@hpfcso.FC.HP.COM (Ken Shrum)
Date: Mon, 14 Dec 1992 21:30:25 GMT
Subject: Re: AH HAAAA.... (INQUIRE WS TYPES)
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.windows.x.pex

In comp.windows.x.pex, rthomson@mesa.dsd.es.com (Rich Thomson) writes:

> I don't see how "default workstations" should change INQUIRE
> WORKSTATION TYPES.  Or are you saying that the connection to the PEX
> server isn't made until OPEN WORKSTATION time?  That doesn't sound
> very smart.

What PEX server?  There isn't even necessarily an X server running on
the client.  Until OPEN WORKSTATION time, the client knows nothing
about what server is in use.

    Ken Shrum
From: ggh@reef.cis.ufl.edu (Greg Huey - Aymer deGregory)
Newsgroups: comp.windows.x.pex
Subject: email address for PEX software support
Date: 16 Dec 92 18:27:53 GMT
Distribution: comp.windows.x.pex
Organization: Univ. of Florida CIS Dept.


  Does anyone know the email address of software support for PEX?

Thanks
Greg
ggh@reef.cis.ufl.edu
Newsgroups: comp.windows.x.pex
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: AH HAAAA.... (INQUIRE WS TYPES)
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Date: Mon, 14 Dec 92 17:34:31 GMT

In article <1992Dec9.155020.19988@mintaka.lcs.mit.edu>
	mor@xenon.lcs.mit.edu (Ralph Mor) writes:
>In DEC PHIGS, the default workstation (specified by phigs$wstype and
>phigs$conid environment variables) is opened at OPEN PHIGS time.

OK, but what does this have to do with the list of workstations that
are supported by the connection?  The connection is still made at OPEN
PHIGS time, right?  When you connect to a PHIGS implementation it
should know what kinds of workstations are supported.

>The point is that OPEN WORKSTATION can open a workstation that is
>not the default.  So, INQUIRE WORKSTATION TYPES (which can be called
>before OPEN WORKSTATION), does not know ahead of time if there will
>be a connection to a valid PEX display.

I don't see how "default workstations" should change INQUIRE
WORKSTATION TYPES.  Or are you saying that the connection to the PEX
server isn't made until OPEN WORKSTATION time?  That doesn't sound
very smart.

						-- Rich
-- 
		      Don't blame me; I voted Libertarian
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer
Newsgroups: comp.windows.x.pex
From: mor@expo.lcs.mit.edu (Ralph Mor)
Subject: Re: AH HAAAA.... (INQUIRE WS TYPES)
Organization: X Consortium, MIT Laboratory for Computer Science
Date: Sun, 20 Dec 1992 20:22:09 GMT

rthomson@mesa.dsd.es.com (Rich Thomson) writes:

>OK, but what does this have to do with the list of workstations that
>are supported by the connection?  The connection is still made at OPEN
>PHIGS time, right?  When you connect to a PHIGS implementation it
>should know what kinds of workstations are supported.

I think we have a disagreement over what INQUIRE WORKSTATION TYPES is
supposed to tell you.  You seem to think it returns all supported
workstation types for the connection made at OPEN PHIGS time.  My
understanding of DEC PHIGS, is that it returns all workstation types
supported by the implementation (regardless of what connection is
made at OPEN PHIGS time).  I tried to explain the reasoning for this
before.  OPEN WORKSTATION can open a new connection to any display
on the network, so why should INQUIRE WS TYPES only return wstypes
supported by the display opened at OPEN PHIGS time?  I think we've
battered this topic enough.  If you want to discuss it further, we
can take it off line.

Ralph

Newsgroups: comp.windows.x.pex
From: wdcg6607@uxa.cso.uiuc.edu (William David Cizek)
Subject: Is there a FAQ for this group?
Organization: University of Illinois at Urbana
Date: Mon, 21 Dec 1992 03:43:50 GMT


Need I say more?

Bill Cizek
cizek@uiuc.edu
From: johns@hpfcse.HP.COM (John Sutton)
Newsgroups: comp.windows.x.pex
Subject: PHIGS++?
Date: 15 Dec 92 16:39:16 GMT
Organization: Hewlett Packard Co.



Can anyone tell me what PHIGS++ is?  I recently received an enquiry
regarding our support of graphics standards and was asked specifically
about PEX, PHIGS, PHIGS+ and PHIGS++.  I cannot seem to find anyone
who has heard of PHIGS++.


Thanks.





                   John Sutton - Technical Consultant
    /_  __         Professional Services Organization
   / / /_/          Hewlett-Packard (Canada) Limited  
      /                    (416) 678-3666
Newsgroups: comp.windows.x
From: djones@cbnewsg.cb.att.com (david.jones)
Subject: HELP : Setting system time chokes server.
Keywords: time
Organization: AT&T
Date: Wed, 16 Dec 1992 14:21:04 GMT

I have an application that runs under X11R5 server.
(on SPARC based Sun)

The app. is built static under OpenWindows 2 ( - I know why the difference -
but thats another story. )

One of the options of this app. is to be able to set the machines
system time. If I do  this a couple of times in a row, the server
gives me the message "Select failed; error code 22". This seems to
come from _XtwaitForSomething.

Looking at the code (in NextEvent.c) it looks like I need to send the 
server EINTR if I change the time. Is this correct ?

If so how ?

Any help/pointers appreciated.

- Dave


----------
David G Jones            |    Voice: +44 666 832273
AT&T Network Systems     | Internet: mltsa!djones@mlgtw.att.com
Swindon Road             |     UUCP: {...att...}!mlgtw!mltsa!djones
Malmesbury               |
ENGLAND                  |
----------
Newsgroups: comp.windows.x,comp.unix.sys5.r4
From: quy@stone.oz.au (Quy Tonthat)
Subject: SUMMARY: USL X clients and DISPLAY number
Organization: Stone Microsystems, NSW, Australia
Date: Mon, 14 Dec 92 06:04:04 GMT
Keywords: USL, DISPLAY


Few days ago, I posted a question to ask everybody how to 
start  X clients on USL svr4 and displayed on an X server
with DISPLAY number other than 0.

The following command won't work:

     xterm -display xzy:1

The error message is "Can't not open display".

With the great help from people at USL, I have the answer from
kumar@usl.com:

> assuming you are trying to run USL clients against various servers
> with display set to non-zero, you need to do one thing 
>
> In your /etc/services file, add the following:
>
> xserver1        6001/tcp   # X server display 1
>
> If you are running our server as display 1 (ie: X :1 &), you need
> to do this on the server machine also, or else the remote USL
> clients will not connect to our server.

I wonder why I missed this. I guess because all the systems I have
around here hardcoded port 6000 in their code or at least hardcoded
the convention 
      port for server n = (port for server 0) + n

Do you know any other X that does the way USL does ?
Of course I see this as a feature as long as users know about it.

-- 
   Quy Tonthat                              Email: quy@stone.oz.au
   Stone Microsystems,                      Fax:     (02) 818 3070
   NSW.     Australia                       Voice:   (02) 818 3211