	Instructions on Setting up MDComm for VMD


1. Get and install RAPP and MDComm.  RAPP should be installed in some
  other directory, which will be refered to as $RAPPDIR .

  RAPP home page: http://www.ncsa.uiuc.edu/Apps/MCS/CompSci/RAPP/rapp.html
  MDComm home page: http://www.ks.uiuc.edu/Research/mdcomm/
  
  You have the choice of installing the prebuilt binaries for MDComm
  or installing both RAPP and MDComm and then compiling them.

2. Make sure that you have the MDComm for this architecture.

3. Make a symbolic link from $RAPPDIR to ./rapp

	ln -s $RAPPDIR ./rapp

4. Run "setup_rapp", a perl script which will make all the appropriate
symbolic links.

  If you don't have perl installed (why not?) you can do this step by
hand instead.

    a) ln -s rapp/include include
    b) look in rapp/apps/mdcomm/bin for the list of available
architectures.  There should be things like SGI5 or HPPA.  Call this
name RAPP_ARCH and use the following table to find the corresponding
definition for ARCH

	RAPP_ARCH   <===>  ARCH
        ------------------------
	  SGI5		   IRIX5
	  HPPA             HPUX9

  The problem is the architecture definitions used by RAPP (and
MDComm) are different than those used by VMD.  This will be used to
set up the correspondence between the two systems.

    c) ln -s rapp/apps/mdcomm/bin/$RAPP_ARCH bin_$ARCH
    d) ln -s rapp/apps/mdcomm/lib/$RAPP_ARCH lib_$ARCH


5.  Reconfigure VMD to add the "REMOTE" option, ie.

	cd $VMDDIR
	./configure `cat configure.options` REMOTE

Remember, when all the new options are defined you should redo the
Makefile dependencies before compiling (though you'll probably have to
have gcc for that step).

	cd $VMDDIR/src
	make depend

And that should be everything.

						Andrew Dalke
						vmd@ks.uiuc.edu
						Feb. 21, 1997
