This message is from the T13 list server.
> Harlan Andrews <[EMAIL PROTECTED]> 12/13/01 05:31PM > ... > Neither the device nor the host should use > ANY intermediate data > until the transfer is COMPLETED > and errors are checked. > Therefore, the "extra" bytes should be completely transparent. Hang on a minute, this can't be meant as quoted out of context here? An x0A/2A/AA Write block command that fails renders all the content of the blocks it addresses indeterminate? Maybe commonly only the blocks before the bad block changed, but only a BadHost assumes that limited effect? Ditto a ModeSelect command: a bad page in the stream doesn't guarantee that good pages in the stream will have no effect? Ditto a WriteBuffer command: a bad Crc for the last burst of bytes doesn't guarantee the good bytes sent earlier will have no effect? Ditto .... > Neither the device nor the host should use > ANY intermediate data > until the transfer is COMPLETED > and errors are checked. A device can avoid using intermediate data only by buffering all the data of the command. For a command block that moves, say, xFFFF blocks i.e. about 32MiB at 0.5KiB/block, ... no device that buffers less than 32MiB can avoid using intermediate data. Pat LaVarre Subscribe/Unsubscribe instructions can be found at www.t13.org.
