We will use as an example the installation for HP 9000 series 400 computers. The installation for other Unix systems is similar. If you are installing for an HP 9000 series 700 or 800, see also section HP-PA Installation.
MIT Scheme is distributed as a compressed `tar' file. The tar file contains a single directory, called `dist-7.3', and that directory contains subdirectories `bin', `etc', and `lib'. The `bin' subdirectory contains two executable files, `scheme' and `bchscheme'. The `etc' subdirectory contains several files that are used during the installation process. The `lib' subdirectory contains several files and subdirectories that Scheme uses while it is executing.
The goal of the installation is to put the executable files in a directory where they will be executed as commands, and to put the library files in some convenient place where Scheme can find them.
gzip -cd hp400.tar.gz | tar xvf -If you do not have the `gzip' program: we have built executables of this program for each of the machines that we support. Either use the executable that we have already built, or else get the gzip sources (from us or from numerous other sources) and build it yourself.
cd dist-7.3The easiest way to install the files is to use the "install.sh" shell script that we've provided in the distribution. You will need to edit that script to tell it where and how you want Scheme installed. If you want to do something more complicated, or if the script can't easily be made to work for your system, use the script as a guide to installation.
schemeat the command line (if you use the C shell, you may have to type `rehash' before `scheme' will be recognized).
If you are using an HP 9000 series 700/800 computer (often called an HP Precision Architecture machine, or HP-PA for short), read this section.
Scheme has built-in code that flushes the instruction and data caches of your machine in certain circumstances. This code is sensitive to your computer's model, because each model has different cache hardware.
This distribution contains a database, called `hppacach.mod', that describes the cache structure for each model of computer. As of this writing, that database contains entries for the following models:
705, 710, 715, 720, 730, 735, 750, 755, 834, 835, 850, 867
If you have a model that is not in the database, Scheme will not run -- instead it will print an error message informing you of this fact, and stop. If this happens, you must add an entry to the database. This must be done once, at installation, for each new model.
Here is the procedure for updating the database:
cd /usr/local/lib/mit-scheme ./hppacache -update hppacach.modThe reason that you must be super-user is that `hppacache' needs to read the device `/dev/kmem' to get the information that it needs. Normally, `/dev/kmem' is readable only by the super-user, or by users in group
sys. Thus, becoming super-user is the easiest way to read this information. An alternative method for doing this is to change the permissions of the `hppacache' program so that it is in group
sys, and to turn on its "set group ID on exec" permission bit, but since this also requires you to be super-user, you might as well just execute the program as the super-user. Please note that you must execute this program on the computer whose model you wish to add to the database. Also, if you wish to add several models to the database, you must execute the program once on each model. If you have several computers that are all of the same model, you need only update the database once from one of the computers; thereafter all of the other computers of that model will work.
cd /usr/local/lib/mit-scheme ./hppacache -print hppacach.mod > model-7xx(If you have previously updated the database, you do not need to be super-user to execute this command.) The resulting file, `model-7xx' in this example, is the model information for the machine that you executed the command on; it is C code that we can use to update our copy of the database. Send the model information for each new model to us by electronic mail at
This section describes how to install MIT Scheme on DOS, Windows 3.1, and Windows NT. We would prefer that the Windows version be used, rather than the DOS version, because we intend to maintain the DOS version only so long as it is convenient. For the most part the installation on any of these platforms uses the same files, and the procedure is similar. It is possible to install MIT Scheme so that it will run under all three operating systems on one computer, but this does require some care with the configuration of the system.
Note that we have only tested the DOS version on Microsoft DOS 5.0.
MIT Scheme requires at least a 386SX with 8Mb RAM. The bare minimum disk space required is 5.5Mb, which gives you a command line interface for Scheme. We strongly recommend a more advanced environment. To build the Edwin editor band requires an additional 4.3Mb. The whole installation without source code occupies 36Mb of disk.
The installation is split into several files according to functional units and the size constraints of a 1.4M high density 3.5" floppy disk. The following files are distributed:
BIN.ZIP Scheme binaries for Windows 3.1/Windows NT DOSBIN.ZIP Scheme binaries for DOS LIB.ZIP Smaller files from Scheme library RUNTIME.ZIP `runtime.com' band RUNNOFLO.ZIP `runtime.com' band for DOS machines with no FP hardware EDDEL.ZIP `eddel.com': a kit to build `edwin.com' band COMPDEL.ZIP `compdel.com': a kit to build `compiler.com' band HELP.ZIP WinHelp User and Reference Manuals BCIRUN1.ZIP Debugging information for runtime system BCIRUN2.ZIP " " " " " BCIRUN3.ZIP " " " " " BCIED1.ZIP Debugging information for Edwin BCIED2.ZIP " " " " BCIED3.ZIP " " " " BCINOFLO.ZIP Extra debugging information for machines with no FP hardware SRCRUN.ZIP Source code for the runtime system SRCUC.ZIP Source code for the microcode (C) SRCED.ZIP Source code for Edwin SRCCOMP.ZIP Source code for i386 compiler WIN32S.ZIP Win32s installation floppy from Microsoft INSTALL.TXT These instructions UNZIP.EXE Program to unpack the `.zip' files
Minimal installation on Windows NT requires: `BIN.ZIP', `LIB.ZIP' and `RUNTIME.ZIP'.
For the Edwin editor and the native code compiler add `EDDEL.ZIP' and `COMPDEL.ZIP' repectively.
Any configuration for Windows 3.1 is the same as for Windows NT except that Win32S also needs to be installed.
For DOS the minimal installation comprises `DOSBIN.ZIP', `LIB.ZIP' and one of `RUNTIME.ZIP' or `RUNNOFLO.ZIP'.
These installation instructions describe how to install MIT Scheme on one or more of DOS, Windows 3.1, and Windows NT. If you are installing for DOS and another operating system, you should do the bulk of the installation using the windowing environment.
In each of the following steps the amount of disk space consumed is indicated in square brackets. These sizes do not include the `.zip' files which are required only during installation.
a: unzip wherever\win32s.zipRun the `setup' command on the floppy disk. If you are not sure whether you have Win32s installed, or what version you have installed, try to install it anyway. If you have version 1.0 then the Win32s installation disk will upgrade your Win32s system to version 1.1.
mkdir c:\scheme cd \schemescheme is the string `
unzip wherever\bin.zip unzip wherever\lib.zip unzip wherever\runtime.zipThis will create the directory structures `scheme\bin', `scheme\lib' and `scheme\etc', and unpack the essential files. (Wherever stands for the place that you have put the `.zip' files, which might be another directory or a floppy disk.) If you have a computer without floating-point hardware (e.g. a 386 machine or a 486SX) and you wish to run the DOS version then you must install the runtime with special floating point support instead of `runtime.zip':
unzip wherever\dosbin.zipThis creates a `scheme\dos-bin' directory containing the DOS versions of the `.exe' files. These files are different from the Windows versions, so they are placed in a different directory to allow both versions to co-exist on your computer. It is only the `.exe' files that differ between DOS and Windows. The other parts of the MIT Scheme system are shared. The DOS version will run under Windows 3.1 but not under NT. Either running on DOS or Windows 3.1, the DOS version has no graphics support
path %PATH%;scheme\bin\win31This command must be in a `.bat' file to work
PATHin the system environment (using the Registry Editor,
\bin\ntin your environment (use the control panel's system option
PATHrather than copying files, i.e. you must arrange for Windows 3.1 to be run with `scheme\bin\win31' on the path and for Windows NT to be run with `scheme\bin\nt' on the path. This can be done by putting
path %PATH%;scheme\bin\win31in the `autoexec.bat' file and adding `scheme\bin\nt' to the Windows NT system environment path.
scheme\bin\schemeFrom DOS you should be able to get Scheme running by typing the following at the DOS prompt:
scheme\dos-bin\schemeIf there are any problems at this stage, review the installation so far. Remember that you might have to restart your machine to get the effect of any changes that you made in `autoexec.bat' or the NT registry.
scheme\bin\scheme -load scheme\etc\pmgrpThis program creates a program group called `MIT Scheme' which contains
unzip wherever\help.zipThis installs two windows help files, `user.hlp' and `scheme.hlp', in `scheme\bin'.
cd scheme unzip wherever\eddel.zipTo build `edwin.com' start the `build EDWIN.COM band' icon, or run the following command:
scheme\bin\scheme -large -load scheme\etc\build -eval (edwin.com)This will load in `eddel.com' and create the new band [4.3Mb]. After a successful build the program will exit. The `edwin.com' band can be used by both the DOS and Windows versions, so you only need to do this step once, even if you are installing for more than one of DOS, Windows 3.1, and Windows NT. If you are installing only for DOS you will have to build `edwin.com' from the command line. Be sure to run the DOS `scheme.exe' rather than the Windows version:
scheme\dos-bin\scheme -large -load scheme\etc\build -eval (edwin.com)
cd scheme unzip wherever\compdel.zipTo build `compiler.com' start the `build COMPILER.COM band' icon, or run the following command:
scheme\bin\scheme -large -load scheme\etc\build -eval (compiler.com)This will load in `compdel.com' and create the new `compiler.com' band [4.8Mb]. After a successful build the program will exit. As for Edwin, this step needs to be done only once. If you choose to build this band using the DOS version be sure to run the DOS `scheme.exe' rather than the Windows version:
scheme\dos-bin\scheme -large -load scheme\etc\build -eval (compiler.com)
cd scheme unzip wherever\eddel.zip unzip wherever\compdel.zipTo build `all.com' start the `build ALL.COM band' icon, or run the following command:
scheme\bin\scheme -large -load scheme\etc\build -eval (all.com)This will load in both `eddel.com' and `compdel.com' into the runtime band and create the new band [6.7Mb]. After a successful build the program will exit. If you choose to build this band under DOS, be sure to run the DOS `scheme.exe' rather than the Windows version:
scheme\dos-bin\scheme -large -load scheme\etc\build -eval (all.com)
schemecopy the icons and edit the command lines to change `scheme' to `bchschem' (that is right: no tailing `e').
MITSCHEME_INF_DIRECTORYenvironment variable to this directory. `bcied1.zip' through `bcied3.zip' [3.8Mb installed] hold the debugging information files for Edwin.