Since my CDROM drive is currently broken, the only supported compiler is SAS/C V5.10b. It might seem that GNU-C is supported as well, but it isn't (for now). SAS/C V5.10b has various problems; among them is the serious restriction of the command line length. In order to recompile mris, your global SASCOPTS variable should set the following options: -n64 The following non-standard tools are required to build mris: GNU-make 3.72.1 (Make) SAS/C V5.10b (C-Compiler) blink V5.10b (Linker) oml V5.05 (Librarian) Additionally, GNU-make seems to be using a shell which identifies itself as KSH_VERSION=@(#)PD KSH v4.9 93/09/29 I have no idea where I got that from (besides that, it doesn't work very well). You might need to fiddle the makefile if you want to use other tools. Also, the makefile is somewhat kludgy, since for some reason I couldn't get filenames with spaces in them (the "mris gardens/#?" stuff) to work properly. ---------------------------------------------------------------------- You'll need the gamesupport.library distribution as well. Somewhere on Aminet... ---------------------------------------------------------------------- Now some comments about the sources. mris does not use the (link-) libraries supplied by the compiler vendor. Since my own libraries are not in a state that would allow a release, I decided to just create "mini libraries" that only contain the few functions that mris uses. This is what the stuff in MyLib/ and BOOPSILib/ is for. Also, building mris is somewhat different from building Xmris, because mris doesn't get the sprites compiled into the executable. Instead, the CreateSprites program uses the sources created by scram, and creates lots of IFF-ILBM files with the sprite images. These files are concatenated to form the final sprite files. ---------------------------------------------------------------------- If you have looked at the installer script, you might have noticed that some things are solved in a rather kludgy way. The reason for this is that, for some reason, I couldn't get various functions such as shiftrght, shiftleft, bitand and others to work. Since the Installer program is generally quite buggy, it might be a problem with the Installer. ---------------------------------------------------------------------- Christian Stieber