Post by Ãyvind TeigThis is so interesting!
I agree! and I think it is important to preserve the evolution of
Occam from the beginning and it provides context as to how the
language and implementations were evaluated in the early days. It also
provides a more complete view of how Inmos developed as a company as
it attempted to gain interest from a wider audience.
Post by Ãyvind TeigI have scanned some more today, I just needed that inspiration! But to me it looks like a very serious description of occam itself, not a description of a toolkit. And the layout is so tasty(?)
As we develop an inventory of these early documents, it is useful to
circulate the full title and publishing details of the document, the
typical contents of the cover page, inside page, document version, any
visible dates etc. This can help establish the timeline for the
document.
To add more to how I got here, in the past days I have been exploring
the UCSD Pascal p-System environment, and came across a volume that
was labeled OCCAM.
Here is the startup when the volume is booted (I am using the
Ersatz-11 PDP-11 emulator):
***@nw-Latitude-7420:~/Downloads/E11 emulator$ ./e11 OCCAM.bin
Ersatz-11 V7.3 Demo version, COMMERCIAL USE LIMITED TO 30-DAY EVALUATION
Copyright (C) 1993-2017 by Digby's Bitpile, Inc. All rights reserved.
See www.dbit.com for more information.
E11>mount dy: OCCAM.bin
E11>boot dy:
Welcome OCCAM, to
U.C.S.D. p-System IV.0
Current date is 18-Jan-83
Command: E(dit, R(un, F(ile, C(omp, L(ink, X(ecute, A(ssem,? [IV.0 B3h]
Command: D(ebug, H(alt, I(nitialize, U(ser restart, M(onitor [IV.0 B3h]
Here is the directory of the volume:
Filer: G(et, S(ave, W(hat, N(ew, L(dir, R(em, C(hng, T(rans,? [C.7]
Vols on-line:
1 CONSOLE:
2 SYSTERM:
4 # OCCAM:
6 PRINTER:
8 REMOUT:
Root vol is - OCCAM:
Prefix is - OCCAM:
Filer: G(et, S(ave, W(hat, N(ew, L(dir, R(em, C(hng, T(rans,? [C.7]
Dir listing of ? #4
OCCAM:
VDUTAB.DAT 1 16-Nov-82
UART.TEXT 24 5-Jan-83
MATRIX.TEXT 26 12-Jan-83
TEA.TEXT 42 16-Nov-82
UTILITY.TEXT 10 12-Jan-83
AUTOBAHN.TEXT 72 12-Jan-83
OLIB.TEXT 4 13-Jan-83
ARRAY.TEXT 28 13-Jan-83
OCCAM.CODE 92 27-May-82
SYSTEM.LIBRARY 6 27-May-82
SETUP.CODE 89 13-Jan-83
SYSTEM.FILER 34 5-Dec-80
SYSTEM.PASCAL 105 17-Sep-81
SYSTEM.PDP-11 26 16-Apr-81
SYSTEM.MISCINFO 1 13-Jan-83
README.TEXT 46 16-Nov-82
16/16 files, 376 unused, 376 in largest
Filer: G(et, S(ave, W(hat, N(ew, L(dir, R(em, C(hng, T(rans,? [C.7]
The startup screen is the same as other UCSD p-Systems in how they
appear when the first prompt appears. It shows the last date it knew
which is 18-January-1983, quite early in the life of PortaKit (and
Occam).
On the diskette (volume) there are TEXT and CODE files. The text files
here are the expected Occam examples, although there are a couple that
are more extensive like AUTOBAHN.TEXT and UART.TEXT - (I can extract
all these files and provide a link to them soon).
The SYSTEM.* files are as expected for a PDP-11 based UCSD p-System
bootable volume.
The README.TEXT file is not particularly revealing about the
content/source of this volume, other than reference to "occam
evaluation kit"
Filer: G(et, S(ave, W(hat, N(ew, L(dir, R(em, C(hng, T(rans,? [C.7]
Transfer ? readme.text
To where ? #1
Note : a hard copy of this document can be obtained from Inmos Ltd.
READ ME
-------
Contents
--------
PART I - description of I/O in the occam evaluation kit
PART II - description of occam programs supplied with the oek
Please note that on some systems there may be disk activity
whilst reading this document interactively. This is due to
limited memory capacity.
PART I I/O IN THE OCCAM EVALUATION KIT
...more of the file elided but it continues to describe some IO aspects...
Here is an attempted session starting the OCCAM.CODE file and entering
UART.TEXT as a file to work with:
Command: E(dit, R(un, F(ile, C(omp, L(ink, X(ecute, A(ssem,? [IV.0 B3h]
Execute what file? OCCAM
% Occam #1.0 Inmos Ltd. (12 Jan 1983)
File: UART.TEXT
UTART $ $ # # #!#! ! " " UART.OUT"(#(# # $ $ $ % % % & & & ' '
' ( ( ( ) ) ) * * * + + + , ,
Program interrupted by user
Segment WKEYS Proc# 12 Offset# 10
Type <space> to continue
System re-initialized
Having entered UART.TEXT it seems to want something else, but nothing
I enter on several tries seems to be what it is expecting, so I am
stumped as to what it wants at this point. Also it seems to write
sequences of characters after that second entry, I have an idea it
might be screen-escape-sequences, but I will need to find a way to
capture it so I can inspect them.