Instructions:
http://www.elitehomepage.org/manual.htm
(Very briefly: F10 to leave space station, <> S X for left right up down, space for faster, ? for slower. Press A to fire lasers, but if you do that near the space station the cops will get you. When flying, F1 for rear view, F10 back to front view)
One of these: http://www.computinghistory.org.uk/det/33101/Acorn-Cambridge... with a TI 32016 processor & using a BBC Micro for UI - except that my housemate Colin thought it was a bit expensive, so reverse engineered the board, redesigned it to be a little smaller (this was in the mid-80s & chip specs were changing rapidly), wire-wrapped a prototype for testing, then etched five proper PCBs, of which only a couple were populated.
An article about that board in some computer magazine of the time (probably PC World) was the first time I had heard of Unix and C - I was amazed at the same of C code they gave - no line numbers!
Edit: This was probably 1983 when I was 17 and my programming experience was based on Apple II and Sinclair machines.
I never got nearer than a magazine review to one of those beasties so I am probably getting the OS part wrong - but I do vividly remember wondering what #include did.... :-)
There were things I could read about in magazines as a kid but never got to see in the flesh. That Cambridge Workstation is still a mythical beast to me.
The Centre for Computing History is a great place to visit - lots of machines up and running you can actually use (mainly from the 8-bit era, but other interesting things too).
There are some BBC BASIC programs broadcast on TV (literally!) by the BBC on their Computer Literacy Project website,[0] saved from the original floppy disks stored in one of the presenter's attic!
They also have (almost?) all of the TV programmes related to computers aired in the 80's on there too. It's well worth a visit.
I don't think it's possible to fork a process? At any rate the example code is basically an infinite loop... So I think you get to do pretty much whatever for you 50 seconds of runtime..
Yup, that machine had literally no notion of a process. You could say it was strictly single-process: whatever is in memory is what gets run...a fork bomb would require breaking out of the VM.
had a bit too much fun with this the last few days, but had an idea and trying to get it into a tweet (without minifying) was fun - wanted more of a typing effect but lack of way to delay/wait/slow BBC BASIC flow or get timing right with GIF maker (should've read doc note! it generates the gif after 18 seconds and then for only 2 seconds long). Still very neat, takes me back to my <ahem> youth.
"Spelled" is more common now even in British English. E.g. compare a Google search of 'site:bbc.co.uk "spelt"' with 'site:bbc.co.uk "spelled"'. Most recent usage of "spelt" is referring to the grain, or a direct quote of somebody who prefers the old-fashioned spelling.
https://bbc.godbolt.org/
I had one of these when I was young and it pretty sport on with how I remember it.