30 Apr
1999
30 Apr
'99
2:20 a.m.
Ok, I have managed to assemble and link a program!
.R MACRO
*DEMOFG.OBJ,DEMOFG.LST=DEMOFG.MAC
BTW - the file types (formerly called extensions) are defaulted
based on position in the command line. So:
.R MACRO
*DEMOFG,DEMOFG=DEMOFG
is equivalent to the above...
The RT Utilities use something called CSI (command string
interpreter) which has a standard form... up to 3 output files
(the ones to the left of the '=') and up to 6 input files
(the ones to the right of the '=').
For MACRO, the output files are objects, lists and symbol
table (in later versions). And the 6 input files are all
expected to be .MAC
results in the expected listing and object file
(I'm glad Gary Kildall
modelled CP/M after RT-11!)
It sure does look that way, doesn't it... :-)
Then I linked it with
.R LINK
*DEMOFG.SAV=DEMOFG.OBJ,ODT.OBJ
Same as above comments here, only the defaults are: .SAV image,
.MAP file for outputs, and up to 6 .OBJs for input.
Then I ran it with
.R DEMOFG
and it ran, popped into ODT which I continued out of and exited 'cuz the
background program wasn't running.
To run a foreground program, you issue the command FRUN <program_name>
OK. So we're almost cooking, but it raises some
interesting questions:
1) I can compile on the other disk by preceding the names
with DX1: in the assmbler line.
Or you could ASSIGN DX1 DK, and then R MACRO and specify the
command line without device specifications.
Typically, one would boot from one device, then ASSIGN the other
device as DK (default disk) on which all new files would be
created if not otherwise specified, and from which all input
files would be taken, again unless otherwise specified.
2) How can I run a program on DX1: ? If I type .R
DX1:PROG
it says ?ILL-CMD?
The 'R' command is used for running programs/utilities specifically
from the system device 'SY' (the boot device).
To run a program
from another disk, you can either do 'RUN' with no device specified
to have
it run from DK:, or 'RUN dev:program' to run 'program' from
'dev:'
3) Which side of the disk is the directory on? (inner
or outer
tracks?)
The directory for all RT-11 volumes is a contiguous set of blocks
starting with block 6. It consists of two blocks per segment for
as many segments as have been specified in the PIP dev:/Z[:n]
command (up to 31). Each segment can specify up to 72 files. So
for one segment, the directory is in blocks 6 and 7. The first
file data block is block 010.
The last question relates to the disk problem I'm
seeing. My guess is
that write precompensation is screwed up on that disk which would explain
why it works until it writes the directory.
Sorry, can't answer that one...
Megan Gentry
Former RT-11 Developer
+--------------------------------+-------------------------------------+
| Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry!zk3.dec.com |
| Unix Support Engineering Group | (home): mbg!world.std.com |
| Compaq Computer Corporation | addresses need '@' in place of '!' |
| 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ |
| Nashua, NH 03062 | "pdp-11 programmer - some assembler |
| (603) 884 1055 | required." - mbg |
+--------------------------------+-------------------------------------+