Leisner.Henr@xerox.com (Marty) (08/16/89)
I dug this up which explains some more about the AT disk problems. marty ---------------------------------------------------------------- Date: 15 Sep 87 17:37:34 EDT (Tuesday) Subject: 1.2 AT drivers still seems at little ill To: info-minix@udel.edu cc: leisner From: Marty <Leisner.Henr> I now have a 1.1 system up and running on Aztec C and want to get my hard disk going so I can have a useful system. After the bootblok transfer control to fsck, the controller status port (1f7H) is 0 -- the disk controller is totally idle. After booting the system, execute win_init() which executes com_out(), which calls drive_busy() which fails automatically if RDY (ready) or SC (seek complete) is 0. I'm currently playing around with the driver (I have the specs for the WD1002-WAH in front of me and it seems to agree with the bios). I played blindly with the winchester driver to get my home system running of the hard disk, now I want a driver which runs reliably on both 6 and 8 Mhz ATs. The way the driver boots up (if you can send a command to the controller, set number hard disks to 0) is not very robust. I went though this in May, and I'm going through this again. Does anyone have a really good AT driver they'd like to send me (uucp please). Any pointers to good discussions about how these WD1002-WAH boards work would be nice. Has anyone been able to use the at_wini driver with newers ATs? It seems like its really close except for some sticky (:->) bits. marty GV: leisner.henr NS: martin leisner:henr801c:xerox UUCP: martyl@rocksvax.uucp ----------------------------------------------------------------