Newsgroups: comp.sys.transputer
From: J.C.Highfield@lut.ac.uk
Reply-To: J.C.Highfield@lut.ac.uk (J.C.Highfield)
Subject: T414 Emulator (for Macintoshes)
Summary: Available
Organization: Loughborough University, UK.
Date: Tue, 9 Aug 1994 20:36:29 GMT
Message-ID: <CuABwt.G42@lut.ac.uk>

The emulator I mentioned a while back is now available from several
archives including mac.archive.umich.edu and its mirror on src.doc.ic.ac.uk.

On mac.archive.umich.edu it may be found as:
/mac/util/organization/emulator1.01a.sit.hqx
[115     7/30/94    BinHex4.0,StuffIt3.07]

and on src.doc.ic.ac.uk as:
/packages/mac-umich/util/organization/emulator1.01a.sit.hqx

I have included the program notes below. This slightly differs from the
version I first discussed in that it will take instruction profiling 
information if you turn that feature on. Also you can turn off error
checking (the -se sort) if you wish.

I had intended to port the emulator back to unix systems, (it started life on
one), but due to a fairly low level of interest and the amount of time that
supporting this takes that will probably not happen.

Julian

==============================================================================
 
This (free) program emulates a combination of an Inmos T414 transputer (with 2M
RAM) and the standard iserver host interface program. It runs on Macintoshes.
(Both 68k and PowerPC based ones.) It needs 2.5 MBytes of memory.

The emulator has been tested on a PowerMac 6100, a IIci, an LCII, a quadra 650
and a powerbook 165.

A "Hello World" binary is included as an example for testing the emulator on
other machines.

The emulator runs single transputer binaries as though invoked using
"iserver -se -sb bootfile.btl". The "-se" stop-on-error flag may be turned off
using the options menu. The other options menu entry allows you to enable
instruction profiling, which counts how many instructions of each kind are
executed and saves the result to a file called "profile".

This is the first release and will have many new bugs for you to discover. Bugs
may be reported to J.C.Highfield@lut.ac.uk until the end of September 1994.
Initial bug reports should take the form of a summary of the machine the
emulator is being run on, the compiler the transputer binary was generated by
and whatever the binary does. Since bugs in an emulator can take a long time to
track down, with some recent ones appearing after the emulator had executed 100
million instructions, then to actually solve a bug report I would probably need
the binary and any data files it uses. Arithmetic bugs etc. would however be
much simpler to solve than this, with a one line example program being quite
adequate.

If anyone has suggestions for improvements then please send them along - I will
try to include them. One feature I already intend to alter is that the emulator
does not currently update its window after being obscured by another window.

Julian Highfield, 28 / 7 / 94.

Email: J.C.Highfield@lut.ac.uk [Until the end of September 1994]


