Now that we have all config files adjusted to our needs, we should try to boot it.
Normally a simple call to SERVER.EXE should do it, so try now:
C:\TRANS\HELIOS13> server [RETURN]
This should show you the booting process info and results in a bash-like shell. Hooray! You’re running a real OS on your Transputer, congratulations!
You might have stumbled over the many ‘shoulds’… well, there’s a known problem with the server. It uses very simple calibration- and delay-loops (for/next) to determine speeds and setting pauses between each command sent to the Transputer. If you computer is too fast (i.e. built after 1990) those pauses might by too short and server.exe can’t initialize the Transputer correctly resulting in boot errors 🙁
But don’t despair! Michael Brüstle, aka “Mr. T”, came to the rescue and wrote a little ‘helios loader’ which uses more precise timers but is a bit basic – in other words you have to know what you’re doing… which makes this loader a piece of “real men software” 😉
What it does is: Resetting the Transputer, putting the Helios bootstrap-image and nucleus into the Transputers RAM and then quits. So it’s not booting Helios… that’s still left to the server program. To use this tool 3 steps are to be taken:
1) Download HBOOT.EXE from here and put it into your Helios root directory
2) Change your host.con file to prevent SERVER.EXE to overwrite the already loaded bootstrap-image and nucleus. So add/uncomment these lines in your host.con:
no_reset_target # do not reset the Transputers
no_bootstrap # don't load nboot.i
no_image # don't load nucleus
no_check_processor # don't check CPUs as this would need a reset, too
3) [optional] Create a batch file (e.g. START.BAT) in your Helios root folder containing these two lines:
hboot lib\nboot.i lib\nucleus
That’s pretty self-explaining, I guess. So enter START and Helios should successfully boot now.
Next up, using more than one Transputer with Helios…