This version of adventure is based on the RT-11 version by Bob Supnik. It is essentially a recoding of the FORTRAN-IV sources into RALF code. The RALF code has been optimized to fit into 32K. Also, many modifications were made to the code to increase execution speed. Because it is based on the RT-11 version of ADVENTURE, the following features of the FORTRAN-10 version are not supported: 1) MAGIC mode was removed 2) The HOURS command was deleted This program is an update of the original ADVENT submitted. It allows the text to be output in upper or lower case, and has a 128 character keyboard typeahead buffer. It also allows the game to be suspended and resumed later. The program requires a secondary storage device with at least 145 blocks of free space for working storage. Included with the sources are batch stream files for compiling and loading the program. COMPILATION: .SUBMIT COMPILE LOADING: .SUBMIT LOAD (this creates a load map - LOAD.LS) EXECUTION: .R FRTS *ADVENT.ld (the ".LD" is optional) *dev:ADVENT.TX/1(where "dev" is the device where "ADVENT.TX" resides.) *dev1:ADVENT.DA/2< (the secondary text storage file) *$ (altmode or escape) execution proceeds. When started, the program will take approximately two to three minutes to set up its data base (ADVENT.DA). Initialization and execution can be optimized by placing the data file (ADVENT.DA) on a different device from the text file (ADVENT.TX). Also, it is more efficient to have the load module (ADVENT.LD) on a different device than the data file (ADVENT.DA). For a two-drive DECtape system, for example, put ADVENT.LD and ADVENT.TX on SYS:, have ADVENT.DA written on DTA1:. i.e. .R FRTS *ADVENT *ADVENT.TX/1 !Initial text file *ADVENT.DA/2 !Internal text file *$ .SAVE SYS ADVENT !Save the game .R ADVENT !And play. When the program is done initializing, it will return to the monitor, which will be indicated by the monitor dot. Save the current core image (which will take 129 blocks.). This program can then be run at any time to play adventure. To stop your adventure for a time, give the SUSPEND or PAUSE commands. The program will return to the monitor, and allow you to save the image again to allow restarting. For example, SUSPEND (Given to ADVENT) .SA SYS ADV !Save the game . . . .R ADV !Re-run it. If the game is suspended, the location of the data file ADVENT.DA MUST not change before re-starting. It is advisable to have it as the first file on a device to maintain its position. If the file is not where ADVENTURE expects it to be, the messages output will be trash. Simply quit with control c and resume after correcting the problem. Also, the hardware configuration on which the game is saved must be present on the machine on which it is run. For example, if ADVENT is saved on a machine with EAE or FPP, it must be run on a machine with that hardware. The reverse is not true. A copy of ADVENT saved on a machine with no special hardware will run anywhere (but not as efficiently as it could). To run the program, only the files ADVENT.LD and ADVENT.TX need to be copied from the distribution tape. These are the load module and the text file. The rest of the files are sources. Good luck and happy adventuring!