
               INSTALLATION NOTES FOR LOOM 4.0 with KPML

			    January, 2003


The natural language generation system KPML is generally used with
Franz Allegro or Xanalys Lispworks on PCs running Windows or Sparcs
running Unix. This is relevant to Loom 4.0 because Windows support is
not as complete with the Loom 4.0 release as it might have been.  For
running with Windows, a few changes need to be made.  These changes
are all in the file defsystem.lisp and concern differences between the
implementations of the Lisps for Windows and Windows handling of file
names. 

To use this version of Loom 4.0 it is necessary to load one file from
the KPML 4.0 release first. This is the file version-utilities.lisp
(which is in the folder Processes/startup/). You then need to *replace*
the Loom file defsystem.lisp with the KPML file cond-defsystem.lisp
(also in the folder Processes/startup). The file needs then to have 
its name changed so that it is also defsystem.lisp.

    THESE CHANGES ARE PROVIDED ALREADY MADE IN THE FOLDER
    Processes\kr-interfaces\loom\fix-for-loom4-under-Windows
    Copying all of the files in this folder to the top-level Loom
    directory will do the trick.

Then, after loading the file version-utilities, loading of Loom 4.0
can proceed on all machines and the mentioned versions of Lisp as
described in the Loom installation file.

The trickiest thing about installing is to make sure that Loom knows
which directories the binaries live in, if it messes up at all, then
this can be done by hand by copying the compiled binaries into the
place that Loom wants to have them. If it manages by itself, then all
is well. Some versions of Lisp may end up compiling to the BIN/MISC
directory, which is OK as long as you are only using one of them.

For Lispworks 4.2 you may need to load the file lww42-compatibility.lisp
too.

John Bateman
Uni Bremen