In the previous post we talked about PPNs like [1,REG]; here REG is the ID that identifies which user you are.

To create a new user ID, simply choose a 3 letter ID and log in as that. This must be on a device internal to SAIL, ie the console or display terminal, not via the external communication lines that are modelled by a telnet connection on simh.

Here I choose REL as an ID and log on. It asks me if I am sure, as this is a new ID, and if I type Y I am logged in and can run programs or create files.

.l 1,rel
JOB 1    Stanford 6.17/K 08-16-74
Are you sure? y
Friday  26-JUL-74       0945
.

If I log out with an empty directory, it will be removed.

.k
Your empty file directory has been deleted.

But it is recreated the next time I log in.

If you had logged in as 1, FOO, you would get this message when you logged out:

You are not an authorized user. Your files have been deleted.

This turns out to be a simple check in the LOGOUT routine - if your user ID is one of FOO, BAR, BAZ, ABC, 100 it will say you are unauthorised, probably because these are common IDs used for testing.

You will note that no password was asked for at any stage. You can set a password by replacing the . with a % at the login stage, eg L 1%REL. You get the option to only ask for a password if you are logging in remotely so you don't need to supply it when logging in via the console or display terminals.

The password is set at the PPN level on the user file directory entry, so you could have a different password for say 1,REL and 2,REL. According to the UUO (system calls) manual it is stored in plain text, case insensitive with a maximum length of 6 characters.

Files and directories have a 3 octal digit protection code.

The default protection is 000, so anyone can do anything.

To set protection on files, you need to use COPY with the /PROTECTION flag to create a new file with the desired level, eg

.copy /protection=006 foo2 ← foo1

would create FOO2 from FOO1 but set protection so guest users can't access it at all.

Directory protections can only be set by logging in with the % delimiter

WAITS is quite similar to TOPS-10 here so reading the Jobs on TOPS-10 post will give more details. But in brief:

When you log in to WAITS, it gives you a job number which lasts throughout your session. Some simple commands (like DAYTIME) you type are built into the monitor. Others need to be loaded into memory from core files, which have the extension .DMP on WAITS.

If you have a core file FOO.DMP in your directory you can invoke it with RUN FOO. Common programs are stored in the SYS: area, which is equivalent to [1,2], and programs here can be run using R. RUN can also take a file name and directory, so R LISP is the same as RUN LISP.DMP[1,2].

Some common programs, like COPY, are recognised by the monitor but behind the scenes it will invoke RUN on the right core file.

You can create another job by logging in a second terminal. But you can also DETACH from a job, which will suspend it and log you out, and then log in elsewhere and resume execution using ATTACH. Jobs can also run in the background if they do not need interact with the user's console.

All that is pretty much the same as TOPS-10. WAITS adds some more conveniences. FORK works like DETACH, but rather than logging you out will create a new job as your current ID. KILL can be used to kill a job owned by you.

WAITS replaces TOPS-10's SYSTAT with WHO, along with the "who line" we saw earlier on interactive terminals.

TOPS-10 had a fairly sophisticated batch processing system, where jobs could be submitted from the terminal or via cards, and queues of jobs could be maintained and run in the background.

WAITS chose instead for a simple facility to run from the terminal, similar to a shell script file on a modern system. The concept is you create a file with a set of commands or data to input to those commands. The end of each line must be denoted by a ↔ rather then Return. There are a number of other metacharacters to allow you to enter the special keys on the Stanford keyboard, eg ≠ will emit an Altmode key

You run the file with DO and it basically pastes data it into your keyboard buffer as if you'd typed it directly, expanding any metachracters.

There is provision for variables via the question mark and a single letter, eg ?A. The first time this is seen it will prompt for input and store that in variable A; from then on using ?A will expand it to the value you entered.

There is no looping or branching available, however.

As an example, if you have the file foo.do:

hello↔dir [?D,DOC]↔

and type DO FOO.DO it will run the hello command, prompt you for a value for D then do a directory listing of that area under DOC.

See the Monitor Command Manual for more details on these topics.

I welcome any questions or comments, and also especially any corrections if I have got something wrong. Please email me at rupert@timereshared.com and I will add it here and update the main text.

Files are named file.ext where file is 1-6 characters long and ext 0-3. The extension is used to identify the type of file, eg HELLO.SAI would be a source code file in SAIL, the lab's version of Algol. One exception is seen in some shared directories, where the file extension is the initials of the person maintaining the file.

Filenames are case insensitive, and each character is stored using 6 bits instead of the usual 7 bit Stanford ASCII. This means that the special characters in Stanford ASCII like ← or α cannot be used in file names.

PPN means project and programmer number. These are both 1-3 alphanumeric characters long, with the programmer number (eg REG) identifying the person and the project number (eg 1) indicating a particular set of work. Programmer numbers can also be shared areas, eg DOC.

This information is given when you log in (eg typing L 1, REG) and also represents an area of the disk, for which is written in square brackets, (eg [1, REG]). By convention, [1, xxx] is like the home directory of user xxx, but the number 1 itself has no special meaning. Users would generally have different project numbers for different tasks, eg REG has [CRF, REG] for working on the CREF program and [DOC, REG] for documentation tasks.

To change directories, eg from [1, REG] to [DOC, REG] you could log out and log back in again with K and then L DOC,REG. But an easier way is to use ALIAS. With one argument this will change your project number, so ALIAS DOC will put you in [DOC, REG], as seen in the screenshot above. When invoked with two comma-separated arguments it will change to that PPN, eg ALIAS 1,BGB. With no arguments it will return to the directory you logged in as.

Typing R ALIAS will show what your current alias is, and what you logged in as.

To create a new directory, you need to log in with that PPN, so to create [FOO, REG] log out with K then log in with L FOO,REG. It will ask you for confirmation and then create an empty directory which you can start adding files to.

When you log out, if your logged in directory has zero files, it will be deleted.

Alphanumeric PPNs are a change from TOPS-10, which only allowed octal numbers. Unlike TOPS-10, there is no concept of sub-directories on WAITS.

There are several commands to manipulate files which share a common code base.

In general the arguments for these commands takes the form destination ← source. On display terminals you can get the left arrow by pressing the left cursor key; on TTYs, you can use underscore instead.

So COPY bar ← foo would copy foo, creating bar, and RENAME bar ← foo would change the filename foo to be bar.

Each file argument can be fully specified as

dev:file.ext[prj,prg]

dev is by default DSK: and does not need to be specified unless you are working with magnetic tape devices. prj,prg by default is the PPN you are currently logged in or aliased to.

The * wildcard means match all for the field it is specified in, eg *.txt. There is no partial wildcarding like a*.txt.

Some examples:

    RENAME *.BAK ← *.TXT

renames all text files in your current PPN to have an extension BAK.

    COPY X ← A,B,C

concatenates a, b and c to form x

    DIR MYLIST ← *.TXT

lists all files in the current PPN matching *.TXT and writes output to the file MYLIST.

There's also a working copy of PIP, DEC's Peripheral Interchange Program, on disk which you can run with R PIP. See my article in the TOPS-10 series of posts for more details.

The root of all directories is [1,1], also called the Master File Directory. If you do a DIR on this you can see each sub-directory as a file containing the PPN and the extension UFD, for User File Directory.

. dir [1,1]
...
  1REG  UFD    388  26-JUL-74
...
DOCREG  UFD    116  01-JAN-64
...

Some notable areas on the file system. As well as browsing these in WAITS, you can also look at the saildart archive by prepending https://www.saildart.org/ and either the PPN in brackets or the programmer number on its own, eg https://www.saildart.org/[S,DOC] or https://www.saildart.org/DOC .

The file manipulation commands are documented in COPY.RPH[S,DOC] in WAITS, or at saildart.org here.

We'll look at file protection, and user setup, in the next post.

I welcome any questions or comments, and also especially any corrections if I have got something wrong. Please email me at rupert@timereshared.com and I will add it here and update the main text.

Teletypes here means the console typewriter (shown below, with John McCarthy helpfully holding the paper) and remote connections, which simh emulates as a telnet connection but on the real system could have come from phone dial up lines or over the Arpanet.

Using the console at SAIL. Source: CHM.

These devices support the backspace key, but do not delete characters; instead they print a backslash, then the characters you want deleted, then another backslash when you start typing again. So if I entered ABCDEF but deleted the last three characters and inserted XYZ it would look like:

ABCDEF\FED\XYZ

You can press Control-U to delete the whole line, but TOPS-10's Control-R to reprint the line is not supported.

Pressing Control-C will stop a job; pressing Control-O will keep a job running but suppress any further output.

.L 1,BGB
JOB 1    STANFORD 6.17/K 08-16-74
THE CTY IS FOR DEBUGGING ONLY,
UNLESS YOU KNOW THE PASSWORD =

$ telnet 0 1974
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.


Connected to the KA-10 simulator DCS device, line 0


TTY2    SYSTEM LOADED ON FRIDAY    26-JUL-74    18:10  
^C
.l 1,reg
JOB 2    Stanford 6.17/K 08-16-74
Remote login prohibited for that account.
You must log in locally and set a password to allow remote logins.
KJOB
.

.l 1,foo
JOB 2    Stanford 6.17/K 08-16-74
We prefer that our ARPA NET guests login as "NET,GUE".
Type "Y" to be logged in as "NET,GUE"; anything else to proceed: y
What is your name, please? A tourist
Friday  26-JUL-74       1822
3 jobs logged in. 1 Running.
.

Most users in the lab would have access to a display terminal, which was very unusual for the early 1970s. There were 6 III (Triple-I) vector displays and 58 DD (Data Disc) raster displays in 1973 (not all DDs could be used at the same time, however). simh has good support for the III which we'll go into details below.

Left: An III display in use at SAIL running an unknown music program. Source: CHM. Right: a simulated III display on simh.

Display terminals used a special keyboard, the layout of which is recreated below.

Stanford keyboard layout. Source: keyboard-layout-editor.com

There are a number of modifiers that can be combined with other keys: Shift, Control, Meta and Top. On simh, Meta is mapped to the Alt or Option key. Top is used to select the symbol on the top of most letter and number keys, such as > on the F key. This is mapped to the Windows/Command key on your keyboard (which may be hard to use as some window managers grab these). On your modern keyboard you will have many of these available directly, so for > you can press Shift and dot as normal.

There are also special keys at the side like BREAK and CALL which are used to control the line editor; simh uses the function keys for these. These are not modifiers, ie to type the sequence BREAK e you'd press F3, let go and type E.

The ALT key (also known as ALTMODE) is not a modifier but another special key, and is accessed by pressing Escape on your modern keyboard. The ESC key is another function key not related to the modern Escape key.

Here's a summary of how all these keys are mapped to a modern keyboard when using simh.

There does not seem to be a simh mapping for CLEAR, however

The cursor keys will emit the arrow characters like ←.

Not a Stanford key, but a facility provided by simh: pressing F11 will make the window full screen.

The saildart javascript emulator does not use the above keyboard mappings, but does provide a layout with a virtual keyboard you can click keys on.

Similar to the facility you are used to in modern shells like bash, the display terminals supported a powerful line editor to help you quickly edit text, using the Control and Meta keys. This works on all text input fields, not just the monitor command line.

If you log on to the III you will see there are two cursors, one at the start of the text field you are typing into, and one at the end. You can move back and forward on the line with Control-Backspace and Control-Space respectively. If you are not at the end of the line, typing a character will replace what's currently behind the second cursor. Typing Meta and a character will insert a character. So typing X with the cursors as shown below would change 'world' to 'xorld'.

The two cursors. Source: Rupert Lane. License: CC0.

Meta-Backspace will delete the character behind the cursor. Control-D deletes the character in front of the cursor.

Plain Backspace at the end of the line deletes the last character, but if the cursor is not at the end it will act the same as Control-Backspace, ie move the cursor left.

A summary including the other line editing commands. C- means Control. M- means Meta.

Finally, you can repeat a command n times by typing Control and the number n, then typing the command.

Often commands with lots of output will cause the screen to scroll. To pause the output, press Control-BREAK (ie Control-F3). HOLDING will appear at the top of the screen. Press an editing key like Control-Tab to resume.

You can also make it pause automatically after every n lines by typing ESC n E, ie to pause after every 20 lines press the keys F2 2 0 E. The important thing here is that you must enter this command while a program is running, and it only has effect for the life of that program, ie you can't set it once at the monitor level and have it apply to all programs.

In summary:

To control the WHO line at the top of the screen:

There are also other controls to adjust the position and pane of glass behaviour which I have not yet found much use for - see section 2 of the Monitor Command Manual, linked below for details.

The Data Disc display on simh. Source: Rupert Lane. License: CC0.

The Data DIsc terminal was the more common of the two terminal types at SAIL. It used a modified TV set to display pixel graphics and text; the name came from the controller which used tracks on a hard disk to store pixel data to be sent to the screen. It also had a video switch so you could select video from TV cameras used in lab experiments and even broadcast TV signals. There's a footmote in the Monitor manual that says:

The first edition said, at this point, "Thus, BREAK S at 6pm on a weekday selects Star Trek." However, I understand that we are being spared that this season.

This terminal is not supported on the saildart emulator yet. On simh, it is emulated but has several problems with scrolling (see this issue for details). You can try this out by changing set dd disable to set dd enable in the run.ini file in the quickstart and restarting the emulator.

You can find out more about the SAIL keyboard, along with pictures, at Xah Lee's site and in an issue created by Lars Brinkhoff on the Github PDP-10 organisation.

This 1975 video shows the Stanford DD display terminals in action.

The Monitor Command Manual section 2 describes the display terminal in more depth.

June 2026: Corrected numbers and availability of display terminals, from a comment by Lars Brinkhoff.

I welcome any questions or comments, and also especially any corrections if I have got something wrong. Please email me at rupert@timereshared.com and I will add it here and update the main text.

I have put together a repo on Github that uses Richard Cornwell's KA PDP-10 simh emulator along with a ready-to-use disk image of WAITS from Lars Brinkhoff's sailing-on-arpanet project. This builds on the simh disk images from Richard Cornwell and ultimately Bruce Guenther Baumgart's saildart archive.

To use this, you will need a Unix-like environment capable of running a shell, git, make, a C compiler, bunziip2 and the SDL library. An optional requirement is a telnet client. See the README for more details.

First, clone the repo and cd into it

git clone https://github.com/timereshared/stanford-waits-simh-quickstart.git
cd stanford-waits-simh-quickstart

Then type ./build.sh. This will

• Download opensimh using git and compile the pdp10-ka emulator binary.
• Download a copy of the WAITS disk images.
• Apply some missing system files.

Type ./run.sh. An III display terminal window will pop up, and the system will boot, showing the below on the main console window.

Stanford 6.17/K 08-16-74

CTY	SYSTEM LOADED ON (date, time)

The main window now acts as the PDP-10 console. You can log into it using the LOGIN command which can be abbreviated as L. As this is a snapshot of a live system, it has several accounts set up already. Let's use REG, which was the account of Ralph Gorin, a system programmer at SAIL. By defailt, no password is needed so just type L 1, REG

L 1,REG
JOB 1    STANFORD 6.17/K 08-16-74
FRIDAY  26-JUL-74       1105


EXIT
^C
.

It prints EXIT and ^C to show the login job has finished, then prompts you to enter commands with a dot.

Type TTY FULL to let it use upper and lower case letters (the console would normally only print capitals).

If you have tried TOPS-10 the interface will look familiar, and indeed most of the commands work the same way. Type DIR to get a directory listing; you can use wildcards to limit the search, so to find all SAIL programs:

.dir *.sai

26-JUL-74  1132
FILNAM  EXT   SIZE LAST WRITTEN

   [1,REG]
FORTUN  SAI    256  30-MAY-72
        TOTAL=   256


EXIT
^C

You can view the contents of files by using the TYPE command, so to see the above you'd enter TYPE FORTUN.SAI

The help system is invoked by typing HELP; to see a summary of commands type HELP HELPER.

.help helper
ALIAS   Command to change default directory used for disk files
ARPA    Basic information for users from other ARPA network sites
ASSIGN  Command to acquire use of non-sharable device
ATTACH  Command to attach terminal to a detached job
BINCOM  Program to compare binary files
...

As a snapshot of a running system rather than a freshly installed but blank operating systen, there are several commands available to run that were created by the researchers at the AI Lab. One example is PARRY, which was an attemp by psychiatrist Kenneth Colby to simulate a person with paranoid schizophrenia. You can invoke this with the R command. It asks you some questions to set up the parameters for the interaction than lets you start talking to Parry. Press Control-C to exit.

.r parry

END INPUT PARAMETERS WITH CARRIAGE RETURN OR ALTMODE

PRINT NON VERBAL FEATURE? [Y,N]
*y
[...] 
END INPUT WITH A PERIOD OR QUESTION MARK, 
   FOLLOWED BY CARRIAGE RETURN. 
TO INDICATE SILENCE, TYPE   . 
   WHEN FINISHED, TYPE   BYE. 
USE PERIODS ONLY AT THE ENDS OF SENTENCES,
   NOT IN ABBREVIATIONS.

READY:
*why is the sky blue?

THAT'S THE WAY IT GOES

READY:
*tell me about your past.

I'M QUITE UPSET

READY:
*why are you upset?

PEOPLE GET ON MY NERVES SOMETIMES

READY:
*^C
^C

Let's create a simple hello world program using Fortran. We will use the SOS editor to create the source file then compile it and run it.

Type CREATE HWORLD.F4 to create a new file and put us in the editor. As this is a new file, the editor will allow you enter text immediately. It will precede each line with a line number (which is not a Fortran label) automatically. So the screen will look something like this after you run CREATE

.create hworld.f4
00100

Type the following program. Where you see ⭾ below you should press the Tab key rather than typing spaces.

⭾	DO 1 J=1,5
1 ⭾	WRITE(5, 2)
2 ⭾	FORMAT(' HELLO, WORLD')
⭾	END

Type Alt-mode (which is Esc on your keyboard) to exit input mode, and then type e at the * prompt to save and exit. Finally type exec hworld.f4 to compile and run the program. Your screen will look something like the below.

.create hworld.f4

00100           DO 1 J=1,5
00200   1       WRITE(5, 2)
00300   2       FORMAT(' HELLO, WORLD')
00400           END
00500   $
*e

EXIT
^C
.exec hworld.f4

FORTRAN:  HWORLD.F4
LOADING

LOADER 5K CORE
EXECUTION

HELLO, WORLD
HELLO, WORLD
HELLO, WORLD
HELLO, WORLD
HELLO, WORLD
EXIT
^C
.

The program is still in core memory at this point, so if you want to save a permanent copy to disk use the SAVE command

.save hworld
JOB SAVED IN 4K

^C

If you now use DIR you can see the files you created.

.dir hworld.*

26-JUL-74  1122
FILNAM  EXT   SIZE LAST WRITTEN

   [1,REG]
HWORLD  F4      19  26-JUL-74
HWORLD  DMP    3.5  26-JUL-74
HWORLD  REL     57  26-JUL-74
        TOTAL=   3.6

EXIT
^C

The .rel file is the object code and the .dmp the executable, which you can run again by typing RUN HWORLD (RUN rather than R as R is for system programs)

So far we've done everything using the console, but you probably noticed the III display terminal that appeared when simh started with its welcoming prompt.

Prompt on WAITS display terminals. Source: Rupert Lane. License: CC0.

All the login and command line programs we have used so far will work on this terminal as well. But this is a vector terminal that can draw text and graphics, along with a keyboard that can enter more characters than the traditional teletype.

Let's login this time as BGB, the main archivist of the saildart.org site. Type L 1,BGB and then try a few commands. You will note that pressing Delete will delete the last character rather than reprinting it as it does on the teletype; in fact there is an extensive command line editor which we will look at in a later post. A warning: the system does not handle type-ahead that well, so it's best to type slowly.

The video display can show more than just the interaction with the monitor command line. Press F2 then W and a dynamic display of system usage will appear at the top of the screen - called the WHO line. Press F3 and then W to turn it off. A more extensive set of system information cab be displayed in the main area by typing WHO; press any key to exit.

Next, type COPY MON ← MONCOM.BH[S,DOC]: you can get the left arrow by pressing your left cursor keu. And then type TV MON.

This will open up the TV editor on a copy of the monitor command manual. Type Control-P to advance by page and Control-minus then Control-P to go back. Press Control-Alt-E to exit back to the prompt.

Running the TV editor. Source: Rupert Lane. License: CC0.

There are also a number of graphical demos. Try running each of these with R, eg R DAZZLE

• armdpy
• dazzle
• hypno
• petal
• repent

When done with each, press F1 twice and type CORE 0 to clear the screen.

Display hacks running on the III. Source: Rupert Lane. License: CC0.

Maybe finish with a game? Two which have graphical versions for the III are Go (R IIIGO) and AI Monopoly (R MONPLY).

Two games on the III. Source: Rupert Lane. License: CC0.

Type K, short for KJOB on any logged in terminal to log off. Or get a more personalised signoff by typing K/ME.

There is no procedure to shut down the operating system. Just switch over to the main simh window, press Control-E and type q.

You can restart the operating system with ./run.sh as needed.

Read the Monitor Command Manual on saildart.org for more information on WAITS commands (this was the document we saw in the TV edit session above).

See PARRY Parries Again for a recreation of a dialogue between ELIZA and PARRY.

June 2026: Corrected program compilation example to use e to exit SOSt and then to type the exec monitor command, rather than the g command in SOS, as g will not work until you have done the first compile/exec command.

I welcome any questions or comments, and also especially any corrections if I have got something wrong. Please email me at rupert@timereshared.com and I will add it here and update the main text.

Screenshot of saildart.org. Source: Rupert Lane. License: CC0.

The complete backup tapes for WAITS have been preserved and are available for access. Bruce Guenther Baumgart, who worked at SAIL, was asked by John McCarthy to preserve the tapes produced by the DART archive tool when the system was shut down. He has built an amazing archive site, saildart.org, where you can access files, documents and other information about the system. (Personal files are not publicly available.)

For most operating systems we will look at, we only have the material to install the officially published software. But in this case we have the full file system, so we get to see all the surrounding files that made up a living system. Most of the documentation for WAITS was produced on WAITS, so it is available in its original digital form. Also, as an incremental backup, we can see how files changed over time.

Beyond the file archive, Bruce has produced a snapshot of the system as of July 1974 - representative of the lab's peak activity period - that can be used by emulators.

There are two emulators for WAITS.

WAITS running on saildart.org's emulator. Source: Rupert Lane. License: CC0.

Bruce has produced an emulator that uses the 1974 snapshot and runs in your web browser at saildart.org. This has demonstrations of a number of interesting systems such as SUDS, the Stanford University Drawing System. It also has interactive access to the complete system using either the console or the III display terminal, so you can login and run commands. Without any additional setup, this allows you to try out the system, but note that your work is not persisted across sessions.

WAITS running on simh. Source: Rupert Lane. License: CC0.

Richard Cornwell has adapted his simh PDP-10 KA emulator to incorporate some of the special hardware used by WAITS, and has provided disk images on his site. The emulator contains support for the III and DD display terminals, along with networking capabilities, which Lars Brinkhoff is currently trying to recreate its Arpanet connection at sailing-on-arpanet. The simh version needs some set up, but does allow you to import/export files and keep your changes over several runs of the system.

One important thing to note: neither emulator has complete coverage of WAITS features, and some programs do not work. This is not due to lack of effort on the part of the authors, rather due to the non-standard nature of the SAIL hardware, which often lacks docs and diagnostics, and the fact this is a snapshot of a running system rather than an official release.

In this series of blog posts I plan to cover

• A quick tour of running WAITS on simh
• Using the terminals
• Files and directories
• Users, jobs and security
• Getting data in and out of the system
• Utilities and tools
• Text editors

• Printing and documentation tools

  • The XGP
  • PUB
  • POX
  • TeX

• Programming

  • SAIL
  • LISP

The main focus of this blog is the operating system and its associated tools, so I will not look in detail at all the user programs available on WAITS - but if time permits, I will try to cover some interesting examples.

For background information on the PDP-10, see my previous article.

As mentioned, there is a great deal of information on saildart.org. A good place to start is the booklet which gives an overview of SAIL WAITS, and the archive project. The Visitor 1976 gives a photo tour of the lab along with some of its equipment and people.

For more detail, look at the collection of AI Memos and SAIL Operation Notes, or dig further into specialised areas on the main page such as music.

References to files on the SAIL system can be viewed by prepending saildart.org. For example, to read the Lisp manual LISP.WD[S,DOC] you would go to https://www.saildart.org/LISP.WD[S,DOC]

AI Memo 228 gives a good overview of the work done at SAIL in its first 10 years.

Regarding the PDP-1 system that preceded WAITS, the Stanford archive The History of Artificial Intelligence has some interesting material, eg Time Sharing Implementation on the PDP-1 and the User's Guide.

June 2026: Added links to more PDP-1 material.

I welcome any questions or comments, and also especially any corrections if I have got something wrong. Please email me at rupert@timereshared.com and I will add it here and update the main text.