Contact us Heritage collections Image license terms
HOME ACL Associates Technology Literature Applications Society Software revisited
Further reading □ OverviewUser note 1LOADGO header recordsLarge software charactersCamera schedulesNotes on initial serviceFR80 logging systemProgram for viewing FR80 tapes (FRVIEW)Colour specificationGrey-scale recordingFR80 software (DRIVER)Interruptions to serviceIII News (June 1979)
ACD C&A INF CCD CISD Archives Contact us Heritage archives Image license terms

Search

   
ACLLiteratureFR80 Reports :: Literature: FR80 Reports
ACLLiteratureFR80 Reports :: Literature: FR80 Reports
ACL ACD C&A INF CCD CISD Archives
Further reading

Overview
User note 1
LOADGO header records
Large software characters
Camera schedules
Notes on initial service
FR80 logging system
Program for viewing FR80 tapes (FRVIEW)
Colour specification
Grey-scale recording
FR80 software (DRIVER)
Interruptions to service
III News (June 1979)

DRIVER

R W Witty

May 1976

INTRODUCTION

All software for the FR80 is supplied in binary object program format only. Making changes requires decompilation of the binary program followed by break-out patches. The III software runs as stand-alone programs because the FR80 has no operating system or run time support package. Run time errors usually crash the machine. The primitive architecture of the III-15 CPU means that it cannot trap bad instructions or write-protect parts of store. There is neither software or hardware protection for the vulnerable analogue side of the FR80, particularly the CRT which is very expensive to replace.

All III software has been designed to run in an 8K machine and no disc. To squeeze it into such a small store, the software is coded entirely in Assembler. The software is poorly designed, badly coded and unreliable.

The number of lines of patched code exceeded the size of the code that it was patching. ACL put about 3 manyears of effort into patching III software before the decision was made to rewrite it completely.

DRIVER

III software is unreliable, difficult to maintain and impossible to develop. A replacement system, DRIVER, is being constructed by R W Witty. The advantages of DRIVER are:

  1. Reliability
  2. Good documentation
  3. Ease of maintenance
  4. Easy addition of new facilities
  5. Good base for new system programs (run time support)
  6. Improved error detection and recovery
  7. Automatic logging and monitoring of system performance
  8. Reduction of multiple Displayers to one DRIVER
  9. Improved performance and throughput
  10. Portability to other FR80 sites
  11. Compatibility with existing software
  12. Improved operator interface
  13. Protection of vulnerable hardware

To make DRIVLR reliable, maintainable and modifiable it is constructed in a structured high level language, DRIL, which is cross-compiled from the 1906A by a TREE-META compiler-compiler produced translator. The advantages of such a high level language over Assembler are many. Cross-compilation means software development causes minimal interference to the FR80's production schedule as most of the work is done on the 1906A. DRIVER is designed and constructed according to the best principles of structured programming. Reliability is greatly increased by proving that DRIVER terminates for any input. Automatic documentation tools are currently being constructed. The DRIVER prototype first ran on 29 March 1976 and the first production version, Mk 1, is scheduled to go into service on 1 December 1976.

Mk 1 DRIVER will offer the following new facilities:

  1. Font changing
  2. Easier to use colour system
  3. Vector speed change
  4. Temporary pictures on disc
  5. Accurate clock
  6. Improved 'manyup'
  7. Special features for Data Compilation project
  8. Better operator interface
  9. Logging and accounting
  10. Hardware protection
  11. Multi-reel colour

DRIVER is designed to be a good base for future developments. These could include:

Development of DRIVER has highlighted some of the problems in dealing with III. For example:

  1. queries about the operation of the hardware were either wrongly answered or not answered at all
  2. The Engineer's circuit diagrams and documentation are inadequate as is the software documentation.
  3. III documentation contains errors and omissions.

DRIVER timescales are:

⇑ Top of page
© Chilton Computing and UKRI Science and Technology Facilities Council webmaster@chilton-computing.org.uk
Our thanks to UKRI Science and Technology Facilities Council for hosting this site