This message is from the T13 list server.
Date & time, yes, to some granularity.
For me, most of the interesting info has appeared in the more or less undocumented hex
that accompanies the event. Provided your issue repeats consistently and you have
memorised enough hex from real bus traces, then the undocumented hex, being plain hex,
becomes readable. There you see Cdb fragments, Data addresses (including alignment in
address & length), Srb parameters, etc. The hex is usually Ctrl+C copyable, but
that's an obscure enough fact that I find people often send me .png instead.
Pat LaVarre
-----Original Message-----
From: Hale Landis [mailto:[EMAIL PROTECTED]]
Sent: Thu 1/30/2003 9:44 PM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [t13] auto sense of Atapi
This message is from the T13 list server.
On Thu, 30 Jan 2003 15:52:39 -0800, Eschmann, Michael K wrote:
>This message is from the T13 list server.
>In Windows-based systems drivers do send request-sense
>and the result doe get logged in an event log,
Having never seen this log, does anyone know where it is documented?
Does it have basic information like date, time, device, command,
command parameters, error status and sense, object name that was the
target of the I/O operation (directory, free space, file name), name
of I/O requistor (kernel component, program name)?
Just curious.
Hale
*** Hale Landis *** www.ata-atapi.com ***
