This message is from the T13 list server.
Okay, then how does T13 plan to address sector recovery after the virtual destructive test of WRITE WRONG (e02126r0) ? Without a means to undo the test data written to the device logs, there is a beauty of a DOS on drives. Some nasty virus which runs and tells the HOST to issue "WRITE WRONG" to the entire or various segments of the media. Or the proposal needs to define it is reserved for vendor unique commands to enable the oem access layer setup. This command should not be set/enable in retail product, well scratch the last comment. Can not set policy in T13, only the technical aspects. <ear plugs in> Thank You !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! <ear plugs out> Andre Hedrick LAD Storage Consulting Group On Mon, 3 Nov 2003 [EMAIL PROTECTED] wrote: > This message is from the T13 list server. > > > > No. There is no 'read right' proposal in the queue. > > Please note that at the October Plenary, that Larry Barras agreed to take > 'ownership' > of WRITE WRONG (e02126r0), since Curtis Stevens (the original author) is > not currently > a member of T13. > > Thank You !!! > ----------------------------------------------------------------- > Jim Hatfield > ATA Interface Firmware & T13 (ATA/ATAPI) Standards Representative > Seagate Technology - PSG > e-mail: [EMAIL PROTECTED] > s-mail: 389 Disc Drive; Longmont, CO 80503 USA > voice: 720-684-2120 > fax : 720-684-2711 > ==================================================== > > > James, > > Is there not an additional proposal for Write Wrong called Read Right to > clear the forced media error? Maybe Curtis can answer? I just remember > the bad jokes and great laughes everyone had when the IDEMA Japan folks > were in from over seas. > > Cheers, > > Andre Hedrick > LAD Storage Consulting Group > > >
