Qi II is a complete rebuild of Qi. None of the code in Qi I is used in Qi II. The installation routine for Qi II is held in the folder Lisp. To install, first copy your executable CL to the folder Lisp and fire it up. Type

(LOAD "install.lsp").

This should compile, load and save an executable version of Qi II. To run it, click on the respective icon.

When you run the installation program under Linux be sure to set the permissions on the Lisp directory to allow you to do so.

For support on Allegro and CLisp under Linux; Jianshi Huang jianshi.huang@gmail.com

We need support on LispWorks under Linux.

We currently lack ports to Allegro (mlisp version), ABCL, PowerLisp and MCL.

SBCL/CMU

There seems to be a bug in the SBCL/CMU compiler when Qi II is set to the highest compiler speed (speed 3). The code fails on the Proplog example in chapter 10 of FPQi. This does not happen in CLisp, LispWorks or Allegro. Since this occurs in CMU, it may be a bug that SBCL has inherited. Note that this bug was found in SBCL 1.0 for Windows, so it may have been fixed in later releases.

Allegro/LispWorks

Note you have to have licence permission to run the file Qi 1.0.dxl from Franz and your license permission should be in the current folder. Note as of 21st May 2007, we had problems with saving an Allegro image. According to Franz this is due to a problem with Allegro which they aim to fix with 8.1. We don't have this version ourselves.

Hence in the installation under Allegro and LispWorks the program does not quit Lisp after it attempts to build an image, in case this attempt should fail.

If you have problems with saving Allegro then use the next method. Note you still have to have your license permission in the current folder.

(A) Run Allegro using alisp within this folder and then type

(LOAD "install.lsp")

(B) Once you've done that then you need not repeat this process. Whenever you need Qi under alisp enter

(LOAD "run_allegro.lsp")

If you have trouble saving an image under LispWorks then follow the same procedure but use run_lispworks.lsp instead of run_allegro.lsp. Martin Simmons of LispWorks writes

To [avoid an error message on saving a LispWorks image], you need to avoid loading the init files before saving the image.  The recommended way is to save using a build script (which just a Lisp file containing the forms to load the code and the call to SAVE-IMAGE). You use the build script by running the LispWorks executable with the -build build-script options or by using the Application Builder tool in the IDE.

If you are running the diagnostics program tests.qi, you may find that LispWorks will raise a stack allocation continuable error message after 5 minutes run time; hit the continue icon and the system should recover from this.

Qi has been tested under CLisp, SBCL, Allegro and LispWorks. Assuming you want to port this code to a different platform you will probably want to make changes. The file to look in is Lisp/features_load_1.lsp which contains all the feature specific aspects of Qi II. Change this file where necessary.

Once you've got to the point of having a clean installation, you can test it by opening Qi II in the Lisp folder and typing (load "tests.qi"). This will load a battery of diagnostics that will run for 40 minutes. No intervention is required. If the load terminates then you've probably got a clean port.