Installing FORTRAN v2 on RT-11 - Revision history

Neozeed: /* Disk 1 */

2009-10-11T15:57:25Z

Disk 1

← Older revision		Revision as of 15:57, 11 October 2009
Line 24:		Line 24:

	== Disk 1 ==		== Disk 1 ==
	And to install fortran I first attach fortran-iv-v021-compiler-files.img to rx0 in simh's console then from ts-11		And to install fortran I first attach fortran-iv-v021-compiler-files.img to rx0 in simh's console then from ts-11. Hit Control+E to interrupt the emulator.
			<pre>
			Simulation stopped, PC: 151262 (ADD #20,R1)
			sim> att rx0 fortran-iv-v021-compiler-files.img
			RX: buffering file in memory
			sim> c
			</pre>

			Then follow the next steps...
	<pre>		<pre>
	.ASSIGN RK0: OUP		.ASSIGN RK0: OUP

Neozeed: /* Verifying the installation */

2009-10-11T15:56:24Z

Verifying the installation

← Older revision		Revision as of 15:56, 11 October 2009
Line 121:		Line 121:
	.MAIN.		.MAIN.

	.LINK DEMO		.LINK DEMO,FORLIB

	.RUN DEMO		.RUN DEMO

Neozeed: /* Disk 2 */

2009-10-11T15:55:30Z

Disk 2

← Older revision		Revision as of 15:55, 11 October 2009
Line 94:		Line 94:
	== Disk 2 ==		== Disk 2 ==
	(then swap rx0 to fortran-iv-v021-objecttime-system.img)		(then swap rx0 to fortran-iv-v021-objecttime-system.img)
	This will build the fortran library ~~into the~~ system ~~library~~ to ~~simplify linking.~~		This will build the fortran library.
			Hit Control+E to interrupt SIMH:
			<pre>
			Simulation stopped, PC: 151256 (BCC 151310)
			sim> att rx0 fortran-iv-v021-objecttime-system.img
			RX: writing buffer to file
			RX: buffering file in memory
			sim> c
			</pre>

	<pre>		<pre>
	.R LIBR		.R LIBR
	*OUP:~~SYSLIB~~=INP:NHD,OTSCOM,NOVIR,V2NS/G		*OUP:FORLIB=INP:NHD,OTSCOM,NOVIR,V2NS/G

	Global? $ERRS		Global? $ERRS

Neozeed at 14:52, 11 October 2009

2009-10-11T14:52:42Z

← Older revision		Revision as of 14:52, 11 October 2009
Line 1:		Line 1:
	This is more of a follow through on building the FORTRAN install on [[TS-11]] on [[SIMH]]..		This is more of a follow through on building the FORTRAN install on [[RT-11]] on [[SIMH]]..

Neozeed: lame inital version

2009-10-11T14:52:24Z

lame inital version

New page

This is more of a follow through on building the FORTRAN install on [[TS-11]] on [[SIMH]]..

== REQUIREMENTS ==
You will want the following files:
*http://www.headcrashers.org/comp/rx01/fortran-iv/fortran-iv-v021-compiler-files.img
*http://www.headcrashers.org/comp/rx01/fortran-iv/fortran-iv-v021-objecttime-system.img
I've been using RT-11 v4 from here:
*http://simh.trailing-edge.com/kits/rt11swre.tar.Z

== SIMH Setup ==
When I run SIMH, this is what I get for "show cpu"
CPU, 11/73, NOCIS, idle disabled, autoconfiguration enabled, 256KB

This is my ini file:
<pre>
set cpu 256k
att rk0 rtv4_rk.dsk
att rk1 dungeon1.dsk
att rk2 dungeon2.dsk
att rk3 asc.dsk
</pre>

== Disk 1 ==
And to install fortran I first attach fortran-iv-v021-compiler-files.img to rx0 in simh's console then from ts-11
<pre>
.ASSIGN RK0: OUP
.ASSIGN DX0: INP
.R PIP
*SY:*.*=INP:FORTRA.HLP,DEMO.FOR
*^C
.RUN INP:FORGEN

Answer questions with:
"?" or carriage return (<CR>) for information,
YES(Y) for affirmation, anything else for NO.

A maximum of 56 lines are allowed per listing page.
Is this acceptable? Y
A maximum of 136 characters are allowed in a formatted
(ASCII) record. Is this acceptable? Y
A maximum of 6 channels may be open at a given time.
Is this acceptable? Y
The FORTRAN compiler can compile system-specific OPEN and CLOSE
statement keywords for RT-11, RSX-11, and RSTS/E systems. These
statements are currently compiled for the following system: RT-11
Is this acceptable? Y
FORTRAN can produce inline code for EAE, EIS or FIS hardware,
or it can produce threaded (THR) code which is hardware independent.
Should the compiler produce EAE code? N
Should the compiler produce EIS code? N
Should the compiler produce FIS code? N
Should the compiler produce THR code? Y
The inline compiler can optimize for SPEED or for SIZE. These
optimizations are mutually exclusive. Do you want
the optimization to be for SPEED? NO

Do you wish a threaded only compiler? Y
Compiler options selection complete.

.
.@INP:F4LTHR

.R LINK
*OUP:FORTRA=INP:FROOT///S
*INP:F0,INLINE,OUP:DEFLTS/O:1
*INP:F1/O:1
*INP:F2/O:1
*INP:F3/O:1
*INP:F4/O:1
*INP:F5/O:1
*INP:F6/O:1
*INP:F7/O:1
*INP:F8/O:1
*INP:F9/O:1
*INP:F10/O:1
*INP:LOOP/O:1
*INP:F11/O:1
*INP:F12/O:1
*INP:F13/O:1
*INP:F14/O:1
*INP:F15/O:1
*INP:F16/O:1
*INP:F17/O:1
*INP:CDUMP/O:1//
*^C

.
</pre>

== Disk 2 ==
(then swap rx0 to fortran-iv-v021-objecttime-system.img)
This will build the fortran library into the system library to simplify linking.
<pre>
.R LIBR
*OUP:SYSLIB=INP:NHD,OTSCOM,NOVIR,V2NS/G

Global? $ERRS
Global? $ERRTB
Global? $VRINT
Global?
*^C
</pre>

== Verifying the installation ==
Then to build the Fortran test program to verify your kit is working:
<pre>
.COMPILE DEMO.FOR
.MAIN.

.LINK DEMO

.RUN DEMO
***** RT11 FORTRAN IV V2 DEMONSTRATION TEST *****

INSTALLATION SUCCESSFUL IF NO ERROR MESSAGES
WERE PRINTED ABOVE.

**** FORTRAN DEMONSTRATION TEST COMPLETE *****
.
</pre>

[[Category:Tutorials]]