Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!Lear@RU-BLUE.ARPA
From: Lear@RU-BLUE.ARPA (eliot lear)
Newsgroups: net.micro
Subject: My interesting Experiences with the 3B2 (to say the best!)
Message-ID: <453@brl-tgr.ARPA>
Date: Mon, 5-Aug-85 21:17:39 EDT
Article-I.D.: brl-tgr.453
Posted: Mon Aug  5 21:17:39 1985
Date-Received: Wed, 7-Aug-85 04:18:59 EDT
Sender: news@brl-tgr.ARPA
Lines: 32

Hello,
	I work in a Microcomputer Lab at Rutgers University and we have been
	working with the AT&T 3B2 for roughly 2 months.  At this point I wish
	mention my experiences and I am curious if anyone has had the same of
	troubles.

		No sooner was our 3B2 plugged in and set up when it crashed.
	The only thing we could get out of the machine was "DISK SANITY ERROR"
	and this did not thrill us.  As recommended in the owners manual, we
	called AT&T that night.  The person said he would be over the next day.
	To make a long story short, it took him a week to get here and several
	days to replace the hard disk.
		After the hard disk problem, the system functioned normally
	(for a 3B2) which means NO csh or ksh, OPTIONAL uucp software (which
	took us another 3 weeks to get), and extremely limited help.  (There
	is no `man` facility on a 3B2.  They use an extremely limited `help`
	program.)
		After we received the uucp software, we discovered that the
	pin arrangement on a 3B2 is quite unorthodox.  To connect to modem
	or direct line the 3b2 requires a warped null modem cable.
		As of late, the system has been crashing for no apparent reason
	approxomately every two weeks.  There are no symptoms beforehand
	and directly afterwards, the diagnostics light blinks.
		I am coming to the point of despair with this computer.  I
	wish I could say something good about the 3B2.


						eliot lear

[lear@ru-blue.arpa]
[{allegra,seismo,inhp4}!topaz!lear]
-------