Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!arizona!arizona.edu!ece.arizona.edu!wpd
From: wpd@ece.arizona.edu (William P. Delaney)
Newsgroups: comp.os.minix
Subject: Re: Non-ST506 winchester driver for PS/2
Keywords: ST506 PS/2 386 Model 70
Message-ID: <1991Jun6.130807@ece.arizona.edu>
Date: 6 Jun 91 20:08:07 GMT
References: <2191@Terra.cc.brunel.ac.uk>
Reply-To: wpd@ece.arizona.edu (William P. Delaney)
Distribution: world,local
Organization: University of Arizona Dept. of Electrical and Computer Engineering
Lines: 34
Nntp-Posting-Host: beetle.ece.arizona.edu

In article <2191@Terra.cc.brunel.ac.uk>, eesrajm@cc.brunel.ac.uk (Andrew
J Michael) writes:
|> 
|> I've just tried to get MINIX running on an IBM PS/2 Model 70 386, and
found
|> that the ps_wini.c driver only works for ST506 drives.  The Model 70
has
|> a strange drive on an edge connector rather than ribbon cables - I
presume
|> that it is some kind of IDE, but I wouldn't like to bet on it.

The PS/2 Model 70 386 actually uses an ESDI controller that is identical
in
function to the ESDI adapter that you find in a standard slot on other
PS/2s.
They used the basic idea behind IDE drives (i.e. controller built into
the
drive unit) to save a slot.  From a software point of view, however,
the
configuration is almost identical to a normal ESDI configuration.  The
one
small difference that I have noticed is that the adapter ID value that
comes
from the POS port on the PS/2 motherboard is different.

Someone posted an ESDI driver a few months ago.  It should work fine,
unless
it scans the POS registers in search of a particular adapter ID.  If
this
problem does arise, the fix is pretty straightforward - just check for
either
of two adapter IDs.

Bill Delaney (wpd@ece.arizona.edu)