Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!arktouros!dyer
From: dyer@arktouros.MIT.EDU (Steve Dyer)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: Large ESDI disk help
Message-ID: <1989Dec15.211629.3453@athena.mit.edu>
Date: 15 Dec 89 21:16:29 GMT
References: <764@ursa-major.SPDCC.COM> <3325@ccncsu.ColoState.EDU> <3266@ibmpa.UUCP>
Sender: news@athena.mit.edu (News system)
Reply-To: dyer@arktouros.MIT.EDU (Steve Dyer)
Distribution: usa
Organization: MIT Project Athena, Cambridge MA 02139
Lines: 27

In article <3266@ibmpa.UUCP> mlewis@dolphin.tcspa.ibm.com (Mark S. Lewis) writes:
>> I tried TWO different Maxtor 4380 ESDI drives and got the same error.
>> Both are sitting in the corner of my office unused...
>
>A Maxtor drive that works is model XT-4380E (310 Meg).  The SAUTIL recognizes
>it as a 310e type drive.  If you cannot get any of your drives to work with
>the E-ESDI, perhaps you should regress to the standard ESDI controller.  It's
>better than having such fine drives going unused.

But I *have* an XT-4380E.  Two of them.  I set the switches to the same
as recommended for the 310e drive, which after all, is an XT-4380E, no?
I got consistent results from SAUTIL: "can't init drive" or something like
that--it's been about 6 months.  I've tried the disks in positions 0, 1 and
2 of the controller.  No luck.  What has your experience been with them?
I'm very eager to hear.

I don't have an ESDI (non-EESDI) controller, however.  The rationale
of fleshing out my disks with additional ESDI disks was that I could
get rid of my ST506 controller, which right now is running two non-IBM
disks along with the IBM 110mb ESDI disk as the root/boot on the EESDI
controller.


---
Steve Dyer
dyer@ursa-major.spdcc.com aka ...!{harvard,linus,ima,m2c,rayssd}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu