At the moment, it contains two zip files.  The first, ti1v4.zip, is what you would need if you had a proper old DOS system with a physical transputer board plugged in to its ISA bus.  The .EXE files within are 16-bit and won’t run on a modern Windows system.  This may be the best one for archival and preservation purposes.

 

The other one, ti1v4-32.zip, is just a snapshot of the contents of my C:\TI1V4 directory.  Note that that directory name is pretty much a mandatory default, and your life will be easier if you stick with it.  This is the best one for current use.  A diff will show that it is the same thing as the other zip file, except that the driver .EXEs are now copies of the 32-bit one I built in 2013, and can be used on a modern Windows system along with JAFSERVER.EXE, which you will need to download from Gavin Crate’s web site.

 

                https://sites.google.com/site/transputeremulator/Home/3l-afserver

 

Note that you do need JAFSERVER and not JSERVER, which uses a different protocol.  With all of the above (\TI1V4, JAFSERVER) on your PATH, you should be able to do the following:

 

                t4i/i                                        (show identification and copyright notice: minimal smoke test)
                t4i test                                  (compile test.imp to test.bin)

                decode test                         (decode test.bin)
                t4ilink test                           (link test.bin with Imp run-time library and binary occam “harness” into test.b4)
                jafserver -:o 1 test.b4     (run test.b4)

 

Beware: the t4ilink command is a DOS batch file, T4ILINK.BAT.  If wine doesn’t like that, you should be able to look at its one line of code and run the linker (linkt) directly using the library and harness files named in the .BAT file:

 

                jafserver -:o 1 c:\ti1v4\linkt.b4 test.bin+…stuff from t4ilink.bat…

 

Note further that the -:o 1 switch for JAFSERVER is pretty much mandatory for anything other than Noddy programs.  Inmos, the customer, insisted that the default should be -:o 0, which forces the stack to live in the transputer’s 4KB of on-chip memory.  That gives faster benchmark results for tiny programs but guarantees that anything larger will silently crash.

 

If you get bored typing -:o 1, you can do this:

 

                copy \ti1v4\t4c.exe myprog.exe

                myprog                                (this will run myprog.b4 using jafserver -:o 1)

 

There are lots of optional compiler switches.  These are mostly the same as the C compiler, for which the manual used to be available online at the website of Ram Meenakshisundaram at http://transputer.classiccmp.org/languages.htm  Ones that you won’t find documented there that may be useful to you are /?* to turn on all pass2 and 3 diagnostics (overkill for anything that isn’t tiny) and /?k which tells the compiler not to delete its intermediate files, including the Icode, which is usually ITEMP.1.  Pass1 generates the “no commas” form of DEFINE (‘$’), so you may need my idc rather than your own Icode decoder.  I don’t think there was anything much in the way of a document: the users were all expected to know (or read the CCNATIVE.IMP driver source!)  I may have a look around.