Jay West wrote:
Billy wrote....
What about the MicroData machines with a build
your own
instructions on the fly?
SortofKindaNotReally
MicroData Reality machines were firmware implementations of Pick
(Reality), not software implementations. As a result, you couldn't
actually microprogram the thing as an end user (normally).
The Microdata 800 was the first machine to run reality, 4k of memory, 8
ttys, 2mb disk. most who saw it demoed could not believe it could
actually be running the tty's at the time and followed the wires to be
sure. Had english, but no basic in the first days. all programming
with procs, batch, and english, plus custom assembly code.
Following the 1600, Microdata made Sequel machines which were 64 bit
2900 based microcoded custom machines.
There *WAS* an EEPROM board that would replace the
firmware board, but
I don't believe that was typically released to the field.
I used to have two M1600's (the early ones with the wood panels). One
of them did have the EEPROM microcode option but I do know that
particular unit was sent out from microdata "under the table". I had
let these two machines slip through my fingers many years ago, long
before I got into collecting. BUT - on the bright side - I found out a
year or so ago that those two machines actually did wind up in the
hands of another collector who is known to another listmember!
:-)
they had what they called Arom, for alterable rom. It was a really fast
and expensive three voltage ram part, which was 64 x 1 IIRC. it had to
have about 100ns response time, and was static.
there never was an eprom fast enough for the 1600 before it was not an
issue. We built a development system for our 1600 with two 8k static
parts though (Irvine Compter Corp's version)
I also used two of the parts that they had in the 1600 for the file
registers which were 4 bit x 32 to make a simple memory that you could
program thru the front panel of the 1600, by adding a switch to generate
a write pulse when you had a 16 bit control word and address in the
panel display. Good for debugging the 1600, which had several
instructions which affected the instruction following in the microcode,
but whose affect was suppressed when stepping.
I now have an M1600 that is the later metal panel
variety, waiting to
be restored.
Even on the software implementations (which the microdata's weren't),
you could create new missionary instructions from native instructions
by playing some games in the 5-pass assembly process. However, this
wouldn't technically be considered microprogramming as the "native"
instructions would be just whatever the underlying cpu was (68000,
PDP11, RS6000, x86, etc.). So you could create new virtual
instructions, but still not really microprogramming.
Jay