Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!samsung!uakari.primate.wisc.edu!caen!kuhub.cc.ukans.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!sac
From: sac@matt.ksu.ksu.edu (Stuart Alan Craig)
Newsgroups: comp.os.minix
Subject: ESDI Drives are Now Working
Message-ID: <1991Jun28.161250.25407@maverick.ksu.ksu.edu>
Date: 28 Jun 91 16:12:50 GMT
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University
Lines: 27
Nntp-Posting-Host: matt.ksu.ksu.edu


Found the problem with the WD1007AH ESDI controller when using at_wini.c
It seems that the controller BIOS stores the drive parameter table
into the vector table starting at 0:0160 (16 total bytes), then
repoints interrupt vector 41h to the new table entry.

Since the MINIX 1.3 kernel overwrote the vector table to repoint
to 'unexpected interrupts', the ESDI drive parameter table was
overwritten before the wini driver had a chance to read it.
A few quick bandaids seemed to fix the problem and I am now up
and running.

Many of you have responded, saying that the ESDI controller works
so I can only assume that MINIX 1.5 and up doesn't overwrite the vector
table anymore.

Thanks for all the responses.


-Stuart Craig  
	sac@matt.ksu.ksu.edu

--
---------------------------------------------------------------------------
| Stuart A. Craig                      | "To iterate is human, to recurse |
|    Internet: sac@matt.ksu.ksu.edu    |  divine."   -Dennis M. Ritchie   |
---------------------------------------------------------------------------