Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!hplabs!hp-sdd!ncr-sd!crash!jkimble
From: jkimble@crash.cts.com (Jim Kimble)
Newsgroups: comp.sys.ti
Subject: Re: What is this?
Message-ID: <2785@crash.cts.com>
Date: 8 Apr 88 00:49:07 GMT
References: <186@snjsn1.SJ.ATE.SLB.COM> <Mar.30.11.33.27.1988.27994@topaz.rutgers.edu> <38032CXH@PSUVMA>
Reply-To: jkimble@crash.CTS.COM (Jim Kimble)
Distribution: comp.sys.ti
Organization: Crash TS, San Diego, CA
Lines: 34
Summary: TI does make good professional computers


Regarding an earlier crack about TI and the fact that they "once dabbled in
the Professional Computer industry" (or words to that effect), you haven't
been keeping up.

As a disqualifer, I was one of the many who expanded their TI-99/4A to it's
limits only to be sh*t on a little later when TI backed out.  And the TI
Pro hasn't helped public relations any.  But lately TI has come out with some
decent hardware -- namely the 1000 series.

TI's TMS990 (versus the TMS9900) machines have been out in the business world
for many years, and many of them are still in use.  Beleive it or not, but
TI *still* supports the DX10 and DNOS operating systems.

But anyway, the latest and greatest hardware is the Business System 1500
(which is a multiprocessor [68020-based] minisuper computer).  And the BS1600,
which is basically the same system with a larger chasis that can handle more
processors, handles up to 256 users while maintaing decent system preformance.
One of the nice things about the 1500/1600 systems, is if you want to slap
another processor in the box, all you do is power it off, put in the new
card, and turn it back on.  That simple.

I use a 1500 at work for developement (it's Unix SystemV based) and I'm 
quite impressed.  For the most part, TI has been gaining points in the 
industry lately. . . maybe they turned over a new leaf.


--Jim Kimble

"I used to be into necrophillia, flagellation, and beastiality -- but my
friends said I was just beating a dead horse."

UUCP: {hplabs!hp-sdd, sdcsvax, nosc}!crash!jkimble
ARPA: crash!jkimble@nosc
INET: jkimble@crash.CTS.COM