
Installing DaggeX 0.9 is quite simple, but there are two ways you can do it.

1) If you have an older distribution of DaggeX, you'll only need to replace
   the server binary and copying usr:lib/x11/rgb.txt to your usr:lib/x11/

2) Installing DaggeX 0.9 from scratch. This file is about this option.

Now that you're reading this you obviously has uncompressed the DaggeX0.9.lha
archibve, so that's been dealt with. If not, do it.

Now you have a directory with a few files and directories in it. 

To make DaggeX installation complete you'll only have to do a few things.

1) add a 'assign daggex: drive:daggex', where drive is the the place you
   unarchived DaggeX. 

2) add a 'set DISPLAY foo:0' line to your user-startup. foo is the default
   machine/communications method to use. if you use local messageport 
   communications, then 'foo' is 'local' so the line looks like

   set DISPLAY local:0

   If you choose to use AmiTCP communications for locally running clients, then
   foo is you machines name, 127.0.0.1 don't work for some reason. So if your
   machines name is 'honeypie.someplace.kindergarten.edu' the line looks like

   set DISPLAY honeypie:0

   Of course using commandline option -display or -d overrides this variable.

3) add a 'set XAUTHORITY /somedrive/directory/.xauthority'. this'll tell 
   clients where to look for the authority file. If you use the supplied
   .xauthority file this should be /daggex/.xauthority.

4) add a 'set FONTPATH /drive/place/,/anotherdirve/anotherplace' in the default
   configuration this should look like

   set FONTPATH /daggex/fonts/bdf/misc/,/daggex/fonts/bdf/100dpi/,/daggex/fonts/scaled/speedo/,/daggex/fonts/bdf/75dpi/

5) If you're bot using AmiTCP add a 'set HOSTNAKME 127.0.0.1' to your
   user-startup.

6) add a 'path daggex: daggex:bin add' to your user-startup.

7) copy libs/ixemul.library to your libs or add an assign. If you already have
   ixemul.library v39.47 you can skip this.

8) add an assign usr: daggex:usr if you don't have usr: assigned to someplace
   already. If you have usr: assigned to someplace, do a 'copy usr/#? all usr:'

9) add an 'assign etc: daggex:etc' if you don't have etc: assigned to someplace
   already. 

Thats it! For convenience you might want to add aliases and stuff, but that's
up to you.


Now DaggeX can be started with 'startx'. But you should edit startx script to
suit your system. The default configuration of startx assumes you have done
everything mentioned above, and want to run twm locally using messageport
communications. It also loads resources from supplied .xdefaults file.
