George3 running on Raspberry Pi

This demo will create two directories a68demo and g3pi.
You may find it helpful to visit our George3 emulation page. Download the two ZIP files a68demo.zip and g3pi.zip, and unzip them:
                unzip a68demo.zip
                unzip g3pi.zip

Make the binary program executable, and switch to the demo directory:
                chmod 755 g3pi/g3exec-pi
                cd a68demo

It is assumed that the Raspberry Pi is connected to a local area network (e.g. home hub) using its ethernet socket. Find out the IP number of the Raspberry Pi
                ifconfig eth0

The reply will look something like
eth0      Link encap:Ethernet  HWaddr b8:27:eb:43:6f:54
          inet addr:192.168.0.112  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1488  Metric:1
          RX packets:1871 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1474 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:111174 (108.5 KiB)  TX bytes:177781 (173.6 KiB)
The number that you want in this case is 192.168.0.112.

To start George3 do:
                ../g3pi/g3exec-pi -c192.168.0.112 DA GEORGE3
                                but substituting the IP number of your machine for 192.168.0.112.

This is the equivalent of step 6 in the readme.htm file that is part of the package in a68demo.zip. It would be wise to have this open on another tab on your web browser.

You now need an operator’s console, which can be a telnet command, though some version insist on doing a line-by-line echo mode. You really need character-by-character without echo. There is a teletype emulator in g3pi.zip which you can run on any machine in your local network to act as the operator’s console:
                java TeleType 192.168.0.112 1900
                                but substituting the IP number of your machine for 192.168.0.112.

The operator’s console should now give the responses as in step 7 of the readme.htm file, and you can continue to step 8 and beyond.

MOP

Read the section headed MOP in the readme.htm file,

It is quite possible to run the ICL 7903 on the Raspberry Pi, but it may be that there are reasons to run it on a different machine on your local network. If you wish to run it on the Raspberry Pi you need to add the following line to /etc/hosts.
                127.0.0.1 icl7903
You will need to be superuser to do this, and also to run the ICL7903 program because it needs to listen on the telnet port 23, which is not allowed to ordinary users. To run with 10 teletypes and no VDUs:
                java ICL7903 10 0

If you wish to run the 7903 on a different machine, its IP number needs to replace 127.0.0.1 in the above added line in /etc/hosts.

Some more users

The g3pi directory has a file CR03 which can be copied into the data directory and then used to create 9 users :G1 to :G9:
                cp -pvi ../g3pi/CR03 data
To make George3 read this file, just engage reader 3 in a similar way to reader 4. The first time that you do this it will fail part way through because the new users hjave not yet been created. However, by this time it will have written a file which you can use to create the users, byt typing on the console (remember to press tab to invite input):
                RJ MM,:MANAGER,MKUSRS
After this you should once more engage reader 3. You will then be able to log in as any or all of these users.

Printer Output

If you run a webserver on the Raspberry Pi, and create a symbolic link along the lines of:
                /usr/WWW/temp/LP10.txt -> /home/ecldh/g3/a68demo/data/LP10
                                you will be able to display the printer output on any web browser on your network using a URL similar to:
                http://192.168.0.112/temp/LP10.txt

Unzipping the g3pi.zip ZIP file also creates a directory miscnet which contains a simple webserver, which you can run with:
                java -jar web.jar w80
                                where 80 is the port number that it listens on. (You need to be superuser to listen on 80.)