1
0
mirror of https://github.com/PDP-10/its.git synced 2026-03-07 19:40:48 +00:00

Add documentation in MIDAS directory.

This commit is contained in:
Lars Brinkhoff
2017-02-05 15:01:21 +01:00
committed by Eric Swenson
parent 4b061741b0
commit c7d4f5d0f1
5 changed files with 10176 additions and 0 deletions

6
doc/midas/-read-.-this- Executable file
View File

@@ -0,0 +1,6 @@
THIS DIRECTORY IS NECESSARY FOR THE SPEEDY AND PROPER
PREPARATION OF MAGTAPES WHICH WILL CARRY MACLISP AND MIDAS
SYSTEMS TO OTHER PDP10 INSTALLATIONS. PLEASE DO NOT TAKE IT
UPON YOURSELF TO DELETE THE FILES IN THIS DIRECTORY.

BIN
doc/midas/ideas.30 Executable file

Binary file not shown.

118
doc/midas/info.mins Executable file
View File

@@ -0,0 +1,118 @@
Received: from MIT-JIMI by MIT-MC via Chaosnet; 1 JUN 85 18:49:39 EDT
Date: Sat, 1 Jun 85 18:48 EDT
From: David Vinayak Wallace <Gumby@MIT-MC.ARPA>
Subject: new midas for twenex
To: info-midas@MIT-MC.ARPA
Message-ID: <850601184814.1.GUMBY@JIMI>
Twenex Midas now kills itself (via PRARG) when done. I think this will
only affect MIT users, but if any other site's exec recognises the same
PRARG options, ftp the file oz:ss:<sys.midas>TSRTNS.MID.232.
david

Mail-From: KLH created at 4-Oct-83 13:49:28
Date: Tue 4 Oct 83 13:49:27-PDT
From: Ken Harrenstien <KLH@SRI-NIC>
Subject: Re: Midas improvements.
To: G.EGK@SU-SCORE, info-midas@MIT-MC
cc: KLH@SRI-NIC
In-Reply-To: Message from "Edjik <G.EGK@SU-SCORE.ARPA>" of Sun 2 Oct 83 17:15:13-PDT
ReSent-date: Thu 13 Oct 83 00:21:40-PDT
ReSent-from: Ken Harrenstien <KLH@SRI-NIC>
ReSent-to: info-midas@MIT-MC
MIDAS does have this ability (FOO=BAR"), however it (and many other
such features) exist only for the ITS STINK relocatable format, rather
than the LINK format. I am looking at what would be required to
provide functionality similar to STINK, but this is somewhat difficult as
there are a bunch of things that STINK format allows, which LINK doesn't,
so it requires really understanding what is going on in order to let only
the LINK-allowable things happen. The person who did .DECREL originally
took the easy way out by requiring things to be assembled more or less
pseudo-absolutely. I haven't given up, but it's tough going as very
little of the STINK format is documented. Fortunately a lot of it is
extremely similar to LINK, and they are doubtless related far back in
the dim past.
-------

Date: Sun 2 Oct 83 00:25:46-PDT
From: Edjik <G.EGK@SU-SCORE.ARPA>
Subject: Midas improvements.
To: info-midas@MIT-MC.ARPA
One thing I've noticed MIDAS missing that MACRO has, is the ability to
have external symbols in equals (=). This is quite handy and makes
writing modules easier. Dunno how hard it would be to make MIDAS
generate the appropriate LINK record but it probably is worth it.
--E+
-------

Date: Wed 28 Sep 83 18:12:33-PDT
From: Ken Harrenstien <KLH@SRI-NIC>
Subject: Some questions
To: info-midas@MIT-MC
cc: klh@SRI-NIC
I have a few questions about some things I found in the MIDAS BUGS
file. I seem to be in a mood to fix them, depending on the kind
of answers I get...
1. .FAS or .FASL?
Some people claim that on TOPS-20, output files generated with
the .FASL pseudo-op should have the extension .FASL rather than .FAS.
Is this true? Is this also true for TENEX?
2. TOPS-20 CCL?
This purportedly no longer works for V3+. Where do I find
out how it should work? Should compatibility with V2- be retained?
3. MIDAS .INSRT library?
I would like to provide a system-independent way of allowing
programs to .INSRT commonly used files. For this purpose I am thinking
of adding a new pseudo called .INSLIB which would act exactly like
.INSRT with the difference that the device/directory names would default
to a place containing standard, public, or useful MIDAS .INSRT
packages. This place can be defined on a per-system basis. If it was
ever desired to change these defaults for a single assembly, this
could be done by giving an .INSLIB specification with an explicit
device/directory and no filename. Comments welcomed.
4. Others?
If you have some ideas which have never been sent to
BUG-MIDAS, now is a good time, not because I plan to try doing
anything but because I am interested in seeing whether other people
have found undocumented bugs or have hidden wish lists. I have a
loooong list of MIDAS ideas as well as bugs, which will be available
in MIDAS;IDEAS > (plus MIDAS BUGS), for those who care to avoid
reiteration. The usual warning: very few such items ever
get implemented.
-------

Date: 27 September 1983 13:44 EDT
From: Ken Harrenstien <KLH @ MIT-MC>
Subject: Mailing list on OZ...
To: Ian @ MIT-OZ
cc: INFO-MIDAS @ MIT-MC
Yes, merge it (you can just point to it if you want to keep an OZ-specific
group)...
Latest version of MIDAS (not back on MC yet) fixes the various
problems with building new MIDASes. I am currently
scanning MIDAS BUGS (archive of bug-midas mail) to see if there
are any interesting things that are easy to add before installing
it.

Date: 27 Sep 1983 03:29 EDT (Tue)
Message-ID: <[MIT-OZ].IAN.27-Sep-83 03:29:17>
From: Ian Macky <Ian@MIT-OZ>
To: Info-MIDAS@MIT-OZ
Subject: Mailing list on OZ...
There's this list here... maybe it should be merged? It's mostly to do
with 20-only stuff, usually OZ-only, like new packages and junk.
MIDAS-USERS=Ian Jeh ZZZ Marty *SS:<ARCHIVE>MIDAS.ARCHIVE Gumby egk GZ-OZ GS


5654
doc/midas/midas.bugs Executable file

File diff suppressed because it is too large Load Diff

4398
doc/midas/midas.macro Executable file

File diff suppressed because it is too large Load Diff