kdavis@lamc.UUCP (Ken Davis) (09/04/89)
Info-3b2 Digest, Number 89 Sunday, September 3rd 1989 Today's Topics: AT&T Price Quotations Re: 3B2 problems galore Starlan RS232 NAU Re: Starlan RS232 NAU 3B2 problems galore ---------------------------------------------------------------------- Subject: AT&T Price Quotations From: info-3b2@netsys.com Date: Tue, 01 Aug 89 12:46:06 -0400 Subject: AT&T Price Quotations CTI is a Dutch softwarehouse that has been using AT&T 3B2 computers in the past 4 years. As you may know AT&T has a marketing agreement with Olivetti in Europe. The Italians are not very supportive and do not want to position the 3B2 versus their own LSX-baby. Other than by this Italian connection, the AT&T computer division is not represented in Europe. We are looking for a possibility to import AT&T computers from the US to Holland and we would like to receive offerings from US-based AT&T VAR's. We are particularly interested in the 3B2-range and powerful 80386-boxes with the Unix system V/386 operating system. Please forward information and quotations by e-mail or snail mail. -- --------------------+----------------------+----------------------------------- Paul Hutteman | phone: +31 70 542302 | CTI Software BV paul@ctisbv.UUCP | fax : +31 70 512837 | Laan Copes van Cattenburch 70 ...!uunet!mcvax!hp4nl!ctisbv!paul | 2585 GD The Hague, The Netherlands ------------------------------ Subject: Re: 3B2 problems galore Date: Sat, 2 Sep 89 15:36:56 BST From: Graham Glen (Technical Manager) <netsys!pyrdc!uunet!qukmips!graham> > > The hard drive problems are not the most vexing ones, however. I have two > machines that were working at one time, but stopped suddenly for no apparent > reason. When I try to boot them, the power light comes on and stays on, but > the diagnostic light goes "flash, flash, flash, flash, flash, flash...pause" > and repeats this pattern over and over. Somebody here at Tech who has worked > rather extensively with the 3B2s suggested that maybe the boot ROMs were bad. > I swapped out the ROMs with known good ones, but nothing changed. > > I took one of the machines apart, removed all the memory and peripheral cards, > and decided to start plugging things in until it broke. With nothing in it > but motherboard and floppy disk, it did a SELF CHECK, accessed the disk drive > once, and then the power light went out, but the diagnostic light stayed lit > continuously. I plugged in two 1 Meg RAM cards and got the same thing. If I > press the RESET button, then the power light comes back on and the diagnostic > light begins flashing as before. The DIAGNOSTICS won't run at all. > I have had exactly this problem before. In my case, I swapped parts from a known working system until I had replaced the entire machine, and it still would not work. The reason I found in the end was that the cable from the terminal to the console port had got damaged, the machine was not seeing a complete set of hardware handshaking lines, and so refused to play ball. Try swapping the console cable for another one which you know works, and also put a breakout box on the terminal to check whether all the necessary handshaking lines are being generated. It may cure the problem. Graham -- Graham Glen | Voice +44 1 371 5755 Quadratron Systems (UK) Ltd. | +44 836 380006 (mobile) {quad1,qnorth,qswiss,ukc,attunix!uel}!quaduk!graham "I may not have gone where I intended to go, but I think I have ended up where I needed to be." ------------------------------ Date: Sun, 3 Sep 89 12:00 EDT From: Uwinken@netsys.netsys.COM (Lawrence Livermore Labs) Subject: Starlan RS232 NAU Gatewayed into The Info 3B2 Mailing List at netsys.com ============================================================== From: pjh@mccc.uucp (Pete Holsberg) Subject: Re: Starlan RS232 NAU Date: 3 Sep 89 03:17:48 GMT Reply-To: pjh@mccc.UUCP (Pete Holsberg) Distribution: u3b Organization: The College On The Other Side of U. S. Route 1 In article <15688@netsys.netsys.COM> len@netsys.COM (Len Rose) writes: =Hi.. I am getting ready to hook up some telebit trailblazers =to the RS232 NAU and was wondering if anyone has any comments =about it.. Is the rs232 NAU different from the std NAU? The NAUs in my 3B2/400s each have a "hole" marked "phone" (I think) but I didn't find any documentation on how or what. What can you tell me? Thanks. -- Pete Holsberg -- Mercer College -- Trenton, NJ 08690 ...!rutgers!princeton!njsmu!mccc!pjh ------------------------------ Date: Sun, 3 Sep 89 12:15 EDT From: len@netsys.netsys.COM (Len Rose) Subject: Starlan RS232 NAU Gatewayed into The Info 3B2 Mailing List at netsys.com ============================================================== From: len@netsys.netsys.COM (Len Rose) Subject: Re: Starlan RS232 NAU Date: 3 Sep 89 16:14:43 GMT Reply-To: len@netsys.COM (Len Rose) Distribution: u3b Organization: Netsys,Inc. The RS232 NAU is an external stand alone device which allows one to interface standard rs232 devices onto a starlan network. It provides support for terminals and modems. It's really a nifty device,allowing one to have a starlan printer,data terminal,modem directly attached to the net.. I haven't received mine yet,but when I do, I'll know more. Len ------------------------------ Date: Sun, 3 Sep 89 03:16 EDT From: daemon@netsys.netsys.COM (The Daevil) Subject: 3B2 problems galore Gatewayed into The Info 3B2 Mailing List at netsys.com ============================================================== From: info-3b2@netsys.COM Subject: Re: 3B2 problems galore Date: 3 Sep 89 07:16:13 GMT Sender: daemon@netsys.netsys.COM From: Graham Glen (Technical Manager) <pyrdc!uunet!qukmips!graham> > > The hard drive problems are not the most vexing ones, however. I have two > machines that were working at one time, but stopped suddenly for no apparent > reason. When I try to boot them, the power light comes on and stays on, but > the diagnostic light goes "flash, flash, flash, flash, flash, flash...pause" > and repeats this pattern over and over. Somebody here at Tech who has worked > rather extensively with the 3B2s suggested that maybe the boot ROMs were bad. > I swapped out the ROMs with known good ones, but nothing changed. > > I took one of the machines apart, removed all the memory and peripheral cards, > and decided to start plugging things in until it broke. With nothing in it > but motherboard and floppy disk, it did a SELF CHECK, accessed the disk drive > once, and then the power light went out, but the diagnostic light stayed lit > continuously. I plugged in two 1 Meg RAM cards and got the same thing. If I > press the RESET button, then the power light comes back on and the diagnostic > light begins flashing as before. The DIAGNOSTICS won't run at all. > I have had exactly this problem before. In my case, I swapped parts from a known working system until I had replaced the entire machine, and it still would not work. The reason I found in the end was that the cable from the terminal to the console port had got damaged, the machine was not seeing a complete set of hardware handshaking lines, and so refused to play ball. Try swapping the console cable for another one which you know works, and also put a breakout box on the terminal to check whether all the necessary handshaking lines are being generated. It may cure the problem. Graham -- Graham Glen | Voice +44 1 371 5755 Quadratron Systems (UK) Ltd. | +44 836 380006 (mobile) {quad1,qnorth,qswiss,ukc,attunix!uel}!quaduk!graham "I may not have gone where I intended to go, but I think I have ended up where I needed to be." ------------------------------------- To join this group or have your thoughts in the next issue, please send electronic mail to Ken Davis at the following address; {apple, netsys, pacbell, pyramid}!lamc!info-3b2-digest The views expressed in Info-3b2 Digest are those of the individual authors only. ********************** End of Info-3b2 Digest **********************