> >Anything in the interrupt code, or the arch independent IDE code since
> >then? From the descriptions posted, there was a stray IDE interrupt after
> >the set multiword DMA failure in most cases. Should the SET_FEATURE
> >command that performs the set multiword DMA 2 operation generate an
> >interrupt? Can delayed handling of this interrupt result in the drive not
> >clearing the busy flag?
>
> It should not generate an interrupt, but I may have forgot to tell the
> drive not to do so. But that's not the problem. The IDE interrupt
Can you add code to tell the drive not to generate that interrupt when the
feature set happens? Maybe the drive is being boneheaded, and insists on
first having the int cleared before it will proceed further.
Just a dumb idea, I know ...
Michael
