The index for the Allegro CL Documentation is in index.htm. The documentation is described in introduction.htm.
This document contains the following sections:
1.0 Installation introductionThis document describes how to install Allegro CL and related products. Please note that the installation procedure is significantly changed from earlier releases of Allegro CL.
A printed copy of this document is supplied with the distribution CD's. (Trial users do not get a CD and so will not get a printed copy of this document. Trial users should read 11.0 The Trial Edition.)
You can install Allegro CL from the CD without any key or code (though you need a license file, as described below, in order to use Allegro CL). Once Allegro CL is installed, the documentation, including this file, is available in the doc/ subdirectory (this file is doc/installation.htm). A copy of this file is also available on the Franz Inc. web site (www.franz.com).
Starting with release 6.0, all versions of Allegro CL (for a particular platform) and all add-on products are copied off the distribution CD onto your computer. (Contrast this with recent releases where only those products for which you are licensed are copied from the CD.) A license file named devel.lic controls which products will be usable. This license file is supplied separately, as described in 10.0 Getting a license file. Allegro CL will not work without a license file properly installed in the Allegro directory. The distribution CD does not contain a license file. You must obtain a license file from Franz Inc. separately from the CD.
If you do not have a license file or the license file you have does not seem to license the correct product mix, contact your Account Manager for information. (That link goes to the file introduction.htm. If that link does not work, call Franz Inc. in Berkeley, California, at +1 510-548-3600 or send email to bugs@franz.com or info@franz.com. In email, be sure to identify yourself and provide information on how you can be contacted.)
Once the material is read off the CD and the license file is installed, you can use the licensed Allegro CL version and all licensed add-on products. If you upgrade your Allegro CL version, or purchase a license for an add-on product, you will be given an updated license file. You do not have to re-read the CD. Simply installing the new license file makes the newly licensed products available for use.
The distribution includes two CD's. They are labeled One and Two. The contents are printed on each CD.
The following shows the size of the Allegro directory after installation, but without ObjectStore installed. The units are 1k blocks.
134924 Compaq Tru64 UNIX (32 bit) 149095 Compaq Tru64 UNIX (64 bit) 124221 FreeBSD 4.x 161545 HP-UX 10.20 165448 HP-UX 11.00 (32 bit) 137401 HP-UX 11.00 (64 bit) 149672 IBM AIX 4.3 124242 Linux, Redhat 5 161442 Linux, Redhat 6 (also 7) 137484 LinuxPPC 2000 207788 IRIX 6.5 170828 Solaris 2.7 and 2.8 265670 Windows 9x, Me, NT and 2000
CD Two (for FreeBSD, Linux Redhat 6, and Windows) is written in Joliet format, which supports long filenames (rather than allowing only 8.3 format). FreeBSD and Linux Redhat 6 users, please note that if you have rebuilt your kernel so that it does not support the Joliet format, certain filenames on CD Two may be mangled (for example, emacs/source/emacs-20.7.tar.gz might be mangled into emacs-source/emacs-20.gz). This only affects files in the emacs/ subdirectory of the CD and (more seriously) redhat6/openssl/openssl.tbz2 and freebsd/openssl/openssl.tbz2 (see below for information on the contents of CD Two).
Note that, therefore, even if your kernel does not support the Joliet format, you can install Allegro CL and (on Linux Redhat 6), ObjectStore (which is not available on FreeBSD). But you may have trouble with installing the OpenSSL libraries and the Emacs sources (see 8.0 Installing OpenSSL libraries).Note further that CD One is written in Rockridge format, which is supported on all UNIX platforms. CD One contains certain material for FreeBSD and Linux Redhat 6 but there should be no problem reading those CDs.
If you want the OpenSSL Libraries and/or the Emacs source files (the only files affected by this problem), you can:
On Windows, Solaris, and Irix, Allegrostore 2.0 is built with ObjectStore 6.0. Since ObjectStore 6.0 database format is not compatible with ObjectStore 5.x database format, which was the format used in Allegrostore 1.3, you must convert existing AllegroStore 1.3 databases before using them with AllegroStore 2.0. Do this as follows:
You should delete the beta version of Allegro CL if you received it. It is not necessary to delete version 5.0.1 if you have that installed, but note that on Windows, the registry will be updated so extensions refer to Allegro CL 6.0 instead of earlier versions.
If you have the Trial edition, see 11.0 The Trial Edition.
Here are the installation steps in brief:
% cd /cdrom/cdrom0/solaris/
See 4.0 Installation of Allegro CL on UNIX for more details.
Windows: (assuming the installation process has not started automatically) find the directory in your Windows Explorer [cdrom-drive-letter]:\windows\.
% ./bunzip2 < acl60.bz2 | (cd /usr/local; tar xf -)
If the copy of bunzip2 on the CD will not execute (some machines restrict running executables on CD's) see 4.1 What to do if bunzip2 won't execute on the CD for what to do.
See 4.0 Installation of Allegro CL on UNIX for more details on this step.
Windows: run the exe file. Double click on it if using the Windows Explorer. Execute it if at a Command Prompt or a DOS prompt. Follow the instructions that appear. See 5.0 Installation on Windows for details.
Be sure that you keep the CD available in case re-installation is necessary, but (unless you purchase an AllegroStore license and need to install ObjectStore) it is not necessary to copy additional material off the CD to use add-on products you may purchase licenses for later. All add-on products are included in the distribution copied from the CD following the procedure given here.
The Allegro CL distributions for all UNIX platforms except Linux Redhat 6 and FreeBSD are on CD One. The Allegro CL distributions for Redhat 6 and FreeBSD are on CD Two. The distributions are in directories whose names refer to the platform and, where necessary, to the operating system version. In each case, we give the minimal OS version that is supported. Generally later versions are also supported, but we cannot have tested on versions released after Allegro 6.0 was released. If you have problems with a later Operating System version, send mail to bugs@franz.com for assistance.
The directories on CD One are:
The directories on CD Two are:
The Windows distribution is also on CD Two.
In each platform-specific directory, there are two files and 0, 1, or 2 subdirectories. If the distribution supports AllegroStore, there is an ostore/ subdirectory. If there is an available shared library version of the OpenSSL library, there is an openssl/ subdirectory. Note: if your Linux Redaht 6 or FreeBSD kernel does not support Joliet CD format, you may have problems installing the OpenSSL libraries. See 1.4 Warning to Linux Redhat 6 and FreeBSD users about long filenames on CD.
The two files are:
AllegroStore customers will also copy material for a new version of ObjectStore on some platforms, as described in the detailed steps below.
Users interested in writing applications using secure sockets may wish to install the OpenSSL libraries if they are available. See 8.0 Installing OpenSSL libraries for instructions and more details. OpenSSL libraries are only supplied on the following platforms: Windows, Solaris, HP-UX (10.20 and 32-bit Lisp 11.00 only), Linux (all types) and FreeBSD.
To install, insert the correct CD into the CD drive. It is not necessary to be root to install, but you must have write permission in the directory where the Allegro Directory will be located (you choose that location; the typical location is /usr/local/). Here are the steps after inserting the CD into the CD drive.
Note to Trial users: the link from 11.2 Information on installing the Trial edition comes here. Follow the instructions below to install the Trial edition for Linux and FreeBSD.
% cd /cdrom/cdrom0/
% cd solaris
If you are installing the Trial edition, cd into the directory where you downloaded the distribution files.
% bunzip2 < acl60.bz2 | (cd /usr/local; tar xf -)
If the copy of bunzip2 on the CD will not execute (some machines restrict running executables on CD's) see 4.1 What to do if bunzip2 won't execute on the CD for what to do.
A directory named acl60/ should be present in the location specified to the tar portion of the command above (/usr/local/acl60/ if you used the exact command above). This is the Allegro directory.
Allegro CL is now installed. See these documentation files to start with:
Note that there is no Allegro Composer executable or binary. To use
Allegro Composer, evaluate (require :composer)
after starting Allegro CL. An Allegro Composer binary can be built by using
buildcomposer.cl. See composer.htm.
There is no CLIM binary, but one can be built using buildclim.cl.
Note for CLIM on Linux and FreeBSD: you must have Metro Link Motif 1.2.4 (Linux) or Metro Link Motif Complete! (FreeBSD). See the Metro Link web site www.metrolink.com for details.
On the distribution CDs, the various UNIX directories which contain compressed files ([CD]/solaris/ on CD One and [CD]/redhat6/ on CD Two, for example), also contain the program to uncompress the files, bunzip2. This program is put on the CD with an executable mode, but some machines restrict running programs on CDs. On such machines, you will not be able to execute bunzip2 in commands like:
% ./bunzip2 < acl60.bz2 | (cd /usr/local; tar xf -)
In that case, you can either:
% chmod +x bunzip2
In either case, the command to uncompress the files becomes (assuming the current directory is the CD directory containing the compressed file):
% [directory with bunzip2]/bunzip2 < acl60.bz2 | (cd /usr/local; tar xf -)
The Allegro CL distributions for Windows is on CD Two. (That CD also has the distribution for FreeBSD and Linux Redhat 6.) The Windows distribution is in the windows/ subdirectory of the CD.
Windows 9x, Me, NT and 2000 are all supported.
The windows/ subdirectory contains one file, acl60.exe and two subdirectory, ostore/ and openssl/.
acl60.exe is a self-extracting executable that, when executed, runs an installation program.
AllegroStore customers need to install ObjectStore, as described in the detailed steps below.
To install, you should exit all programs (step 1) and then insert CD Two (the one containing the Windows distribution) into the CD drive (step 2). If you have autorun enabled, the installation process will start automatically. If not, you must start the executable, as described in steps 3 and and 4.
Note to Trial users: the link from 11.2 Information on installing the Trial edition comes here. Follow the instructions below to install the Trial edition for Windows.
If you do not install the Allegro CL and ANSI documentation and the ANSI spec, shortcuts relating to documentation on the Allegro CL menu item on the Start menu will link you to versions on the Franz Inc. web site. However, if you have the space, it is best to include the documentation.) Also displayed in the dialog is how much space is required for the whole installation and how much space is available.
Check or uncheck the desired options. Click Cancel to cancel installation, Back to choose a different location, and Next to continue. If you click Next, the installation will take place.
Allegro CL is now installed. See these documentation files to start with:
There is no CLIM binary, but one can be built using buildclim.cl.
Be sure you have saved databases where necessary. See 2.0 Preinstallation Steps
AllegroStore does not work on all platforms on which Allegro CL runs, nor on all Operating System versions that Allegro CL works on. See 6.2.2 Step 2: Install ObjectStore for supported platforms and Operating Systems versions.
The next subsections tell you how to install ObjectStore and how to configure it for use with AllegroStore, and how to test the result.
This must be done for every platform.
The new ObjectStore distribution is in an encrypted file in the ostore/ subdirectory of your platform directory on the appropriate CD (CD One for all UNIX platforms except Linux Redhat 6, CD Two for Linux Redhat 6 and Windows).
% cp /cdrom/cdrom0/solaris/ostore/ostore.blf /usr/local/acl60/astore/
(Replace /cdrom/cdrom0 with the actual cdrom directory, if it is different. Replace /usr/local/acl60 with the Allegro directory location, if it is different.)
On Windows, use the Windows Explorer to copy the file.
On UNIX: run [Allegro directory]/ostore.sh.
On Windows: run [Allegro directory]/ostore.bat.
If you are licensed (according to your license file devel.lic) to install ObjectStore, an ObjectStore distribution will now be in place in [Allegro directory]/ostore/. To install it, go to 6.2.2 Step 2: Install ObjectStore.
The supported operating system version levels are:
Make sure the OS_ROOTDIR environmental variable is not set before beginning the installation. The installation procedure will print an error message telling you to un-set the OS_ROOTDIR variable if it is set when you begin the installation. The osinstal (note: one `l' in instal) script starts the installation. You must be root to run this script.
# cd [Allegro directory]/ostore # ./osinstal
When the osinstal script ends, it instructs you what to do next. When running the osconfig step (as described in those instructions), calling osconfig with a "server" argument is recommended for most users. If you desire a client only installation, use a "client" argument.
The minimum-supported operating system version levels are:
Run [Allegro directory]/ostore/setup.exe to begin the installation. The default installation option installs both a client and a server. If you desire a client only installation, choose a custom installation and pick the appropriate custom settings. Note that if you choose the default installation, you will see a number of message boxes containing installation warnings. These warnings should all be ignored. We recommend that you answer 'yes' to the Reinitialize the ObjectStore Server log file? query, and we recommend that you let the installation process configure your computer to automatically start the Ostore server and/or client cache manager.
On Windows 95/98, you may need to increase your environment space for MS-DOS. Do this by adding the following line to your config.sys file on your boot drive:
SHELL=C:\COMMAND.COM C:\ /E:2048 /P
If you get "out of environment space" error when booting Windows 95, then you will need to add the above line.
NOTE: You should reboot after the ObjectStore installation (even though the ObjectStore installation process does not ask you to reboot).
Each user should update their environment appropriately for their use of AllegroStore. The environment variables listed next are used by ObjectStore and you may wish to change them from their default value. Variables required for proper AllegroStore operation are noted in the following table; don't remove those.
OS_ROOTDIR. Setting this is required. The
value of this variable should be the name of the root directory of the
ObjectStore installation. The value of this variable is set
automatically on Windows by the ObjectStore installation.
AS_CONFIG_PATH. Setting this is required.
The value of this variable is the AllegroStore configuration
directory. For a server installation, it should be the same as the
Allegro directory. For a client installation, it should be the
Allegro directory on an AllegroStore server machine. If that
directory is not mounted on the client, specify the path as host:path,
where host is the server host name, and path is the Allegro
directory path on the server machine.
PATH. Setting this is required.
The value
of this variable should include $AS_CONFIG_PATH and
$OS_ROOTDIR/bin. The value of this variable is set automatically on
Windows by the ObjectStore installation.
OS_AS_START. Setting this is required on IRIX
only and not required on other platforms. Specifies the
starting address for the persistent virtual memory address space. The
size of that space is controlled by the related OS_AS_SIZE
variable. On IRIX, the default ObjectStore value (0x64000000)
conflicts with the Lisp C heap. A value of 0x64100000 will not
conflict with the Lisp C heap.
OS_AS_SIZE. Setting this is required on HP-UX
32-bit Lisp versions only (HP-UX 10.20 and 11.0 for 32-bit Lisp)
and not required on other platforms. Specifies the maximum
size of the persistent virtual memory address space. On HP-UX, using
the default value results in a conflict with the Lisp C heap starting
address (0x64000000). Specify the value 0x14000000, which will not
result in a conflict with the Lisp C heap.
OS_16K_PAGE. Setting this is usually not
required. On some IRIX machines, ObjectStore will abnormally
exit with an error message that looks similar to:ObjectStore internal error Fatal error Invalid argument(errno = 22) mmap failed: os_map_memory addr 0x74ee0000, len 0x1000, prot 3, fd 17, share 4 off 0x2000 (err_internal)
If you experience this problem, set OS_16K_PAGE
to 1 (one), and try again.
Astore 2.0 on Linux is based on the Ostore 6.0 SP5 Beta release, which is the first Linux ObjectStore release. Here are issues related to the ObjectStore Beta version status:
On IRIX and HP-UX 11.0 (but not on HP-UX 10.20), you must use the executable aslisp or aslisp8. These executables are needed on HP-UX 11.00 and IRIX to be able to load the AllegroStore shared library. If you use mlisp[8] or alisp[8] on HP-UX 11.00 or IRIX, the load of this shared library will fail.
On other UNIX platforms, you can use mlisp or alisp, both of which have International Character set support, or mlisp8 or alisp8, which do not. (mlisp and mlisp are case-sensitive executables/images; alisp and alisp8 are not.)
;; IRIX and HP-UX 11.00 (to run a case-sensitive ;; image with International Character set support) ;; aslisp -I mlisp.dxl ;; IRIX and HP-UX 11.00 (to run a case-insensitive ;; image with International Character set support) ;; aslisp -I alisp.dxl ;; IRIX and HP-UX 11.00 (to run a case-sensitive ;; image without International Character set support) ;; aslisp8 -I mlisp8.dxl ;; IRIX and HP-UX 11.00 (to run a case-insensitive ;; image without International Character set support) ;; aslisp8 -I alisp8.dxl
;; Other UNIX (to run a case-sensitive image with ;; International Character set support) ;; mlisp ;; Other UNIX (to run a case-insensitive image with ;; International Character set support) ;; alisp ;; Other UNIX (to run a case-sensitive image without ;; International Character set support) ;; mlisp8 ;; Other UNIX (to run a case-insensitive image without ;; International Character set support) ;; alisp8
On Windows, start Allegro CL from the Start menu choosing a menu item that contains AllegroStore in it. On Windows only, Lisp needs special command line arguments for AllegroStore to work properly. See the command line in the shortcut for the AllegroStore menu items for details. You can choose to use either the International (mlisp or alisp) or non-International (mlisp8 or alisp8) versions to build your AllegroStore image.
If you would like to build a Lisp image with AllegroStore pre-loaded, then evaluate the following form in Lisp:
(build-lisp-image "[ACL directory]/astore.dxl"
:lisp-files '(:allegrostore))
This image can be started with the same executable used above, with
the arguments -I astore.dxl
Start Lisp as in Step 4. Then, evaluate the following forms:
(require :allegrostore) (load "[ACL directory]/astore/verify.cl")
If you are testing a client only installation, you must edit the verify.cl file. Change the two "averify.db" strings to a string naming a file in a directory that is on a disk that is local to an AllegroStore server. If such a directory is not available via a network mount, use the "host:dir" format described above in the AS_CONFIG_PATH description. Note that "host" need not be same host specified in the AS_CONFIG_PATH variable.
On IRIX, if you see an error that looks like:
ObjectStore internal error Fatal error Invalid argument(errno = 22) mmap failed: os_map_memory addr 0x74ee0000, len 0x1000, prot 3, fd 17, share 4 off 0x2000 (err_internal)
then you need to set the OS_16K_PAGE environmental variable, as detailed in Step 3.
On Windows, if you see an error message indicating that Ostore could not find a running server on your computer, run Start/Programs/ObjectStore Win32/ObjectStore Setup. Make sure you answer 'yes' when asked whether Ostore should reinitialize the server log file, 'yes' when asked whether Ostore should configure your computer to automatically start the server and/or cache manager, and 'yes' when asked whether Ostore should start the services 'now'. After exiting the Setup program, retry the AllegroStore test.
Versions of Emacs and Xemacs (collectively called Emacs) are supplied with the distribution as a convenience. These are copied from standard locations (identified in various readme files). Franz Inc. does not support Emacs or Xemacs. Both source and binary files are included.
CD One (with all UNIX Allegro CL distributions except FreeBSD and Linux Redhat 6) has an emacs/ subdirectory with Emacs versions for all UNIX platforms (including FreeBSD and Linux Redhat 6). CD Two (with Allegro CL for Windows and Allegro CL for HP-UX) has an emacs/ subdirectory with Emacs for Windows.
On CD One, the emacs/ directory has two subdirectories, source/ and unix-xemacs-binaries/.
The source/ subdirectory contains source trees (tarred up and compressed or zipped). Unpack them if desired. The contents are not needed to use Emacs.
The unix-xemacs-binaries/ contains three files:
Once you have untarred the correct emacs binary directory four your platform, additional readme files (usually with a longer name) in each binary directory (e.g. README.rs6000-ibm-aix-4.3.0.0 and README.sparc-sun-solaris2.6) provide installation instructions.
Once you have installed Emacs, see doc/eli.htm: this is the documentation file for the Emacs-Lisp interface. See particularly What should be in your .emacs file in that document for information on what to add to your .emacs in order to ensure the Emacs-Lisp interface code is loaded.
Allegro CL supports the Secure Socket Layer (SSL) protocol, as described in Secure Socket Layer (SSL) in socket.htm. The OpenSSL libraries are necessary to make use of this facility. The Allegro CL distribution contains versions of these libraries on the following platforms: Windows, Solaris, HP-UX (32-bit Lisp versions only), Linux (all varieties) and FreeBSD. These are the platforms where the libraries were available in shared library format at the time of release. There is also on each CD an openssl/ directory at the top-level of the CD which contains the sources.
In the directory associated with the platform on the appropriate cd, there is a openssl/ subdirectory. (If there is no such directory, the libraries are not supplied.) Note: if your Linux Redaht 6 or FreeBSD kernel does not support Joliet CD format, you may have problems installing the OpenSSL libraries. See 1.4 Warning to Linux Redhat 6 and FreeBSD users about long filenames on CD.
This directory contains a single file, openssl.tbz2 on all UNIX platforms where the libraries are supplied and openssl.exe for Windows. The libraries, when installed, have filenames aclssl and aclissl and extension dll on Windows, sl on HP-UX, and so on other UNIX platforms.
The openssl.tbz2 is a compressed tar file in the openssl/ subdirectory of the platform directory on the CD. Thus, for example, on CD One, solaris/openssl/openssl.tbz2 and hp11/openssl/openssl.tbz2 (and LinuxPPC, Linux Redhat 5, and HP-UX 10.20 -- note: not available on the HP-UX 11.0 64-bit Lisp version); and, on CD Two, redhat6/openssl/openssl.tbz2 (and FreeBSD).
To install, first select a target directory on your machine in which to store the files (/usr/local/openssl-0.9.5/ in our example), create that directory and extract the files, as shown in this example:
% mkdir /usr/local/openssl-0.9.5 % cd [cd dir]/[platform]/ % ./bunzip2 < openssl/openssl.tbz2 | (cd /usr/local/openssl-0.9.5; tar xf -)
On Solaris, for example, assuming the CD directory is /cdrom/cdrom0/, do
% mkdir /usr/local/openssl-0.9.5 % cd /cdrom/cdrom0/solaris % ./bunzip2 < openssl/openssl.tbz2 | (cd /usr/local/openssl-0.9.5; tar xf -)
If the copy of bunzip2 on the CD will not execute (some machines restrict running executables on CD's) see 4.1 What to do if bunzip2 won't execute on the CD for what to do.
Once the library has been installed, add the lib/ subdirectory of your selected directory to the Unix loaders search path. On Solaris and Linux the search path is stored in the LD_LIBRARY_PATH environment variable. On Hpux the environment variable SHLIB_PATH or LPATH is used.
You may also wish to add the bin/ subdirectory of to your shell's search path so you can access the openssl program that comes with the openssl libraries.
For Windows the libraries are stored in a self extracting .exe file found on CD Two in windows\openssl\openssl.exe. To install the libraries run openssl.exe and select a location with at least 3 megabytes of free space. Next run the System program in the Control Panel and edit your PATH variable to include the directory where you installed the openssl libraries.
Also on the distribution CDs are the following directories:
Note: there are two directories named doc/: [Allegro directory]/doc/ and [CD]/doc/. The first is is part of the distribution and contains the HTML documentation (and a few PDF files for which there are no HTML equivalents). The second is in on the CD and contains PDF files made from the documentation HTML files. These are provided as a convenience. You need not copy them from the CD if you do not wish to.
You must have a license file to use Allegro CL and its associated products, and to install ObjectStore if you are an AllegroStore customer. The license file is not on the CD.
Professional and Enterprise customers with current maintenance agreements should have received an email message from Franz Inc. with instructions on how to obtain their license file. Trial Edition customers should receive such an email after providing the necessary information to Franz Inc. (usually by filling in a form on the Franz Inc. web site, www.franz.com).
The email sent by Franz Inc. gives an URL from which the license file can be retrieved. The email is in Mime format, with plain text and HTML versions. If you are able to read mail in a mime-enabled client, you will be able to click on the URL immediately.
You should retrieve the license as soon as you receive the email, even if you have not received the distribution CDs. Then the license file will be ready when you install Allegro CL. The name of the file when it is put in the Allegro directory must be devel.lic. However, you may use any name when retrieving, renaming when you copy it to the Allegro directory later.
The license file is a text file which includes encrypted text. See The Allegro CL license file in startup.htm for a sample (with the encrypted text much and obviously modified).
If you upgrade your license or purchase add-on products, you will be sent email with instructions for retrieving a new license file. Placing the new license file in the Allegro directory is all you must do to use the upgraded version of the new add-on products (except users who add AllegroStore must install ObjectStore from the CD).
If you do not have a license file or the license file you have does not seem to license the correct product mix, contact your Account Manager for information. (That link goes to the file introduction.htm. If that link does not work, call Franz Inc. in Berkeley, California, at +1 510-548-3600 or send email to bugs@franz.com or info@franz.com. In email, be sure to identify yourself and provide information on how you can be contacted.)
The Trial edition, available for Windows, Freebsd, and Linux, is provided free of charge so that potential users may gain experience using Allegro CL and some add-ons before purchasing. The Trial edition is fully described on the Franz Inc. web site (www.franz.com, click on the Download button to see information about Trial software). That information may be updated more frequently than the information here. If there is a conflict between the information on the Web site and the information given here, the information on the Web site is correct.
To obtain a Trial edition, you typically fill out an information form on the Franz Inc. web site. Sometime after submitting the form, you will receive email with information on retrieving a license (see 10.0 Getting a license file) and information on downloading. The Trial edition is not available on a CD. It must be downloaded. The Windows version does not include the documentation (but instead links to the documentation on the Web site).
The license file you receive for the Trial edition will expire after 30 days. You can run the program newlicense in the Allegro directory to update your license file. newlicense can be run up to 7 days before their license expires, so timely action will result in no interruption of Lisp service. newlicense must be run in the Allegro directory.
newlicense updates your license by sending your current license to Franz Inc. An error message will be displayed if there are any problems. If the update succeeds, your license is updated.
The license can be updated five (5) times, for a total of six (6) months use. After five updates, newlicense will cease to work. contact your Account Manager or a Franz Inc. sales representative for information after five updates.
You must download the files associated with the Trial edition. Download into an empty directory on your machine. For Windows, a single file named something like acl60_trial.exe is downloaded. For Freebsd and Linux, two files, acl60_trial.bz2 and bunzip2 are downloaded.
Once the download has succeeded, follow the steps starting here in 4.0 Installation of Allegro CL on UNIX for Linux and Freebsd. follow the steps starting here in 5.0 Installation on Windows for Windows. In both cases, the CD directory is the directory you downloaded into, not the CD drive on your machine.
Copyright (c) 1998-2000, Franz Inc. Berkeley, CA., USA. All rights reserved. Created 2000.10.5.