This message is from the T13 list server.
The greatest problem I've run into with getting rid of old functionality is with customer testing and manufacturing software. Frequently this is old stuff that is not even maintained anymore, so having them update it to avoid the old command is not really an option. Remember that ATA was originally created to guide people as to what they need to make products that can be sold. We always have to be careful not to let our desire to reduce the task of new implementations from breaking old ones. That said, I personally like the idea of making seek obsolete. Jim -----Original Message----- From: Pat LaVarre [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 8:05 AM To: [EMAIL PROTECTED] Subject: Re: [t13] Proposal - obsolete Seek This message is from the T13 list server. Obsoleting not-useful-in-the-field stuff like Ata op x70 Seek isn't necessarily helpful. Summer of 2001 I saw people surprised to discover an Oem in question there wanted Ata ops x23/33 ReadLong/WriteLong to work. They were ok learning those new ops and the corresponding xEF:44 SetFeatures VendorUniqueLongBlockLength ... but they were not happy having to learn an obsoleted data transfer protocol: they had trouble tossing just the hi bytes away after the first x200 bytes transferred in pairs. Pat LaVarre >>> [EMAIL PROTECTED] 01/16/02 08:56AM >>> This message is from the T13 list server. On Wed, 16 Jan 2002 08:41:40 -0700, Mclean, Pete wrote: >I have uploaded e02101r0 Proposal to obsolete the SEEK command in >ATA/ATAPI-7 to incoming on the FTP site. It will be added to the agenda for >the February meeting. Yes! Yippie! Party Time! Why didn't we do this years ago? *** Hale Landis *** www.ata-atapi.com *** Subscribe/Unsubscribe instructions can be found at www.t13.org. Subscribe/Unsubscribe instructions can be found at www.t13.org. Subscribe/Unsubscribe instructions can be found at www.t13.org.
