![]() Mation on how to end your adventure, etc., type "INFO".) (Should you get stuck, type "HELP" for some general hints. ![]() Have to enter "NORTHEAST" as "NE" to distinguish it from "NORTH". You that I look at only the first four letters of each word, so you'll Treasure and gold, though it is rumored that some who enter are never Somewhere nearby is Colossal Cave, where others have found fortunes in Welcome to Adventure!! Would you like instructions? ( Here's a video of the PDP-11/34 booting RT-11 v4 of the RK05 decpack and running ADVENT) If you compile with /ONDEBUG, advent will print as it builds the cache: To save time at startup, the ATEXT.TXT file is pre-processed into ATEXT.DAT and AINDEX.DAT by ABUILD.FOR. LINK/PROMPT ADVENT,ASUB,AIOSUB,ASUSP,AMAC COMPIL/NOVEC ADVENT,AINIT,ASUB,AIOSUB,ASUSP COPY XAA.TXT+XAB.TXT+XAC.TXT+XAD.TXT+XAE.TXT+XAF.TXT ATEXT.TXT Compiling source files After copying the six files, I recombined them: There is probably a way to use EDIT to do this. To reduce the size of the FORTRAN IV files, I removed all comment and blank lines, and I used /usr/bin/split to break the still-too-large files ( ATEXT.TXT and AMAIN.FOR) into smaller chunks and transferred the individually. If you copy in too much data, EDIT unhelpfully says "INSUFFICIENT MEMORY" with you hit the double escape. However, the RT11 v4 added an EDIT command that seems to cope quite well up to about 6000 baud. The copy command appears to be too slow to keep up with 1200 baud, much less 9600 baud. However, on the real hardware using COPY TT: FOO.TXT won't work. Repeat for ABUILD.FOR, ADVENT.FOR, AIOSUB.FOR, AMAIN.FOR, ASUB.FOR, ASUSP.FOR, AMAC.MAC and ADVENT.ODL Using EDIT/CREATE ![]() Tiny:~/simh: unzip adv350kp.zip RT11SRC.ZIP ![]() Then attach each file in turn to the PC: device and copy the text from it.ġ00 220k 100 220k 0 0 368k 0 -:-:-:-:-:-:- 472k Sources are available from Rick Adam's Colossal Cave page. Transferring source files With simh using PC: * 1=OUP:FORLIB=INP:NHD,OTSCOM,NOVIR,V2NS/G Sim> att rx0 fortran-iv-v021-objecttime-system.img The inline compiler can optimize for SPEED or for SIZE. Or it can produce threaded (THR) code which is hardware independent. Statements are currently compiled for the following system: RT-11įORTRAN can produce inline code for EAE, EIS or FIS hardware, Statement keywords for RT-11, RSX-11, and RSTS/E systems. The FORTRAN compiler can compile system-specific OPEN and CLOSE YES(Y) for affirmation, anything else for NO.Ī maximum of 56 lines are allowed per listing page.Ī maximum of 136 characters are allowed in a formattedĪ maximum of 6 channels may be open at a given time. "?" or carriage return ( ) for information, LA36 DECwriter II and VT52 DECscope terminals Modify location 56 with a Deposit command before proceeding with If you are using a terminal that requires fill characters, Please use the HELP command it describes the new options in many ![]() RT-11 V04 provides new hardware supportĪnd some major enhancements over Version 3B. Sim> attach rx0 fortran-iv-v021-compiler-files.img These instructions are copied from computing history wiki. To transfer them to a simulated PDP-11, you can use the PC: trick described in simh. You will need ADVENT.SAV, AINDX.DAT, ATEXT.TXT and ATEXT.DAT. If you don't want to build the FORTRAN IV compiler, you can download the pre-built executables from /osresearch/advent. This is a transcript of how to setup simh on a simulated PDP-11, generate a working FORTRAN IV compiler, transfer the original ADVENT source code into the simulator or real PDP-11 hardware, build it and play Colossal Cave Adventure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |