Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!atha!aunro!ersys!drin From: ersys!drin@nro.cs.athabascau.ca (Adrian Smith) Newsgroups: comp.sys.next Subject: Re: major SCSI disk problem (?) Message-ID: Date: 26 Apr 91 13:35:46 GMT References: Organization: Edmonton Remote Systems, Edmonton, AB, Canada Lines: 32 cnh5730@maraba.tamu.edu writes: > In article <1991Apr19.203828.21435@ulrik.uio.no> me@spirea.UiB.NO (My Account > ersys!drin@nro.cs.athabascau.ca (Adrian Smith) writes: > >We're having a *major* problem with a SCSI drive on a plain, 105 Meg > >slab. Before I get into it, I've tried NextAnswers, FAQ, my campus rep, > [stuff deleted...] > >We've got a Micropolis 1648-7 drive (330 Meg half-height), which we're > > and I have a Conner CP-3100 SCSI (105 Meg half-height) > > Your SCSI drives probably are not compatible with the NeXT. There are > drives out there which will _NOT_ work with the NeXT, no matter how > hard you try. I am not sure of the Micropolis model # mentioned, but I > have seen a Micropolis drive which _WAS INCOMPATIBLE_ with the NeXT. > This was due to the drive manufacturers SCSI implementation (if you want to > call it that), not NeXT. > > In otherwords, caveat emptor, and hope you have a money-back > guarantee. > > -- > "Battle not with monsters, lest ye become a monster, > and if you gaze into the abyss, the abyss gazes also into you." > -Friedrich Wilhelm Nietzsche The problem was a bad ROM. It's now fixed. Works great... Adrian Smith ersys!drin@nro.cs.athabascau.ca Edmonton Remote Systems: Serving Northern Alberta since 1982