This is my little pool of Transputer software… while my main interest lies in the area of getting them run (and lots of ’em ;-)), you come to a certain point you actually want them to do something.
Don’t expect megabytes of software here… go over to Rams software section, he collected/rescued nearly everything which was available on the market.
This is a simple DOS tool I’ve written to scan a system for a link-interface (aka C011/012). Similarly to the standard tool ‘ispy’,itest just does a scan on a given port address (default is 0x150) and tries to identify a device behind it (16 or 32 bit Transputer, C004).
Depending on the result, a clear text info and a (DOS) error code is returned, which could be used in a batch file. A sample batch file for scanning the usual ports is included in the archive as well as the source (Turbo-C[++]).
“PePo” is my very, very simple DOS Peek/Poke Tool, to have a quick look into a Transputers RAM. Actually it can be used with any B004 compatible interface which supports the INMOS protocol.
So it also works fine with the NumberSmasher i860, which is the reason, why it insists on a 32bit alignment. It uses the Port Address of 0x150 by default. Define the environment variable “TRANSPUTER” to change this.
Usage is simple: Just call PePo with either “peek” or “poke” and an address you want to read/write from/to, so to read the first five 32bit lines in a Transputers external RAM enter:
pepo peek 80001000 5To write something to it enter
pepo poke 800010000 deadc0de
Inmos MMS2 archive
To make things easier configuring your C004 network, I prepared an archive for instant use.
It contains some example soft- and hardwire files, an
ISERVER.EXE (the program you need to upload code into your Transputer) as well as a batch file to easily start MMS (
Also you will find a folder with INMOS’ pimped version of
ANSI.SYS called BANSI (“Better ANSI”), because all INMOS tools make heavy use of ANSI screen control. So put that into your
The Transputer Tool Kit (TTK)
This is a collection I’ve put together, providing all essential tools to get you started with your brand new/old Transputer equipment. Read this post to learn more about its contents.
The Transputer SDK
For a start, I’ve prepared an “Transputer SDK”, well, actually it’s a FreeDOS VM image for VirtualBox containing some of the most commonly used cross-compilers and Transputer software, so you don’t need a Transputer running to host a compiler:
- INMOS Occam
- version D7305 (more DOS oriented)
- and D7405 (comes with many cool optional Windows tools. Windows is not provided.)
- INMOS C (version D7414)
- LSC (versions of ’89 and ’91)
Documentation for all these compilers are available at the usual place.
AFAIK there’s no complete documentation of all additional features of the D7405 package – a 28 page ‘flyer’ from ST can be found here.
Additionally you’ll find the sources for the occam Mandelbrot demo used for the Apple IIgs, as well as my beloved “Mandel” tool, which runs on DOS only.
Both can be fully compiled in the VM (Borland C is provided, too).
When using one of the INMOS compilers, you have to set some environment variables first. To do so, execute the batch file inside the corresponding folder.
For example: You want to use the D7305 occam compiler (which I recommend for the first steps) – change into its folder
C: > cd D7305A
and call the identically named batch-file
C:\D7305A > D7305A.BAT (hint: FreeDOS has auto-completion, so enter “D” and hit TAB)
This sets all paths etc. and you’re good to go. Change into the
OCCMANDEL folder, call the
make_t8.bat batch and let the magic happen 😉 The binary will placed into the \bin folder.
The DOS “Mandel” program requires a PC with a B004 Transputer interface – but I’ve added it for completeness. To compile it, just call the included
nmake inside the
It’s a very good example for mixed code, as it uses the LSC C-compiler as well as Borland C.
So have fun fooling around. I know, it’s a steep learning curve, but as soon you dive deep enough into Transputer matters, you’ll be amazed and will ask “why the heck did this technology never made it?!?!“