General comments on the communications engine: The most current copies of the code reside in the /vrmidtown/vrmidtown directory. The most current server if probably in /vrmidtown/vrmidtown/testserver. The most current graphics client is in vrmidtown/vrmidtown/ client/viewer A copy of the viewer that has integrated chat funcitons and a sample simple agent is in vrmidtown/vrmidtown/testclient/viewer Note that for chatting to work properly (ie not core dump) you must go through the glm3d.c file and supress most of the error messages (see the glm3d.c in /testclient/viewer). Addendum: a workaround for this may be possible, check the mailing list for updates. The files in the vrmidtown/vrmidtown directory are used by both the client and the server sides of the communcations engine. The testserver directory contains the server and the testclient and client directories contain client implementations. Note that the server runs a client to handle most of the functionality of the server itself, so the server is rather simple. In general all the functionality of the comm layer if handled by a variety of event which are specifically enumerated. Server Notes: All the clients seem to default to port 2112 so it is best to run the server on port 2112 to avoid difficulties. Client Notes: A path to some graphic libraries nees to be defined to get the graphical clients to run properly. Normally this is done using a simple shell. The one in testclient if client.sh while I believe to one the run the other is in /vrmidtown/vrmidtown/ client/ Graphical clients with communications enabled only seem to run on SGI O2s and Octanes (IRIX 6.3 and above). Addendum: There has been some progress made toward making a server that will run on other types of unix but I am not sure how far advanced these efforts are. As an added bonus the viewer may have trouble compiling on some machines. It compiles fine on the Indigo2s in GVU. Addendum: This seems to have something to do with a 64 vs 32 bit compatibility problem. It may only exist on the Octane.