This message is from the T13 list server.
> Also, as a thought, with ATA-8, would it be worth a further attempt at
> trying to get SMART logging standardised? Having this feature built into
> the OS would be incredibly useful.
Please elaborate on what part of SMART logging is NOT standardized.
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
====================================================
|---------+---------------------------->
| | Andrew Hill |
| | <[EMAIL PROTECTED]|
| | ors.org.uk> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | rg |
| | No Phone Info |
| | Available |
| | |
| | 02/29/2004 06:33 |
| | AM |
| | Please respond to|
| | andrew.hill |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: [t13] Long logical sectors - anything support these?
|
>--------------------------------------------------------------------------------------------------------------|
This message is from the T13 list server.
Hiya,
Busy doing some ATA driver testing again. Just wondered: is there is
anything out there which actually uses the long physical sectors and long
logical sectors in a drive?
I realise most of you are actually working for respective drive companies,
but could anyone recommend a drive which uses these features? I'd like to
see if they work under RISC OS's new ATA driver, but have yet to find a
drive which uses > 512 byte sectors.
Also, as a thought, with ATA-8, would it be worth a further attempt at
trying to get SMART logging standardised? Having this feature built into
the OS would be incredibly useful.
I made my comment regarding improving CRC checking for IDENTIFY DEVICE
blocks in ATA-8 earlier, but still can't think of an effective way of
doing this, without effectively replacing the command with an equivalent
which enforces CRC checking, which obviously carries big downsides itself.
Best wishes,
Drew
