Open main menu

The Jupiter Ace by Jupiter Cantab was a British home computer of the early 1980s. The Ace differed from other microcomputers of the time in that its programming environment used Forth instead of the more popular BASIC.[2]

Jupiter Ace
Jupiter Ace
TypeHome computer
Release date1982; 37 years ago (1982)
Introductory price£89.95[1] (equivalent to £311.81 in 2018)
Discontinued1984; 35 years ago (1984)
Operating systemACE Forth
CPUZ80 @ 3.25 MHz
Memory1 KB (maximum 49 KB)

After Jupiter Cantab ceased trading, the brand was acquired by Boldfield Computing Ltd in 1984, before eventually being sold to Paul Andrews's company Andrews UK Limited in 2015[3]


Jupiter Cantab was formed by Richard Altwasser and Steven Vickers.[4] Both had been on the design team for the Sinclair ZX Spectrum: Altwasser did some work on the development of the ZX-81 and in the design of the hardware of the Spectrum. Vickers adapted and expanded the 4K ZX-80 ROM to the 8K ZX-81 ROM and wrote most of the ROM for the Spectrum.

The new AceEdit

The Jupiter Ace was named after the early British computer, the ACE.[5]

A small Jupiter ACE system

The Jupiter ACE is often compared with ZX81 due to its similar size, low cost, and similar form factor.[6] Internally its design is more similar to the ZX Spectrum although the ACE also had a dedicated video memory of 2 KB, partly avoiding the slow down when programs accessed the same bank (same chips) as the video memory. Like the Spectrum, the Ace used black conductive rubber keys.

Audio capabilities were CPU controlled with programmable frequency and duration. Sound output was through a small built-in speaker.

As was common at the time, it used a common tape recorder instead of disk/tape drives. Similarly, a television was needed as a display - but this was in black and white only, rather than the colour supported by competing models such as the Spectrum.

Its most distinctive characteristic was the choice of Forth, a structured language allowing programs to be written that would run almost as fast as the compiled languages loaded by more expensive computers. Forth was considered well adapted to microcomputers with their small memory and relatively low-performance processors.[7] Forth programs are memory-efficient; as they become bigger, they reuse more previously-defined code.[8] Control structures could be nested to any level, limited only by available memory. This allowed complex programs to be implemented, even allowing recursive programming. The ACE's Forth was "ten times faster than Basic"[9][10][11] and used less than half the memory (a significant cost percentage of low end computers of the time) of an equivalent program written in interpreted BASIC.[9] It also allowed easy implementation of machine code routines if needed.[12]


Characteristic Value
Processor Zilog Z80A clocked at 3.25 MHz.[13]
Operating System FORTH (as both Programming language and Command-line interface).
Memory 2KB for Video + 1 KB base expandable up to 49 KB (Video excluded).
Video Independent sub-system with 2 dedicated SRAM banks : Screen (1 KB) + Char Tiles (1 KB).
Sound Internal Speaker, CPU driven (non dedicated).
Expansion 2 connectors: Main (CPU related) + Video(Screen + AV signal).
Keyboard and Charset 40 keys Qwerty Keyboard (Symbols access with extra key).

All chars in Charset (based on ASCII-1967) being redefinable.

Character set Based on ASCII-1967 with extensions as for the ZX Spectrum character set including ↑, £ and ©.

References to the ACE RAM sometimes include the separate 2 KB video memory, which was not available for programming, thus leading to some confusion. Similarly, it is sometimes argued that because of Forth's efficiency, the 1 KB standard RAM was in effect comparable to at least 2 KB on a BASIC system.

ACE's ForthEdit

ACE's Forth Vocabulary

ACE's Forth was based mostly on Forth-79, with some relevant differences,[5]:176 in particular it added syntax checking to control structures and definer constructions (a.k.a. "Safe Compiling"),[citation needed] and a few extra words were added based on common BASIC sound, video and tape commands. The implementation lacked some less frequently used Forth words, these being easily implemented if needed. Runtime error checking could be turned off to raise speed by 25% to 50%.[5]:171


Its Forth was adapted to the disk-less tape-using home computer hardware by being able to save/load user "compiled vocabularies", instead of the usual numbered programming blocks used by diskette systems.

Decompiling avoided wasting RAM in simulating an absent Block System, used with both disk and tape drivers (these last not to be confused with tape recorders). As replacement, it included an extra data file, for raw binary data. These solutions were unique to the Jupiter ACE.

Define vs CompileEdit

To allow decompile, it distinguished usual Forth definer and compiler words creation, replacing the CREATE .. DOES>,[14] creation pair with:

  1. DEFINER .... DOES> : Create new Defining words, usually used to define and build data structures. Similar to CREATE..DOES usage in standard FORTH.[5]:120 ( Example: Adding Data Structures as Arrays, Records, ... ).
  2. COMPILER .. RUNS> : Create new Compiling words, less frequently used to extend the language with compiler words where CREATE..DOES> is FORTH implementation dependent.[5]:136 ( Example: New Compiler Control Structures as Case, Infinite Loop, ... ).

These 2 defining pairs, instead of one alone, allowed the ACE to decompile its programs, unlike usual Forth systems. This decompiling ability was a solution to the absence of the more flexible disk system used by Forth. Not storing the source of a Forth program, but compiling the code after editing, it avoided completely the emulation of a disk/tape drive on RAM saving computer memory. It also saved time in reading and writing programs from cassette tape. This tape-friendly and RAM-saving solution was unique to the Jupiter ACE Forth.


Avoiding sources was compensated by storing comments entered in the code with the complied output, traditional compilation would discard such comments. The comments were then recovered on decompiling. As a result of "code is the source", modified words (edited) would demand actualization of all code using the one newly edited. This was done with the non standard REDEFINE command.

Although not explicitly designed for such a purpose, the compiled forth could be utilised for ROM extensions to the built in system. External ROMs were developed with Ace Forth to be used as control applications.[15][16]



The ACE had an 8 KB ROM containing the Forth kernel and operating system, and the predefined dictionary of Forth words in about 5 KB. The remaining 3 KB of ROM supported several functionalities: floating point numbers library and character definitions table, tape recorder access, decompiling and redefining newly re-edited 'words' (i.e. routines).[17] Some of the ROM was written in Z80 machine code, but some was also coded in Forth.

The next 8 KB were split in 2 blocks of 4 KB each. The video subsystem consumed 2 KB RAM and allowed the user to choose two different priorities, Regular or Overriding CPU contention. In the latter case TV Image timings were overidden, allowing more processor time for user programs at the expense of the display, which went blank.

The 1 KB of user RAM was only partially decoded, so it echoed in the full 4 KB block address space it resides. That is to say, the user program/data appeared to exist in four different memory locations.

The 1st 16 KB of the memory map was used for ROM, Video and User available RAM, leaving the 2nd 16KB of the memory map free for RAM extension and 32 KB undefined.



The Jupiter Ace was based on the Zilog Z80, which the designers had previous experience of from working on the Sinclair ZX81 and ZX Spectrum.


One 1K bank allowed redefinition of most of its 128 ASCII based characters in 8×8 pixel bitmap format. The other 1K bank stored the full screen display of 24 rows × 32 columns of characters in black and white. Colour was intended to be achieved as expansion, but although a colour graphics board was designed,[18] none was ever produced commercially.

Both graphics and text could be displayed at the same time: (1) redefinition of the character tiles provided standard 256×192 graphics limited to the 128 available (definable) 8×8 chars, concurrent with plotting of 64×48 graphics.


1 KB RAM with the option of a 16 KB RAM-Pack, and later a 32k one. A PCB was also marketed by Jupiter Cantab that converted the edge connector to electrical compatibility with a Sinclair ZX81, allowing use of the ZX81 16K RAM pack.[citation needed]


Internal speaker directly controlled by the CPU in single task mode, with control of sound frequency and duration in ms.

External Storage

Storage was through a cassette tape interface at 1500 baud. Files could be used for either storage of forth programs (compiled code) or raw dumps of memory.


The machine was able to use some ZX-81 add-ons due to similar RAM locations, and external expansion slot. Jupiter Cantab made a 16 KB RAM pack, and external companies made similar RAM packs as well as other peripherals and interfaces.

RAM packs[19]
  1. 16 KB by Jupiter Cantab.
  2. 16 KB and 32 KB by Stonechip Electronics.
  3. 16 KB by Sinclair, with adaptor board from Jupiter Cantab for electrical compatibility.
  4. 48 KB by Boldfield (new Jupiter ACE owner after Jupiter Cantab).
  • SoundBoard (1983) by Essex Micro Electronics,
  1. Jet-Disc Disc Drive System (1983) by MPE (control up to four 3", 5", or 8" drives).
  2. "Deep Thought" Disc interface with a 4K AceDOS in an EPROM (1986) by J Shepherd & S Leask.
Printer Adapters
  • ADS Centronics Interface Machine (1983), by Advanced Digital Systems,[23]
  • RS232 & Centronics PrinterCard (1984) by Essex Micro Electronics.[24]
Graphics Card
  1. Gray Scale card - 4 shades of gray by S Leask (1986)


Sales to the general public were limited by the use of Forth, when all other contemporary home computers used BASIC.[citation needed][25] The lack of published software, the poor case and small initial memory were also factors.


Jupiter ACE 4000

1982 - Original Jupiter ACE in a vacuum-drawn case - Reported 5000 units built.[26]

1983 - Jupiter ACE 4000 on stronger injection moulded case - Reported 800 units built.[27]


Sales of the machine were never very large; the reported number of Ace's sold before Jupiter Cantab closed for business was around 5,000.[28] As of the early 2000s, surviving machines are uncommon, often fetching high prices as collector's items.

Although it had originally be planned to have an on-board 4 KB of base RAM,[citation needed] it in fact shipped with just 1 KB - and the need to buy an extra 16 KB RAM-extension which almost doubled the ACE's price was one main reason for low sales.[citation needed]

Forth, while being structured and powerful, was considered difficult to learn, and a knowledge of BASIC acquired from familiarity with other home computers was of no practical help in learning it. A 1982 review stated that "The success of the Jupiter Ace will depend on the machine-buying public's acceptance of another microcomputer language."[29]

Further, there was only a very limited range of published software - either commercial programs or type-in programs printed in hobby magazines - for the machine, and these were restricted by the base model's small amount of RAM.[30]

Attempts to promote the Ace in the educational market also failed; doubts over whether Forth would be relevant for exam syllabuses, and the lack of support for Forth from teaching staff were key issues.[31] Pupils were more interested in learning the widely used BASIC than a language used by only one (uncommon) machine with a peculiar RPN syntax.[32]

Finally, the tile-based graphics compared poorly to the pixel-based graphics of other machines - which were also colour rather than the Ace's monochrome. This restricted sales largely to a niche market of technical programming enthusiasts.

See alsoEdit

Other Forth-based microcomputers:


  1. ^ "ZX81 killer in a post-Spectrum age?". 2012-08-01. Retrieved 2013-06-26.
  2. ^ "Sales brochure". Page 1
  3. ^ "Provence Trail - The Jupiter Ace". Retrieved 2016-07-29.
  4. ^ "An interview with Richard Altwasser and Steven Vickers".
  5. ^ a b c d e Vickers, Steven (1982). Jupiter Ace FORTH Programming.
  6. ^ "Unpopulated PCB".
  7. ^ Byte Magazine."Editorial". 1980,August. Special Edition.
  8. ^ James, John S. Byte Magazine. 1980, Aug. "What is Forth?", page 102, section "Characteristics of FORTH Code".
  9. ^ a b "Spectrum team deal their Ace". Popular Computing Weekly. 26 August 1982.
  10. ^ "Benchmarks (Entry #9)".
  11. ^ The Complete FORTH, by Alan Winfield, 1983, Sigma Technical Press, page xi.
  12. ^ Electronics & Computing. "Jupiter Ace Review". 1982, November. page 70.
  13. ^ Tecnologías Libres para Síntesis de Imagen Digital Tridimensional. p. 40. ISBN 978-84-689-9280-8. Micro Z80 a 3.25 MHz [...], el Jupiter Ace [...]
  14. ^ Winfield, Alan: "The Complete Forth", Chapter 9 "Extending FORTH", Sigma Technical Press, 1983.
  15. ^ "ACE User 4, page 8: ROM Expansion for the Ace" (PDF).
  16. ^ "FORTH User Vol2#1, page 2, "EPROMs for the ACE"" (PDF).
  17. ^ "ACE ROM Project (E-Book)".
  18. ^ "Adding colour to the Ace". article in ETI Magazine, April 1984
  19. ^ "RamPacks".
  20. ^ "Memotech Keyboard".
  21. ^ "EME AY-3-8910 Sound board Review".
  22. ^ "Disc Drives".
  23. ^ "ADS Centronics".
  24. ^ "Printercard".
  25. ^ "OLD-COMPUTERS.COM museum ~ Jupiter Cantab Jupiter Ace". Retrieved 2013-04-27.
  26. ^ "What is A Jupiter ACE".
  27. ^ "What is A Jupiter ACE 4000".
  28. ^ "What is an Ace".
  29. ^ "Jupiter Ace Resource Site - Your Computer Review, November 1982". Retrieved 2013-04-27.
  30. ^ "Jupiter Ace Software Index".
  31. ^ "Jupiter Ace Resource Site - Letter - Ace Goes Back To School in Popular Computing Weekly 11 November 1982". Retrieved 2013-04-27.
  32. ^ "The Jupiter Ace is 30 - Page 5 • The Register". Retrieved 2013-04-27.
  33. ^ "Micronique HECTOR HRX". OLD-COMPUTERS.COM Museum. Retrieved January 5, 2015.

External linksEdit