Discussion:
MACE 5 tape lost
(too old to reply)
Tom Hunter
2003-08-20 12:55:37 UTC
Permalink
Unless you have a reel containing MACE 5, then the last working copy I know
of has been lost.
It was obtained in May 1970 from MACE author Greg Mansfield, handed to
Northwestern U programmer Larry Atkin, probably in exchange for a copy of
CHESS. It was then conferred upon NU programmer Chuck Filstead, who adapted
small parts of MACE, including its influential coding standard, into NU's
SCOPE. In 1973 the tape was conferred to me.
Then a programmer at Michigan State U, I re-assembled the entire system and
re-built the deadstart for use in research projects. At the time, MACE was
the only general-purpose CDC system that could be configured on-the-fly for
different cpu and storage arrangements.
The tape, sealed in its original plastic cannister, and a padded cardboard
travel container, found its way to my father's office building, where he
stored it for twenty-nine years. It continued to exist during the entire
time Tom Hunter and others were searching for early CDC systems to test the
Desktop Cyber project.
My father sold the building and in July 2003 the new owner cleared the
storage room. When I mentioned the MACE tape to my dad, he recalled
possessing the container, but alas, the new owner's massive trash truck had
been removed to the landfill the previous day.
:-(

What a sad waste. You knew about the tape and you knew about many
people hunting for MACE 5. I don't know what to say!

:-(
Dave Mausner
2003-08-23 00:17:39 UTC
Permalink
To close the loop with the group, i had not seen the tape in 29 years, so
nobody knew it existed.

Anyway, the lesson is: DON'T LET IT HAPPEN TO YOU!

--
Dave Mausner / v.+1-708-848-2775 / f.+1-708-848-2569 / c.+1-312-wake-my-i
Post by Tom Hunter
Unless you have a reel containing MACE 5, then the last working copy I know
of has been lost.
What a sad waste. You knew about the tape and you knew about many
people hunting for MACE 5. I don't know what to say!
:-(
MSCHAEF.COM
2003-08-24 17:21:44 UTC
Permalink
Unless you have a reel containing MACE 5, then the last working copy I know
of has been lost.
...
At the time, MACE was
the only general-purpose CDC system that could be configured on-the-fly for
different cpu and storage arrangements.
Can you post a little more about what MACE was, exactly? Is it correct
to assume it's an Operating System for CDC systems?

-Mike
--
http://www.mschaef.com
Dave Mausner
2003-08-29 17:35:55 UTC
Permalink
re: what was MACE? from my memory of CDC legends, it goes like this.

at the arden hills minnesota fabrication plant, there were many mainframes
on the floor in various states of assembly and testing. in the same building
were a programming staff who i believe were tasked with developing
maintenance tools and custom software projects.

the engineers needed basic operating systems to run diagnostics on all those
mainframes. the best-known was SMM which ran just diagnostic programs. i
suspect that some engineers believed that a system which could run a normal
mix of user code and system functions would be a more complete test
environment. MACE apparently originated in that environment.

the primary author appears to have been greg mansfield. i was told that the
acronym meant "mansfield and cahlander executive", referring also to dave
cahlander, author of the compass version 2 assembler.

MACE used the same classic architecture as seymour cray's COS: a batch job
philosophy in which the ppu were mostly in control of the situation and the
cpu and most of its memory were free for maximal use by user programs, which
were allocated at some maximum number of job control points.

MACE refined the concept of job scheduling by class-of-origin and other
dynamic parameters. however, it contained no provision for permanent
rotating mass storage nor for on-line removable devices. you really couldn't
do anything with MACE after dead starting--there were no applications as we
know the term today. other than an IBM O26 keypunch emulator, Northwestern's
CHESS game, and some goofy SMM toys, it was assumed that everything
originated from cards and tape.

MACE came with a small code development environment comprising the DIS
memory debugging interface, COMPASS assembler, the MODIFY code repository
manager, the LIBEDIT library file manager, and the LINK relocatable module
editor. these allowed engineers to do their coding, assembling, and
debugging on a six-million-dollar mainframe more or less as we do today on a
five-hundred-dollar PC.

MACE had its problems--it had instituted the idea of loading device drivers
on demand into pp-resident memory. this strategy haunted later developers,
due to overlay handling and ppu memory management. it also meant that the
o/s could not optimize disk head movement at a time when the heads were
pushed hydraulically.

despite my sorrow at losing MACE 5, it still lives intact within KRONOS.
version 1 was essentially MACE 5 plus a teletype multiplexor front-end
called TELEX, permanent files using the direct/indirect access concept; and
some oddball stuff devoted to inter-mainframe communication. i believe that
several other key CDC programmers contributed greatly to the evoluation of
KRONOS; but mansfield's participation seemed to decline thereafter. his
career output was extremely influential, especially within the academic
community, and deserves to be better documented.

the main attribute and attraction of MACE was its exceptional cleanliness
and minimalist organization. the coding style was obsessive but in its
consistent rigor, passed a major watershed in man-machine interface: the
production of human-readable code. this subject, which mansfield had
perfected in the late 60's, was not addressed again in the literature until
microsoft's _code complete_ book in the late 90's. it re-invents many of
mansfield's principles of design, including the use of white space,
importance of internal commentary, and strict nomenclatures for storage
objects.

i recall as well that MACE style employed a highly modular algorithmic
approach which recognized the importance of data structures. the separation
of data and code, and the provision of adequate tools for dynamically
managing data, are problems mansfield anticpated, and which are obviously
still not properly addressed in the windows architecture 35 years later.
--
Dave Mausner / v.+1-708-848-2775 / f.+1-708-848-2569 / c.+1-312-wake-my-i
Post by MSCHAEF.COM
At the time, MACE was
the only general-purpose CDC system that could be configured on-the-fly for
different cpu and storage arrangements.
Can you post a little more about what MACE was, exactly? Is it correct
to assume it's an Operating System for CDC systems?
Douglas A. Gwyn
2003-08-29 19:37:50 UTC
Permalink
Hopefully information such as that contained in the previous posting
will be archived on-line somewhere! It is pretty hard to find much
about pre-Internet systems.
Al Kossow
2003-08-29 22:06:19 UTC
Permalink
Post by Douglas A. Gwyn
Hopefully information such as that contained in the previous posting
will be archived on-line somewhere!
It is in the Google news archive

http://groups.google.com/groups?q=MACE+5+tape+lost+-+memories&hl=en&lr=&ie=UTF-8&selm=%259M3b.16873%24Ih1.5975920%40newssrv26.news.prodigy.com&rnum=1
Loading...