Falcon Application RT-11 (FART-11) John M. Crowell Crow4ell,Ltd* 145 Andanada Los Alamos, NM 87544 * but not very COPYRIGHT (C) NOT-AT-ALL This software is furnished under license for use on any computer system and may be copied with or without inclusion of this notice. This software, or any other copies thereof, may be provided or otherwise made available to any other person. Title to and ownership of the software shall at all times remain in the public domain. The information in this software is subject to change without notice, and should not be construed as a commitment by the author or by Crow4ell, Ltd. I understand the Digital Equipment Corporation can't be blamed either. The author assumes no responsibility for the use or reliability of this software on equipment which is not supplied by someone. This diskette contains TECO command files which will perform sufficient modification of RT-11 Version 4.0 source files to enable generation of an RT-11 system (SJ or FB) called FART-11 to run on the SBC-11/21 FALCON microcomputer. Why anyone would actually WANT to run RT-11 on a FALCON is quite beyond me. If you choose to run FART-11 on your FALCON, it is up to you to see that the CPU is properly licensed. None of the files on this diskette represent a breach of contract or or contain proprietary code. The author will assume neither responsi- bility nor liability for anyone who attempts to use FART-11 on an unlicensed FALCON. Page 2 Once the source files have been modified, they may still be used to generate "normal" RT-11 systems. All FALCON specific code is assembled conditionally depending upon values of flags in the file SYCND.MAC. I have tested the procedure for BL, SJ, and FB monitors in memory mapping MODE 0, and, via a hardware kludge, MODE 3. No attempt has been made to generate a MRRT system with this procedure. No attempt has been made to generate a multi-terminal system. New variables and conditionals show up in the file SYCND.MAC. These include: FART$$ A conditional assembly flag RAMSIZ A variable to specify the size of memory of the target system BEVENT A conditional assembly flag to denote that the FALCON clock is to be the system clock AUTO$B A conditional assembly flag to signify that the programmable baud rate of the FALCON's SLU1 is to be utilized. BAUD$$ A variable to specify the baud rate to be selected. If when booting RT-11, the programmable baud rate enable bit is set in the CSR of SLU1, the baud rate will not be changed. (e.g. if the baud rate was set by the primary bootstrap or by the MACRO ODT ROMs available for the FALCON.) If the "autobaud" option is selected, and is not enabled at bootstrap time, the baud rate will be set by the secondary bootstrap program. The system configuration words are set to reflect the presence of an LSI-11 processor and, if appropriate, the presence of a system clock. The second configuration word is cleared. (Who would run a VS60 on a FALCON anyway?) There is also a patch for the file SYSGEN.CND which will include the FALCON options in the sysgen process. It will cause the appropriate entries to be made in the SYCND.MAC and MONBLD.COM files. If you must have FART-11, this is the recommended procedure. The TECO programs on this diskette assume that the source files to be patched reside on a volume named SRC:. If all the source files and TECO files are present on one volume, and the MUNG command is supported, the entire patch may be accompliched by invoking the FART11.COM indirect command file. One final comment concerning the final operating system generated by this procedure: The utility program RESORCE.SAV tries to use nonexistent memory traps to identify some of the possible devices on the Q-bus. Since the FALCON does not execute these traps, configuration of the system is likely to reflect some things that may not be there, such as parity memory or a VT48 graphics device.