>>         atactl wd0 setstandby 5
>> 
>> and all my errors have gone away.   the main reason i used setidle
>> was /usr/share/examples/apm/script uses it.
>> 
>> it isn't clear to me if that means we should just forget about
>> the problems with setidle or not?
>
>Surely not, but I don't really have the time to work on this for now,
>and as we have several workaround possible ... 

It seems to me that many drives have firmware bugs regarding the use
of SET IDLE.  Since it seems like everyone uses SET STANDBY, is it
a) possible _to_ fix, and b) even worth it?

--Ken