On Thu, Apr 21, 2016 at 12:07 AM, Raymond Wiker <rwiker at gmail.com> wrote:
> I was a bit surprised to see that it used 2901 with a date code of 1985 -
> the 2901 was introduced 10 years before.
The 2901 was the workhorse bit-slice data path chip for many years.
The A, B, and C suffix parts were progressively faster variants
introduced later. Eventually there were CMOS versions, and 16-bit-wide
versions. While AMD introduced the 2903 and 29203 as functionally
improved (but not directly compatible) 4-bit parts, they weren't
nearly as widely used as the 2901.
Most other bit-slice parts can be considered "also-ran" at best, with
the Intel 3001 and 3002 probably being the next most successful. MMI
tried to beat AMD to market with the 5701/6701, which was very similar
to (but not compatible with) the 2901, but they were late to market
and AMD won.
Motorola offered the MC10800 ECL bit slice series, which were
significantly faster at introduction than the contemporary Am2900
parts, but AMD kept introducing faster 2901s. Some later 2901
variants from AMD and National Semiconductor actually used ECL
internally, but had normal TTL I/O, but the CMOS that followed were
even faster than those.
> From: Jon Elson
> The 11/45 and 11/70 are mostly the same processor. ...
> the data paths boards and FPU are the same part numbers
'Yes' to the FPP (well, there are two versions, the FP11-B and FP11-C, but
they are both identical in the two machines).
'No' to the data paths, though: e.g. the M8100 in the /45 (the board with the
74S181's on it) is replaced by the M8130 in the /70. The two are _very_
similar, but I suspect not interchangeable (examing the prints shows minor
differences).
AFAIK, the only non-FPP board in the CPU which is interchangeable between the
two machines is the M8132 (instruction register decode & condition codes) -
and only to the KB11-D /45 variant, not the -A.
{As always, just want to be accurate! :-}
Noel
> AFAIK, the only non-FPP board in the CPU which is interchangeable
> between the two machines is the M8132 (instruction register decode &
> condition codes)
So it seems like there's an(other) error in the DEC documentation.
If one looks at 11/70 Maintenance Manual (EK-11070-MM-002), it says (pg. 1-3)
that the KB11-C (11/70 later CPU) contains an M8133 ROM and ROM Control
board, the same as the KB11-B (earlier CPU, pg. 1-4), _but_ ...
The KB11-C prints include the drawings for the M8123 (also used by the
KB11-D, the later /45 CPU). Other manuals confirm that the KB11-C uses the
M8123 (see, e.g., the KB11-A,D Maintainence Manual, EK-KB11A-MM-004, pg 1-1).
I _thought_ the KB11-D used two of the same boards as the KB11-C, but then,
when I went to check, to be sure I had the correct info (before sending out
my email intended to "just want to be accurate", sigh), I relied on the DEC
manual... :-(
Oh well, that's what I get for relying on DEC manuals! :-)
Noel
> From: Jules Richardson
> I can't see the point in modern upgrades .. At the point where people
> start adding emulated storage, USB interfaces, VGA display hardware
> etc. it stops being a vintage system and starts being a modern version
> which just happens to still have a few vintage parts.
I agree with you to some degree, but...
Some components are just hard/impossible to find now - like old original disk
drives (seen any RP0x's for sale recently?), or Able ENABLE's - and in any
case running the disks is both non-trivial (power/heat) and risks damaging
what are effectively museum pieces.
So one is left with the choice of modern replacements, or nothing. And I'm
not capable of building an RP0x, but building a board that uses an SD memory
card to emulate an RP0x, that's within my grasp. And it takes a lot less room
and power, to boot.
Also, the _systems_ were designed to have upgrades installed, and did, BITD -
many of which were not conceived when the machine first came out. E.g. our
11/45 at LCS wound up with 1MB MOS memory boards in it (much smaller and less
power-hungry than the original memory), and high-speed LANs, neither of which
were ever envisaged when the machine was built.
I don't see that building, say, a UNIBUS USB interface now is really that
different from building a high-speed LAN board BITD.
I do agree that if you replace stuff that _is_ still available and perfectly
functional (e.g. QBUS memory and processors), you might just as well run a
simulator. But there's a lot of stuff that's not in that category (above).
Noel
Mark J. Blair wrote:
> I also seem to remember an operator's console with two round CRTs on
it,
> but I might have fabricated that memory from whole cloth.
>
I think that you were remembering the console of one of the Control Data
6000/Cyber-70 series computers that you may have seen somewhere. This
series of Control Data machines were famous for their consoles with two
large, round, green-phosphor monitors that used vector drawn-characters
(generated by one of the Peripheral Processors). Most of the normal
system screens were all text, but there were some special programs
written (including a nice graphical chess game, a little program that
would put up eyes on the screens that would look around and blink, and
some others that don't come to mind at the moment.
I operated one of these systems
(a Control Data Cyber 73 --
http://bitsavers.trailing-edge.com/pdf/cdc/cyber/brochures/Cyber70_Mod73
_Feb71.pdf)
at Tektronix in Beaverton, Oregon, from 1977 through around 1980. It
had two CPUs, 131K (60-bit words) of core, ECS (extended core storage),
and 20 Peripheral Processors, a combined punched card reader/punch,
something like 12 "washing machine" type multi-platter cartridge disk
drives (that held something like 300 MB each), two 9-track tape drives
and one 7-track tape drive. It also had a big chain printer that was
noisy, but pretty fast.
The machine had a channel interface to a Modcomp communications
processor (with communication maintained by one or more Peripheral
Processor programs), that provided serial I/O to terminals scattered all
over the company by some kind of serial concentrator that I can't
remember. There was also a big modem pool for dial-in use. The
system ran a locally-modified version of the Kronos Timeshared operating
system. The system was used primarily by engineering departments
(research and product development) for CAD and CAD software development,
circuit simulation (SPICE), cross-assembling microprocessor code, and
mathematical modeling.
The machine was an all-transistor design, based on the CDC 6600
processor. It was liquid cooled, and had a large cooler unit that sat
with the machine that cooled the coolant (water) and circulated it
through the chassis, venting the heat (which was substantial) through a
special venting system. I remember the CDC Field guys talking about
horror stories when there were leaks in the cooling system. We never
had any problems while I was there.
One day I was at the console when one of the big high-voltage rectifier
tubes that were in the console decided to short.
I was watching one of the system monitor displays, and suddenly I saw
the display collapse into a single very bright horizontal line. I noted
that the other display also did the same thing. I also heard a funny
noise that sounded kind of scary, so I started to push my wheeled chair
away from the console, but not soon enough to avoid a shower of sparks
and even some molten metal that spewed out from the console. I had a
few small burns on my arms, and one little blob of molten metal burned a
hole in my pant leg. One of the other operators in the machine room
managed to hit the power switch for the console and shut it off. Then
the fire suppression alarm went off indicating that the Halon was going
to dump soon, so he ran back and hit the override since the sparking and
smoke had settled once the power was off. Despite this, the fire
department showed up (the fire suppression system in the computer room
had a direct line to the fire department), and we had to tell them it
was a (semi) false alarm.
The machine kept running just fine, and we were able to keep tabs on it
with a serial terminal hooked up to the machine that had a program
running that kind of emulated the console displays. The CDC guys were
there very quickly, and ended up having to replace two (IIRC) big
rectifier tubes, and one burnt up power resistor. When they powered it
up, the screens came up just as they were before the event occurred, and
all was well.
I really enjoyed those days. The machine was really cool, and I have a
lot of great memories of those times.
The Living Computer Museum (http://www.livingcomputermuseum.org) in
Seattle, WA, has rescued a smaller version of a system like this based
on the 6500 processor that is undergoing restoration.
Sorry for changing the subject (but at least I updated it in the
Subject: line).
-Rick
--
Rick Bensene
The Old Calculator Museum
http://oldcalculatormuseum.com
A friend building a Z80 system asked me about whether the Z80 /WAIT
signal has any effect during machine cycles that aren't
memory/IO/intack cycles (i.e., neither /MREQ and /IORQ asserted). The
user manual only describes the use of /WAIT for adding wait states, so
I expect it probably only affects mem/IO/intack cycles, but I can't
find anything definitive in the user manual.
I'm hoping someone can save me the time of hooking up a logic analyzer
and running the experiment.
Thanks!
Eric
In development. Inspired by the Spare Time Gizmos STG1861, but not
based on that design. Rev. 0, not yet ready for production:
https://www.flickr.com/photos/22368471 at N04/sets/72157667299828132
It is 2.0 inch by 0.7 inch, with a 24-pin round-pin DIP header to plug
into a normal 24-pin DIP socket (vs. more the common square pins that
won't work with normal IC sockets).
The surface-mount components were assembled onto the board by a
commercial service, which does not do through-hole, so I had to solder
the DIP header by hand. I had to make the pads for the DIP header
very small to squeeze the TQFP CPLD between the rows, so it turns out
to be unsuitable for hand assembly by novices. Since I am not willing
to do the hand assembly for other people, I'm not sure whether this
board would actually be worth selling; I might have too many customers
that aren't able to assemble it successfully.
The CPLD programming is done by a "Tag Connect", which uses pogo pins
to contact the ten gold pads seen on the top of the board. There are
holes near those pads for the Tag Connect's steel alignment pins;
while there is enough clearance on the top of the board, I failed to
consider that the frame of the DIP header on the bottom of the board
would prevent two of the alignment pins from extending far enough. I
had to cut out part of the DIP header frame.
The CPLD code has been written but has not yet been debugged.
From: John Willis
Sent: Thursday, April 21, 2016 8:02 AM
> That's another thing I remember and miss from those days... your average
> ISP would provide NNTP and UNIX shell accounts, as well as a few megs of
> space to put up a personal web site in ~/public_html.
I still read Usenet newsgroups via GNUS under Emacs on my shell account on
Panix, an ISP located in Manhattan, and have a small web site hosted there
as well:
http://www.panix.com/~alderson/index.html
Some things are too important to relegate to a web browser.
Rich
Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computer Museum
2245 1st Avenue S
Seattle, WA 98134
mailto:RichA at LivingComputerMuseum.orghttp://www.LivingComputerMuseum.org/
I did not use the H800, but I cut my computing teeth on smaller Harris models in college (where my work study job was in the computer center, and I was also a computer science major) and then part-time employment afterwards with the Army Corps of Engineers, which was big on Harris computers at the time. This was in the late 1970s to mid-1980s. I used first a model H150 and then the H550 after they upgraded. I even worked for a contractor part-time who had a Harris H120 (I think that was the model number) in his basement for engineering computing. I don't remember what models the Army COE used at the time - H500s of one variant or another I believe.
I thought these Harris computers were all a great system, the bees knees as far as I was concerned, far better than any full-blown PDP-11 system at the time (and no doubt cost more as well at the time). There are documents on these systems on Bitsavers. Everything was blue in color, and the console was a CRT that ran in block transmission mode, grabbing either one full line or the entire page off the screen at a time, feeding into the DMCP board. The H150 we had in college had two 80 Mbyte CDC drives, and later we added a 300 Mbyte CDC drive when we upgraded to the H550 model. The tape drive was a non-vacuum 1600 bpi drive, and I spent many hours backing up the system onto tape, and then swapping drive packs and downloading everything again. I vaguely recall that we did that drive swapping once a week in the wee hours of the morning.
The Vulcan Operation System (VOS), which later was called VMS, I thought was a cool system, but then I didn't have anything to compare it against. We had Fortran, Basic, Cobal, RPGII, and assembler, plus a version of Runoff so students could write papers that got printed on a Diablo. I spent many hours on that system after hours (I had a key to the college computer center), and even started writing my own tape operating system for fun. We had terminals strung all over campus feeding into the system, connected by long runs of serial cables in the heating tunnels; I spent many hours in those heating tunnels as well, as we had to fix things every time lightning from storms would take out the RS232 chips at either the terminals or on the DMCP board in the computer. I got to know the area Harris field engineer pretty well - he was a chain-smoker that constantly had a cigarette in his mouth, even while working on the computer. I watched him do many a system upgrade to boards, which were all discrete TTL chips and parts that were wire-wrapped at that time.
I'd love to know if any Harris computers still exist today. The ones I knew were all scrapped out years ago. I know if I tried to use one today, I'd get really frustrated with the OS, being as used to Linux/Unix as I am today. Harris did come out with a Unix OS for their computers in the mid-1980s, but I never used it.
Fond memories.
Kevin Anderson