Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!nntp-server.caltech.edu!rknop
From: rknop@nntp-server.caltech.edu (Robert Andrew Knop)
Newsgroups: comp.sys.cbm
Subject: Re: 1750 REU problems
Message-ID: <1991Jan18.033632.23033@nntp-server.caltech.edu>
Date: 18 Jan 91 03:36:32 GMT
References: <9101180107.AA27760@gn.ecn.purdue.edu>
Organization: California Institute of Technology, Pasadena
Lines: 28

rferguso@ECN.PURDUE.EDU (Robert S. Ferguson) writes:

>I did try the REU with a nearby 64C, and it worked fine.  I think the
>problem is in my 128.  Has anybody else had a problem like this?
>Any suggestions as to what I should try next would be appreciated.

I had problems similar to this with my 1750.  It started doing weird things
under GEOS, so I ran one of the tests that came with it on it, and sure
enough it failed.  It was still under warranty, so I took it into a service
center.  At the service center, I tried the REU on another 128- and it worked
fine.  Nothing we could do could get it to fail.  Indeed, it wouldn't always
fail on mine.  To get it to fail, I had to have a couple of disk drives, a
modem, a printer, and maybe even a joystick plugged in.  (I don't remember
exactly, but I did have to have other stuff plugged in.)  A replaceemnt
didn't fail, even with everything plugged in, so we concluded that the problem
was with the REU- but it was a borderline problem such that only some
machines would fail with it.

If your problem is similar, it's a combination of your 128 and your REU.  I
would recommend trying it out on another 128.  Is it still under warranty?
Does it have a warranty?  If so, it may be worth trying to get it replaced.
If it doesn't work, try removing your modem (etc.) before you turn on the 128
to boot up GEOS, or the test, or whatever.

Good luck!

-Rob Knop
rknop@tybalt.caltech.edu