Directory: xds/bin and xds/bin/contrib

All executables will be stored in this directory.

Although NCSA X DataSlice is meant to be server independent since it is
built on the X-Window system, certain operations tend to be dependent
on the implementation of the X-server.  Quirks might appear now and
then due to the different X-servers, and might not necessary imply
bugs in XDataSlice.  In any case, do report any problem that you may
encounter with any of the executables to bugs@ncsa.uiuc.edu.

Executables in the xds/bin/contrib have been contributed to us by users
who have built our sources successfully on their own platforms and have
kindly contributed their executables to us for distribution.  Please
understand that we have not tested these executables ourselves due to the
lack of available machines, and are placing them in the distribution only
for the conveinience of other users who might have problems building the
executables themselves for various reasons.

Note that all executables are compressed to save space and speed up
network transfer.  REMEMBER TO UNCOMPRESS THEM!

Note that X DataSlice now automatically recognizes and handles the
default static visual so that the same XDS executable will run on both
PseudoColor and StaticColor Visuals, etc.  To use the Sun executables
on OpenWindows, set the resource XDS*installCMap in your .Xdefaults file
to TRUE.  You may also turn it on at runtime using the xds -installCMap
commandline option.  Otherwise, color maps may not be set properly on
the OpenWindows X-server.

The executables have been built under XV11R4 wherever possible.
All XV11R4 clients should be able to run under the XV11R3 server and all
XV11R3 clients should be able to run under XV11R4 server (but of course,
that is too general a statement).  Again, if you experience any problems
with the executables under the XV11R3 server, send mail to bugs@ncsa.uiuc.edu.

Overview of client executables:
******************************

*Sun3 OS3.5:	xds_sun3
*XV11R4 client
Much of the development and testing is done on a Sun3/160, so this is
the most reliable of all the executables.  The OS3.5 version should run on
OS4.x too.


*Sun 4/SparcStation OS4.0.3c:	xds_sun4
*XV11R3 client
These executables will run on Sun4s and Sparcstation Is, using the same
version of SunOS.


*Sun386i OS4.0.3c:	xds_386i
*XV11R3 client
To use this executable properly, set the resource XDS*adjustToggles in
your .Xdefaults file to TRUE.  You may also turn it on at runtime using the
xds -adjustToggle commandline option.  Otherwise, toggles may appear to be
clipped.


*Silicon Graphics Personal Iris IRIX3.2G:	xds_iris
*XV11R3 client
This executable will run under the 3.2G 4Sight X-server, but due to the
server's instability, especially with pixmaps, it may crash occasionally
for no apparent reason.  However, if the Iris is used only as a client
machine for display on another X-server, the executable is quite stable.
The UsePixmap option has been turned off for this client because it does
not work on the Iris server.  All images are displayed as XImage structures
instead of Pixmaps.
To use this executable properly, you may have to set the resource 
XDS*installCMap in your .Xdefaults file to TRUE.  You may also turn it on
at runtime using the xds -installCMap commandline option.  Otherwise,
color maps may not be set properly.


*Motorola 88K:	xds_m88k
*XV11R3 client
This executable runs very well under the SysV OS of the new Motorola 88K
server.


*Cray2 Unicos5.0:	xds_cray2
*XV11R4 client
*CrayXMP Unicos5.0:	xds_crayX
*XV11R4 client
Naturally, the Crays can only be used as client machines and you have to run
your X server locally on your own machine.  The rendering speed is very much
dependent on the speed of your X server, and since the computation is done by
the Crays, the speed of the program is just about limited by that of the network
and your X server!