The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brantley@coraid.com (Brantley Coile)
Subject: [TUHS] AT+T UNIX PC Information needed
Date: Sat, 18 Feb 2006 09:34:23 -0500	[thread overview]
Message-ID: <f79fcb134f8eefb41d6f789ef8797d96@coraid.com> (raw)
In-Reply-To: <200602181048.16424.duncangareth@yahoo.co.uk>

The tree you're barking up has fruit.  I know the schematics are
out there.  I used to have a set, but have since lost them.

I've used several 7300s.  The hardware was designed by convergent
technologies.  It has a wonky graphics interface because of a poor
choice of a monitor.

There should be simple power converters to give you 120v at 60 Hz.

The 7300 was used as a console for some of the AT&T PBXs, so there was
a lot of them made.  They had the bigest expansion slots I have ever
seen, going almost the entire depth of the box, which was too deep.
Key action on the keyboard was nice.  The unicomp keyboad that I now
use has similar action.

If AT&T had put some version of Unix other than System V, there might
have been life in the old girl.  The UNIX PC and the DMD terminals had
this myopic corporate protectionism in common.  I always thought that
if the DMD5620 had been cheaper and they had had OS support for BSD as
well as System V, the history of computing would have been very
different.  I couldn't get my boss to pay $6K for a terminal when the
average price for a nice terminal was $1K.  If he had let me buy one,
I then would have had to port the support code.  Compilers, the Mux
communiction protocol, all the programs that ran in the terminal,
would have had to be change to run under the non-System V system that
we were using at the time.  AT&T's decisions during the period
displayed a persistant lack of undertanding marketing.  If the
customer came first, they would have supported the OS customers
wanted.
-------------- next part --------------
An embedded message was scrubbed...
From: Duncan Anderson <duncangareth@yahoo.co.uk>
Subject: [TUHS] AT+T UNIX PC Information needed
Date: Sat, 18 Feb 2006 10:48:16 +0200
Size: 3001
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20060218/b4e2e1b7/attachment.mht>


  reply	other threads:[~2006-02-18 14:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  8:48 Duncan Anderson
2006-02-18 14:34 ` Brantley Coile [this message]
2006-02-18 15:25   ` Duncan Anderson
2006-02-18 15:32 ` Corey Lindsly
2006-02-18 20:19 ` Robert Tillyard
2006-02-18 15:44 Mike Haertel
2006-02-18 16:48 ` Michael Davidson
2006-02-20 10:03 ` Duncan Anderson
2006-02-21  3:46 Brian S Walden
2006-02-21  4:52 ` Corey Lindsly
2006-02-21  8:58   ` Duncan Anderson
2006-02-21  8:56 ` Duncan Anderson
2006-02-21 17:00 ` Sven Mascheck

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=f79fcb134f8eefb41d6f789ef8797d96@coraid.com \
    --to=brantley@coraid.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).