README

   1 Philipp Hachtmann's Honeywell H316 development kit
   2
   3 This package is made by Philipp Hachtmann (hachti@hachti.de)
   4 A fresh snapshot can always be found on http://h316.hachti.de
   5
   6
   7 How to use:
   8 ===========
   9
  10 This is approved working on my two Linux PCs.
  11 You need a "normal" gcc and gnumake etc. bla bla.
  12
  13 Bob Supnik's SIMH simulator must be installed.
  14 SIMH from rev. 3.6 works fine.
  15 Older versions have a severe bug, don't use them.
  16 If you like SIMH consider compiling it with
  17 libreadline support - see the SIMH makefile....
  18 You get SIMH at http://simh.trailing.edge.com
  19
  20 - Extract the archive (You have already done that...)
  21 - Set following environment variables:
  22     export H316=<full path to the directory containing this file>
  23     export PATH=$PATH:$H316/bin
  24     And you need to have the SIMH h316 binary in your $PATH.
  25 - Enter the $H316 directory and run make.
  26 - If there's no error you can start to look around in the tree.
  27   Everything is fine and ready to use.
  28
  29 If there's an error try to correct it or feel free to ask me.
  30
  31 All libraries are built when you run make. Precompiled (original)
  32 stuff is only found in directories called "original" or "obj".
  33 Everything else is always rebuilt.
  34 The IO library works with my private line printer interface.
  35 So don't get frustrated when you try the routines in SIMH - they
  36 won't work as expected.
  37 If you have some original library routines from Honeywell - please
  38 let me know! I am looking for tape drivers, the original line
  39 printer driver etc.
  40
  41 If you have set up everything look for the mandelbrot program.
  42 It's somewhere out there....
  43 Try to compile it with the genious command "frtn <source-file>".
  44 Then you have a Honeywell Object. Now exec it by calling
  45 frun <object-file>. There is also an asm command.
  46 Try it out and read the scripts in $H316/bin for enlightment!
  47
  48 Libraries are built with some scripts contained in the appropriate
  49 subdirectories. There's a kind of receipe file for every
  50 library to build. Works fine, try it out!
  51
  52 So, if there are questions, please ask me.
  53
  54 Best regards,
  55
  56 Philipp :-)
  57
  58
  59
  60
  61
  62
  63
  64
  65
  66
  67