From: grog@lemis.com (Greg Lehey)
Subject: Anyone know what a Masscomp 5400 (54S-01) is?
Date: Sat, 22 Jan 2000 09:06:55 +0530 [thread overview]
Message-ID: <20000122090655.B455@mojave.worldwide.lemis.com> (raw)
In-Reply-To: <14472.36082.530024.331321@cley.com>; from tfb@cley.com on Fri, Jan 21, 2000 at 04:44:34PM +0000
On Friday, 21 January 2000 at 16:44:34 +0000, Tim Bradshaw wrote:
> * rdkeys wrote:
>> On a surplus junket, today, I ran across a 2 dollar chassis that was
>> listed as a Masscomp 5400 (54S-01) computer. It looked rather like
>> a DECish based thing with dual height cards, like some sort of laboratory
>> digital aquisition machine. On the long-shot that it is some sort of
>> PDP-11ish thing, anyone have any recollection or pointers to any info
>> on that kind of a Masscomp machine?
>
> Masscomps were 68k based machines, they had a whole bunch of stuff for
> real-time and data-acquistion type stuff. They ran something called
> RTU -- real-time Unix -- which was a weirdo sysv / BSD hybrid, not fun
> to use. If the 5400 is the machine I remember it's a 68020 machine
> but it may have a lot of cards for other stuff in. If it *is* the
> machine we had it was deeply unreliable. Masscomp got bought by
> someone else later on but I forget who, so they sometimes get badged
> as some other make.
>
> I would run away, fast.
On the other hand, IIRC this was the machine which was the basis for
the Egan/Teixeira (sp?) book on writing UNIX drivers. It might be
amusing for that reason alone. If it's functional and you have the
space, you probably won't regret the $2 you spend for it.
Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
next parent reply other threads:[~2000-01-22 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200001211607.LAA12512@uni02du.unity.ncsu.edu>
[not found] ` <14472.36082.530024.331321@cley.com>
2000-01-22 3:36 ` Greg Lehey [this message]
2000-01-23 21:29 ` John Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000122090655.B455@mojave.worldwide.lemis.com \
--to=grog@lemis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).