Computer Technology Limited

From Wikipedia, the free encyclopedia

Computer Technology Limited
IndustryComputer hardware
FounderIann Barron
HeadquartersHemel Hempstead,
Key people
Iann Barron (1965-1971),
Tom Margerison (Chairman 1971-1975),
Tony Davies (Managing Director 1981-1989)

Computer Technology Limited (CTL) was a British computer company founded in 1965. In 1984 it merged into its holding company and was called Information Technology Limited (ITL).

Founder Iann Barron had worked for Elliott Automation but left to form CTL when he couldn't persuade Elliott to incorporate his ideas in their next generation of computers. CTL was financed by the American Research and Development Corporation and Pergamon Press.[1]

The first CTL computer, the Modular One, appeared for sale in 1968.[2]

Modular One[edit]

The Modular One was a 16-bit computer built with Emitter Coupled Logic (ECL) and was competitive with other first generation minicomputers.


A key feature, from which it derived its name, was that it was composed of separate processor, memory and peripheral modules sharing a common interface and physical form factor, so allowing them to be put together in any combination, housed one or two high in modular racking. Standard modules were roughly 50 cm wide and deep, 70 cm tall, and complete with power supply, typically weighed in excess of 25 kg. Modules were interconnected using a single type of interface, comprising two identical cards to be plugged into two modules to be connected, these cards themselves linked by a flat ribbon cable either one or two metres long. Thus, memory was just another peripheral (such as a printer) but was both input and output.

Every interaction over these interfaces comprised a 3-way handshake, which in the case of a processor accessing a memory module, consisted of send address, receive data, and send new data, a scheme well suited to the destructive read followed by rewrite required by magnetic-core memory of the time. These three phases were mediated by voltage edges rather than pulses, as this was thought to be faster. Furthermore, the input and output impedances of ECL were comparable to the characteristic impedance of ribbon cable. This, together with the small voltage swings between the "0" and "1" states made for low noise, reflection-free communication.

Processors naturally had a number of interface slots bussed together, allowing connection to memory and peripheral modules as required. Memory modules had several, allowing them to be accessed by more than one processor as well as by disc controllers for DMA. Disc controllers could be connected to two processors as well as memory modules. All modules had a "1.x" type designation, for example, the original processor module was 1.11, memory modules were 1.2x, character peripherals were 1.3x, discs were 1.4x and magnetic tape devices were 1.5x. The standard interface was designated 1.01.

The various building blocks could be assembled and configured to produce a fault-tolerant computer system.[3]

Distinctive features of the processor were memory-mapped I/O and an early version of segmented memory (similar to the later Intel 8086 but having both base and limit). The processor had 3 segment registers referred to as X, Y and Z. The X segment was read/execute only and used to map code segments (corresponding to CS in the x86 architecture). It was not possible to execute code in the Y and Z segments, which were used for data (roughly corresponding to DS and ES in x86). There were 8 addressing modes allowing access to data mapped by the segment registers in various ways.[4]

The memory segmentation, together with two execution states (Normal State and non-interruptible privileged Special State) made possible the implementation of a self-protecting operating system kernel (known as the Executive, or Exec). Such ideas were popular in British computer academia at the time. Furthermore, the power system was set up as a peripheral with interrupt capabilities that gave the machine the ability to power down gracefully in an emergency.

Sales history[edit]

The Modular One was comparatively expensive. It was somewhat exotic in that its modular design resulted in almost every system delivered being somewhat different, which created a high maintenance burden.

Many universities were equipped with Modular One systems, in part due to the government of the time having a 'buy British' policy.[5] Acting as a front-end processor for the ICL 1900 mainframe, driving multiple online terminals or as a remote batch job entry station, was a major market for the Modular One.[1]

It never sold widely outside of the UK, and even in the UK it was surpassed in sales by Digital Equipment Corporation (DEC) and Data General before the end of the 1970s.[1]

Over the mid 1970s to mid 1980s the systems were cost reduced with TTL bitslice technology and 8-bit microprocessor communications controllers, retreating from the radical modular design, but it never gained a significant market share.


Very few Modular One computers now remain, possibly only the example being that restored by Redhawk Systems Ltd.[6]

Operating system[edit]

The operating system kernel was referred to as the Exec. Several simple ones (E1, E2 and E3) were developed in the early years of the company. E4, first in-house release around 1973, written entirely in assembler, was a multitasking kernel using Dijkstra semaphores to protect internal data structures from conflicts. It was based on an early version of object-oriented principles, though lacking most of what are now considered essential features of the paradigm, such as inheritance.

Objects included Activities (now more commonly known as tasks or processes), Segments (of memory), Files, Semaphores and Clocks. Another object type, the Sphere, was a run-time protection domain within which all other object types (including other Spheres) existed. Objects could be created in arbitrary quantities, and were each referenced through a Run Time Name, or RTN. Since an object could be referenced by several RTNs belonging to different spheres, they could easily be shared between programs, and were deleted only when the object's reference count of RTNs fell to zero. Linked lists were used very extensively within E4 to manage data structures, in fact the RTN list was about the only linear list there was. (The system generation process included a phase prosaically called "knitting" comprising a combination of macro expansion and procedural elements, by which the initial data structures were dynamically "knitted" together to create an input file for the assembler.)

The ease with which multiple processor, store and peripheral modules could be built into a system, plus the need to extend the upper capability limits, prompted the development of a dual processor variant of E4. This was built entirely from standard modules except for a small synchronisation board which prevented both processors operating simultaneously in special state, and a very minor modification to one of the processors' interface to store zero, allowing each processor to address a small dedicated memory area for processor-specific variables such as the current activity. However, the results were somewhat disappointing as E4 naturally spent a significant proportion of its time in special state even though efforts had always made to limit special state routines to 100uS at a time. Even running processor-bound user programs, the performance achieved was only of the order of 150% of that of a single processor, and no dual processor E4 systems were ever sold.

There was some similarity to Unix in the use of (mainly) device-independent serial byte oriented streams in the file system and interprocess communication, in contrast to the record-oriented file systems then dominant in commercial data processing. E4 also supported real-time priorities and virtual memory at the Segment level.

E4 had a primitive command line interface but a multi-access operating system known as Modus was built on top of it for much greater flexibility and ease of use. This consisted of a "Nucleus" which looked after a collection of "Engines". An Engine was typically associated with a peripheral device and processed work from a queue, for example taking print jobs from a print queue and printing them. A special case was the Read Engine, which was the command processor. This was either associated with a terminal device (in which case it had a terminal device but no queue), or was a batch processor (in which case it had a queue but no device).

The filing system, SDFS, was not part of the kernel but was a separate program. A multi-key indexed file system MKFS was also developed, and together with a transaction processing system and a report generator, formed the basis of many sales into commercial applications.

Modus and many of the applications were written in the high level language Coral 66.[7] Compilers for COBOL and FORTRAN IV were also available for the Modular One.[8]

Later history[edit]

Founder Iann Barron left in 1971, following the collapse of a major customer. He went on to form Inmos and develop the transputer. He was replaced as Chairman by Tom Margerison, from London Weekend Television.[1]

During the 1970s CTL operated modestly successfully in a number of niche markets, while larger American competitors, such as Digital Equipment Corporation (DEC) with their PDP range, increased market share. In 1980 two sibling companies Office Technology Limited (OTL) and Network Technology Limited (NTL), and a holding company Information Technology Limited (ITL) were created.[1]

In 1981 entrepreneur Tony Davies became Managing Director. Under Davies CTL began buying in hardware, to be re-badged as CTL systems, recognising CTL could not afford to develop hardware at all levels. The first was a Convergent Technologies 8086 system which created a price competitive small system for CTL. In 1984 all the subsidiaries were merged into the holding company Information Technology Limited (ITL), replacing the CTL name. Nominally this was an efficiency measure, but it also positioned the company better for a possible public offering on the stock markets.[1]

During the mid 1980s, the company decided that the future lay in open systems and CTL attempted to make the transition to Unix with re-badged systems from Motorola and Sequoia Systems. However, sales of CTL's proprietary systems fell off before the new systems could be ramped up to replace them.[citation needed] The company was taken over by ACT in 1989, primarily for its customers and extensive support network, which effectively ended CTL's era as a computer manufacturer.[1]


In 1969, Computer Technology hired then up-and-coming architect Norman Foster to design their new headquarters north of London, in Hemel Hempstead. Foster responded to the company's need for an open office plan, as well as a compressed building schedule, by designing an innovative inflatable structure or "air tent" that was critically lauded by the architectural press at the time of its unveiling.[9]

See also[edit]


  1. ^ a b c d e f g Hamilton, Ross (June 1997). Continuous Path: The Evolution of ProcesControl Technologies in Post-War Britain (PDF). Department of Computer Science (Thesis). University of Warwick. pp. 115–116, 120, 123, 127, 138–140. Retrieved 6 April 2019.
  2. ^ "Compact machine launched". Computer Weekly. 2 May 1968. Retrieved 9 April 2019.
  3. ^ Paul Walker; Barry Cook (2006). SpaceWire: Key principles brought out from 40 year history. 20th Annual AIAA/USU Conference on Small Satellites. p. 1.
  4. ^ "Computer Technology Ltd. and the Modular One" (PDF). Version 4. February 2023. pp. 14–16.
  5. ^ "The History of Computer Science 1970 - 1979". School of Computer Science. University of Birmingham. Archived from the original on 7 February 2007.
  6. ^ Redhawk Systems Modular One conservation project
  7. ^ "Lucid language may help European computers". New Scientist. 30 November 1972. p. 513. Retrieved 8 April 2019.
  8. ^ "Survey of minicomputers". Computing. 16 August 1973. Retrieved 8 April 2019.
  9. ^ "Office beneath the skin". Design. Council of Industrial Design, The Design Centre.