This message is from the T13 list server.
Tony, Being you are something like the local trusted ATAPI guy, when a host issues an atapi flush cache in packet writing mode, and the device roasts-smokes-frys the firmware, this is a "bad device". Basically a device which has used a previously reserved opcode, now self destructs when operating within the bounds of the atapi guild lines. I found a great roar to hear about a given atapi device shipped by most of the big name vendors being listed as a security attack and destroys the device. Now assuming the host is trying to do the correct thing, how best does one decode the mode pages in atapi under all the variations to date? Cheers, Andre Hedrick LAD Storage Consulting Group
