One of you disk guys probably knows this off the top of your head.
The SATA IDENTIFY_DEVICE block includes a checksum as the last word, as
do several other SATA responses. Does the Windows SATA port driver care
about the checksums?
I wrote many months ago that we have a client doing a simulation of a
SATA controller and device. It works fine on Linux, but on Windows we
get three IDENTIFY_DEVICE requests, and then no more communication. The
drive never materializes. It’s taken this many months to get the
project rolling…
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim,
I’m not trying to be snide here, but it would probably be faster to simply implement the checksum according to the SATA-IO spec and test it, than to ask here.
I don’t have access to the source, so I can’t answer the question for you.
Phil
Not Speaking for LogRhythm!
On 6/22/16, 1:08 PM, “xxxxx@lists.osr.com on behalf of Tim Roberts” wrote:
One of you disk guys probably knows this off the top of your head.
The SATA IDENTIFY_DEVICE block includes a checksum as the last word, as
do several other SATA responses. Does the Windows SATA port driver care
about the checksums?
I wrote many months ago that we have a client doing a simulation of a
SATA controller and device. It works fine on Linux, but on Windows we
get three IDENTIFY_DEVICE requests, and then no more communication. The
drive never materializes. It’s taken this many months to get the
project rolling…
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>